docs: restore the 0.5.0 entry the gate used to forbid - #32
Merged
Merged
Conversation
This entry was written when #26 merged, turned main red, and had to be reverted in #27 because release-gate.mjs required the top CHANGELOG heading to equal package.json's version on every push. #29 fixed that. The gate now reports: release-gate: ok, 0.5.0 pending, package at 0.4.2, 47 packed files all allowed which is the exact state it rejected this morning. The entry credits both of shivam-070208's contributions on the day they landed rather than at release time, which is what the contradiction had been preventing for every outside contributor, not only this one. Text recovered from issue #28, where it was parked so the revert would not lose it. 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.
The entry from #26 that had to be reverted in #27, restored now that #29 lets the CHANGELOG carry a pending release.
The gate on this branch:
That is the exact state that turned
mainred this morning, and it is now the documented, tested "pending" state.It credits both of @shivam-070208's contributions on the day they landed instead of at release time. That was the point of #28: the contradiction was not a tidiness problem, it was the reason an outside contributor could not be named in the changelog when their work merged.
The version stays
0.4.2and the entry stays undated.scripts/release.mjsdates it and bumps the version at release.🤖 Generated with Claude Code