Repository navigation
chore(release): publish release-v14 under its own dist-tag - #3417
Merged
Merged
Conversation
release-v14 becomes the v14 maintenance line, like release-v13 and release-v12: channel v14, range 14.x, npm dist-tag release-v14. master publishes v15 under latest. Merge this before 15.0.0 is released, so no later v14 release can move latest. Ticket: REACT-1532
|
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
 |
Contributor
|
Size Change: -2.43 kB (-0.18%) Total Size: 1.32 MB 📦 View Changed
ℹ️ View Unchanged
|
oliverlaz
approved these changes
Nov 6, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-v14 #3417 +/- ##
===============================================
+ Coverage 86.84% 87.36% +0.51%
===============================================
Files 526 590 +64
Lines 16699 20454 +3755
Branches 5251 6471 +1220
===============================================
+ Hits 14503 17870 +3367
- Misses 2196 2584 +388 ☔ 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
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 v14 maintenance line, the same wayrelease-v13andrelease-v12are, so thatlatestbelongs to v15 frommaster.Ticket: https://linear.app/stream/issue/REACT-1532
Merge this before the master PR (#3418) and before 15.0.0 is released. With today's config,
release-v14publishes tolatest. A v14 release made after 15.0.0 would put 14.x back onlatest.🛠 Implementation details
.releaserc.json:masteronlatestandrelease-v14with channelv14, range14.x.@semantic-release/npmaddsrelease-to a channel that looks like a version range, so v14 releases go to the npm dist-tagrelease-v14, likerelease-v13today.release-v14now fails the release withEINVALIDNEXTVERSIONinstead of publishing 15.0.0.release-v14after this merges publishes nothing new. It adds 14.16.1 to therelease-v14dist-tag. That step runsnpm dist-tag add, which can fail with E401 under npm trusted publishing if the package's trusted publisher does not allownpm dist-tag. The fallback isnpm dist-tag add stream-chat-react@14.16.1 release-v14.developers/RELEASE.mdanddevelopers/BRANCHES.mdnow describe this setup (same text as onmaster). The old copies here still describedmasteras the only branch and listed docs-release workflow options that no longer exist.Checked by running semantic-release 25.0.3 against a local copy of the repo:
fix:commit → 14.16.2 on channelv14;BREAKING CHANGE:commit →EINVALIDNEXTVERSION, range>=14.16.1 <15.0.0-rc.1;latest, which is why this merges first.🎨 UI Changes
None.