docs(changelog): record S1–S3 in the unreleased 2.0.0 entry - #278
Merged
Merged
Conversation
…ed yet 2.0.0 is bumped and merged but not tagged, so its CHANGELOG entry is still a description of what will ship — and S1, S2 and S3 changed what that is. Three paragraphs in the governance section: the state-neutral banners (C-97), check 10 (C-96), and the runbook's pre-tag checklist. Doing this now rather than in the release story: the entry becomes the release notes the moment the tag is cut, and a release note that omits what is in the release is the same defect this epic exists to close. 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.
Part of epic #267 — release hygiene between S3 (#270) and S5 (#272).
2.0.0 is bumped and merged but not tagged, so its CHANGELOG entry is still a description of what will ship — and S1, S2 and S3 changed what that is:
validate_docs.shcheck 10 (C-96)Done now rather than inside S5 because the entry becomes the release notes the moment the tag is cut, and a release note that omits what is in the release is the same defect this epic exists to close.
🤖 Generated with Claude Code