ci: release v3 as beta prereleases until GA - #257
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s Release Please configuration so that releases from master are published as beta prereleases during the v3 stabilization period, preventing them from taking GitHub’s “Latest” badge while still publishing artifacts normally.
Changes:
- Switch Release Please to
versioning-strategy: prereleasewithprerelease-type: beta. - Mark generated GitHub releases as
prerelease: true.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
charIeszhao
approved these changes
Jun 11, 2026
4 tasks
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.
Summary
Switch master releases to beta prereleases while v3 stabilizes (passkey acceptance and App Links are still open):
versioning-strategy: prerelease+prerelease-type: beta: with the breaking commits already on master, the pending release PR (release: 3.0.0-beta #245) will turn intorelease: 3.0.0-betaon its next refresh; every subsequent release bumps the prerelease number (3.0.0-beta.1,3.0.0-beta.2, …) regardless of commit type, so further breaking changes during the beta phase cannot bump the major again.prerelease: true: required by the prerelease versioning strategy, and marks beta releases as Pre-release on GitHub — they never take the "Latest" badge, so they don't interfere with the v2 line.The
publishjob is unaffected: betas are published to Maven Central as usual.To graduate to GA, revert this config and force the final version with an empty commit carrying a
Release-As: 3.0.0footer.Testing
N/A (release config only; will be exercised by the next release PR refresh)
Checklist
.changeset(N/A — this repo uses release-please)🤖 Generated with Claude Code