fix: stamp VS Code extension version for snapshot publishes#34
Merged
Conversation
vsce rejects publish when the version already exists on the marketplace. Stamp package.json with BUILD_NUMBER as a 4th segment (e.g. 0.1.0.42) before publishing, matching the Chrome extension approach. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
vsce publishrejects when the version already exists on the marketplacepackage.jsonversion withBUILD_NUMBERas a 4th segment (e.g.0.1.0.42) before publishingTest plan
workflow_dispatchwithextension: true— VS Code publish should succeed🤖 Generated with Claude Code