chore(release): bump version to 3.0.1 for next dev cycle#665
Merged
Conversation
3.0.0 was published as `latest`, but package.json still pinned 3.0.0. The beta release workflow checks the published versions and aborts when the base version already exists, so every push to master failed at the "Bump pre-release version" step. Bumping to 3.0.1 lets master betas publish as 3.0.1-beta.N again.
github-actions
Bot
added
the
t-tooling
bliuchak
approved these changes
May 29, 2026
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
3 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.
3.0.0was published to npm aslatest, butpackage.jsonstill pinned3.0.0. The beta release workflow (before-beta-release.cjs) aborts when the base version already exists on npm:So every push to master failed at the Bump pre-release version step (example run) and no beta was published.
Bumping to
3.0.1restores the dev cycle — master pushes now publish as3.0.1-beta.N, matching the existing convention (after2.7.0shipped, the repo moved to2.7.1→2.7.1-beta.0).