Repository navigation
chore: release 1.0.0-rc.1 - #254
Merged
Merged
Conversation
The Marketplace rejects pre-release versions such as 1.0.0-rc.1, so a tag with a suffix would fail its Marketplace and Open VSX jobs. Such a tag now makes a GitHub pre-release with the .vsix files and publishes the npm packages under the next tag, leaving latest on the last release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012jSfzj1UNFUHV9YmmbjLg4
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012jSfzj1UNFUHV9YmmbjLg4
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.
The release candidate for 1.0.0.
Commits
ci: publish pre-release tags to GitHub and npm next only. The Marketplace rejects pre-release versions:vsce publishthrows "The VS Marketplace doesn't support prerelease versions", andvsce packageitself is fine. For a tag with a-suffix:.vsixfiles;--tag next, solateststays on 0.16;Plain
v*tags behave as before (--tag latest, which is npm's default).chore: release 1.0.0-rc.1.package.json,server/Cargo.tomlandserver/Cargo.lockare set to1.0.0-rc.1.## Unreleasedbecomes## 1.0.0-rc.1, with a short intro pointing to the stability page and the Breaking entries.Checks
test/cli.jsandtest/npm.jspass.ruby-templates --versionprints1.0.0-rc.1.format:checkpasses.After merge
Push the tag
v1.0.0-rc.1. Then:.vsixfrom the GitHub pre-release, or the CLI withnpm i -D @x-ror/ruby-templates@next.1.0.0PR and tagv1.0.0publish everywhere as usual.Generated by Claude Code