docs: record 1.3.1 in release-please manifest and CHANGELOG#532
Open
petercorke wants to merge 1 commit into
Open
docs: record 1.3.1 in release-please manifest and CHANGELOG#532petercorke wants to merge 1 commit into
petercorke wants to merge 1 commit into
Conversation
The 1.3.1 rtb-data-pin release was published out-of-band from a maintenance branch off the v1.3.0 tag (main had already diverged with in-progress work), so release-please's own bookkeeping never saw it. Without this, release-please could later try to reuse the v1.3.1 tag for a from-main release and collide with the one that already shipped. Co-Authored-By: Claude Sonnet 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
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.
Summary
maintenance/1.3.x(off thev1.3.0tag), sincemainhad already diverged with in-progress breaking work. release-please's manifest never saw it..github/.release-please-manifest.json(.: 1.3.0 → 1.3.1) andCHANGELOG.mdto match, so release-please's bookkeeping is accurate and doesn't risk later colliding with the already-publishedv1.3.1tag.pyproject.toml's version onmain— that stays whatever it is until release-please's own next PR updates it normally.🤖 Generated with Claude Code