Support dual-branch releases (stable + main)#1620
Merged
Merged
Conversation
- Add `stable` to release workflow trigger branches - Make npm dist-tag conditional: `stable` gets `latest`, `main` keeps `beta` (from changeset publish) - Make GitHub release flags branch-aware: stable = latest + non-prerelease, main = prerelease + not latest - Change changeset baseBranch to `stable` for this branch Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Contributor
|
Contributor
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests🌍 Community Worlds (64 failed)mongodb (4 failed):
redis (3 failed):
turso (57 failed):
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 🌍 Community Worlds
✅ 📋 Other
|
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
Configures the release pipeline for dual-branch publishing after the
stablebranch split:stableto release workflow trigger branches so pushes tostablerun the release jobstablegetlatest, pre-releases frommainkeep only thebetatag (applied bychangeset publish)stablereleases are marked as latest + non-prerelease,mainreleases are marked as prerelease + not latestbaseBranchtostableso the "Version Packages" PR targets this branchContext
This is part of the GA release plan:
stablebranch created frommain✅stable(exits changeset pre-release mode → produces 4.2.0 GA) ✅mainstays in pre-release mode for 5.0.0-beta.xTest plan
stablestablewith 4.2.0 versionslatestdist-tagmainbranch releases still publish withbetatag only (nolatestoverride)🤖 Generated with Claude Code