Repository navigation
Release 0.2.0 - #18
Merged
Merged
Conversation
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release preparation
CHANGELOG.md only: change the first line to exactly
0.2.0:.The release workflow's awk therefore emits no
(unreleased)remainder.All release-note entries and history remain unchanged. No version, manifest,
lock or product source changes.
The accepted 16-member archive does not contain CHANGELOG.md.
The tagging guard is a clean-clone reproduction at this exact head with
Node 24.9.0 and pnpm 11.7.0: frozen install, build and package pack, exactly
the release build steps. Expected SHA256:
1924ece1970b4b1fd9172712602239b84e2b54a242eef7d833b34eeb80419c1d.Clean-clone reproduction at this exact head: PASS with those exact tool
versions and release build steps. The archive is binary-identical to the
accepted bytes, exactly 16 members and no CHANGELOG. The verification clone
stayed clean. The existing full gate additionally passes all 35 tests, plus
typecheck, build, lint, peers, uniform DSH graph and import/line guards.
No runtime, checkpoint, restore, lifecycle or permission behavior changes.
The verification clone uses private stores/caches and disposable generated
outputs. Independent review and required CI remain gates; no review bot is
configured in this repository.
The architect sequences both 0.2.0 publications together. Publication is held
for the separately coordinated live real-model acceptance. The builder does
not merge, tag or publish.