Repository navigation
ci: release 6.0.0 candidates from the next branch - #65
Merged
Merged
Conversation
Pushes to next release X.0.0-rc.N under the npm dist-tag next and a GitHub pre-release; master keeps releasing to latest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🎉 This PR is included in version 6.0.0-rc.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Adds a pre-release channel for the 6.0 candidates.
branches:masteras before, plusnextwithprerelease: "rc".release.ymlalso runs on push tonext. The file name and environments are unchanged, so the trusted publisher still matches.concurrency: group: release, somasterandnextreleases never push tags and notes at the same time (sdk-python and sdk-dotnet already have it).nextreleasesX.Y.Z-rc.Nto npm under thenextdist-tag (neverlatest), with a GitHub release marked as a pre-release.masterkeeps releasing as before.nextintomasterwith a merge commit after the server 6.0 release).Releases nothing (
ci:). After this merges,nextis created frommasterand the breaking PRs are retargeted to it.Dry run (semantic-release 25.0.9 against a
file://bare clone, analyzer and notes only):feat!onnextgives6.0.0-rc.1on the next channel, a followingfix:gives6.0.0-rc.2,masterreleases nothing, and mergingnextintomastergives6.0.0on the default channel.🤖 Generated with Claude Code