Repository navigation
chore(release): cut 1.1.2 in the changelog - #23
Merged
Merged
Conversation
1.1.1 was tagged before its changelog section existed, so bump-v1 refused it. 1.1.2 carries the same changes. Co-Authored-By: Claude Opus 5.5 <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
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.
v1.1.1 was published before
CHANGELOG.mdhad a## [1.1.1]section.bump-v1refused it (run 37587372645), sov1is still on v1.1.0 and the v1.1.1 tag is still lightweight.This moves the #21 and #22 entries out of
[Unreleased]into## [1.1.2] - 2026-10-07, with a note that 1.1.1 is skipped. It follows the python-project-template precedent (1.9.1 repairing 1.9.0) rather than deleting and re-creating a published tag.After merge
Publish release
v1.1.2on the merge commit.bump-v1should then pass the changelog check, annotatev1.1.2, and movev1.🤖 Generated with Claude Code