chore(release): make release-v14 the stable v14 line - #3303
Merged
Merged
Conversation
`release-v14` becomes the branch semantic-release publishes to npm `latest` from. `master` becomes a prerelease branch that publishes release candidates to `rc`, ready for v15 to land on it. The `rc` channel is set explicitly: semantic-release otherwise publishes a prerelease branch under a dist-tag named after the branch. The bundle-size check also runs for PRs into `release-v14`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
oliverlaz
approved these changes
Sep 28, 2026
|
Size Change: -2.72 kB (-0.25%) Total Size: 1.09 MB 📦 View Changed
ℹ️ View Unchanged
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-v14 #3303 +/- ##
==============================================
Coverage ? 85.48%
==============================================
Files ? 512
Lines ? 16195
Branches ? 5127
==============================================
Hits ? 13844
Misses ? 2351
Partials ? 0 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This branch was successfully deployed
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
2 participants
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.
🎯 Goal
Make
release-v14the stable v14 line before v15 lands onmaster.When this PR merges:
release-v14publishes 14.x releases to npmlatest.masterbecomes a prerelease branch that publishes v15 release candidates (15.0.0-rc.N) to npmrc.The
release-v14branch itself was pushed at the 14.12.0 release commit (0fb5ac306), so it currently matchesmaster.🛠 Implementation details
.releaserc.json: the branch list becomes:release-v14is a release branch, not a maintenance branch. semantic-release needs at least one release branch, and a prerelease branch doesn't count. Sorelease-v14can't be limited to14.x, and it must not receive breaking changes.mastersets"channel": "rc"explicitly. Without it, semantic-release publishes a prerelease branch under a dist-tag named after the branch (master)..github/workflows/size.yml: the bundle-size check also runs for PRs intorelease-v14. The CI workflow already runs on PRs into any branch, and the Release workflow already allows branches starting withrelease.✅ Verification
I ran a local dry run of semantic-release 25.0.3 against a throwaway copy of the repo, with both branches recreated there: this commit on
release-v14, andmasterwith v15 merged:release-v14, it foundv14.12.0and no releasable commits, so there's no new version.masterwith v15 merged, it proposed15.0.0-rc.1on thercchannel.After this merges, run the Release workflow on
release-v14in dry-run mode. It checks the real tokens and GitHub branches, and should also report no new version.mastermasterstill carries its old config (master→latest) until the v15 merge lands. Until then, don't run the Release workflow on either branch, and keepmasterfrozen.