ci: drop abandoned beta prerelease channel - #111
Merged
Conversation
rolandjitsu
force-pushed
the
ci/drop-beta-channel
branch
from
August 2, 2026 07:55
5eec50a to
32d8dd1
Compare
|
🎉 This PR is included in version 4.0.0 🎉 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
1 participant
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.
What kind of change does this PR introduce?
Did you add tests for your changes?
If relevant, did you update the documentation?
Summary
The
betabranch and itsv3.0.0-beta.1prerelease were leftovers from an abandoned Nov-2024 release attempt on a git lineage that no longer exists. semantic-release cappedmainat<3.0.0-beta.1, so the pending major (feat!: drop Node 20) failed withEINVALIDNEXTVERSION.Remove
betafrom the semantic-release branches to allow the workflow to trigger. Combined with the reservedv3.0.0tag (3.0.0 is permanently burned on npm),mainshould resume cleanly at 4.0.0.Does this PR introduce a breaking change?
N/A.
Other information