chore(release): 0.16.0#38
Merged
Merged
Conversation
Nineteen commits landed since v0.15.0 and none of them reached the changelog, which opens by claiming "all notable changes to agentry are documented here." Two of the nineteen are real defects: syncCursor deleting the user's .cursor/ state, and protect-generated-dirs never guarding .opencode/. Anyone cloning at the v0.15.0 tag still has both. Minor rather than patch: sync's wipe behavior changed, package.json is now private with derived plugin-manifest metadata, and the suite went from 98 to 243 tests. The bump is a single sync-clean commit. It used to take two -- `chore(release)` bumped package.json while `scripts/sync-harnesses.js` held its own copy of the version, so the regenerated manifest landed in a following `chore(sync)` commit and only that one could be tagged. PR #29 made package.json the single source, so bumping it and running sync is one commit that CI's determinism gate passes.
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.
Why now
Nineteen commits since
v0.15.0, none of them in the changelog — which opens by claiming "All notable changes to agentry are documented here" and cites Keep a Changelog.Two of the nineteen are real defects. Anyone cloning at the
v0.15.0tag still has both:syncCursordeletes every file the user keeps in.cursor/, including.cursor/environment.jsonprotect-generated-dirsnever guarded.opencode/, whose three subdirectories are wiped on every syncWhy minor, not patch
Sync's wipe behavior changed,
package.jsonis nowprivatewith derived plugin-manifest metadata, and the suite went98 → 243.This bump is one commit — it used to take two
The old flow was
chore(release): X(bumppackage.json) →docs(changelog)→chore(sync): regenerate harness outputs for X, becausescripts/sync-harnesses.jsheld its own copy of the version. Only that last commit was sync-clean, so only that one could be tagged — the trap that made back-filling v0.12–v0.14 fail until each release's true tip was found.PR #29 made
package.jsonthe single source. Bumping it now carries the manifest automatically:So the release commit is itself sync-clean, and
release.yml's determinism gate passes on it. Verified:Verification
README's status line moves to
v0.16.0. Its one other mention of0.15.0is historical ("the v0.15.0 batch came from auditing the corpus") and stays.After merge
Tag the merge commit
v0.16.0and push it.release.ymlgates on sync-determinism + lint + tests, extracts the section above, and cuts the GitHub Release.