chore: reset CHANGELOG-NEXT.md after the 0.3.5 release - #346
Merged
Conversation
0.3.5 shipped, and its notes are already the GitHub release body and the `notes` in latest.json (verified intact after the Windows CI rewrote the manifest). Leaving the entries here would ship them a second time in 0.3.6. Back to the headings-only template. The guard from #306 rejects it in this state, which is the point: the next release cannot go out until someone writes real entries. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
0.3.5 is out. Its notes already live in two places that matter: the release body and the
notesfield oflatest.json, which the in-app update prompt renders. Leaving the entries in this file would ship them a second time in 0.3.6.Back to the headings-only template.
scripts/checkChangelog.mjsrejects the file in this state, which is exactly the intent: 0.3.6 cannot be released until real entries are written.Post-release checks that gated this reset:
spctlreportssource=Notarized Developer ID,stapler validatepasses)latest.jsonwas rewritten withwindows-x86_64merged inlatest.jsonnotes intact after that rewrite (1801 chars, all four platform keys present) — the failure mode this ordering exists to avoid🤖 Generated with Claude Code