chore: pin the next dev beta to 5.3.1-beta.1 - #116
Merged
Conversation
Retargets the pending dev beta release from 5.2.0-beta.5 to 5.3.1-beta.1. The beta line is still numbered off 5.2.0 because the stable 5.3.0 release never completed: the promote PR (#108) merged with `Release-As: 5.3.0`, but the release-please PR it generated (#109) is still open, so no v5.3.0 tag exists and `.release-please-manifest-beta.json` sat at 5.2.0-beta.4. Release-please therefore proposed 5.2.0-beta.5 (#115) for the flow-discovery fix in #114, which is behind the stable line rather than ahead of it. The stable line is 5.3.0, so the next beta belongs on the 5.3.1 patch series. This commit is intentionally empty — the payload is the footer below, which release-please reads to pin the exact version of the next dev release. It applies once and needs no follow-up cleanup, unlike a `release-as` key in release-please-config-beta.json, which would pin every subsequent dev release until removed. Release-As: 5.3.1-beta.1
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
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.
Retargets the pending dev beta release from 5.2.0-beta.5 to 5.3.1-beta.1.
The beta line is still numbered off 5.2.0 because the stable 5.3.0 release never completed: the promote PR (#108) merged with
Release-As: 5.3.0, but the release-please PR it generated (#109) is still open, so no v5.3.0 tag exists and.release-please-manifest-beta.jsonsat at 5.2.0-beta.4. Release-please therefore proposed 5.2.0-beta.5 (#115) for the flow-discovery fix in #114, which is behind the stable line rather than ahead of it.The stable line is 5.3.0, so the next beta belongs on the 5.3.1 patch series.
This commit is intentionally empty — the payload is the footer below, which release-please reads to pin the exact version of the next dev release. It applies once and needs no follow-up cleanup, unlike a
release-askey in release-please-config-beta.json, which would pin every subsequent dev release until removed.Release-As: 5.3.1-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
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is enabled.