chore: re-anchor the beta line and pin the next beta to 5.6.0-beta.1 - #170
Merged
Merged
Conversation
#168 merged release-please's own `chore(dev): release 5.5.0-beta.6` as an ordinary PR, so no v5.5.0-beta.6 tag or release was created. The manifest then pointed at an untagged version, release-please lost its anchor, rescanned the whole history and picked up the stale version pin from #137 — hence #167. Roll manifest, package.json and CHANGELOG-beta.md back to the last real release (v5.5.0-beta.5) and pin the next beta with a real footer. Release-As: 5.6.0-beta.1
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
This was referenced Sep 17, 2026
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.
#168 merged release-please's own
chore(dev): release 5.5.0-beta.6as an ordinary PR, so no v5.5.0-beta.6 tag or release was created. The manifest then pointed at an untagged version, release-please lost its anchor, rescanned the whole history and picked up the stale version pin from #137 — hence #167.Roll manifest, package.json and CHANGELOG-beta.md back to the last real release (v5.5.0-beta.5) and pin the next beta with a real footer.
Release-As: 5.6.0-beta.1
What & why
Type of change
fix— bug fixfeat— new featureperf— performance improvementrefactor— code change that's neither a fix nor a featuredocs— documentation onlychore/ci/build/test— tooling, no user-facing change!or PR notes aBREAKING CHANGE:)Checklist
pnpm lintpassespnpm typecheckpassespnpm buildpassesCHANGELOG.md(release-please handles this)README.md/STYLE_GUIDE.mdupdated if behaviour or output changedHow to test