docs: the release-manifest guard was missing its changelog entry - #42
Merged
Conversation
Both 1.0.1 rails were written up under "The rails that catch the next one"; this one shipped with only a RELEASING.md cross-reference. Same shape, same section, and it goes in 1.1.0 rather than a new Unreleased heading because 1.1.0 is not tagged yet — nothing has been released. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FEA6GZUG9NKNQYrJKyDGdb
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.
Both 1.0.1 rails were written up in the changelog under "The rails that catch the next one".
The release-manifest guard (#41) shipped with only a
RELEASING.mdcross-reference, so a readerof the changelog would not know it exists or why.
Same shape, same section heading. It goes in the 1.1.0 section rather than a new
Unreleasedone because 1.1.0 is not tagged — only
v1.0.0exists, so nothing has actually been releasedyet and the entry is not retroactive.
The entry records the concrete failure rather than the rule:
plugin.jsonwas bumped alone, gitauto-merged
marketplace.jsonback to 1.0.1 with no conflict and no failing test, and the laggingmarketplace would have published a release nobody was offered.
Test plan
🤖 Generated with Claude Code
https://claude.ai/code/session_01FEA6GZUG9NKNQYrJKyDGdb