refactor(ci): decouple VS Code extension publishing#36
Merged
Conversation
VS Code Marketplace requires strict semver (MAJOR.MINOR.PATCH). Replace 4-segment version (0.1.0.46) with 3-segment (0.1.46) by setting patch to the build number instead of appending a 4th segment. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ryanbas21
changed the title
- Remove VS Code snapshot stamp + publish from release.yml snapshot job - Remove publish-vscode job from publish-extension.yml - Add standalone publish-vscode.yml triggered by workflow_dispatch VS Code extension releases are now fully manual: bump version in package.json, merge, then trigger the workflow. This avoids the semver/4-segment version conflicts and decouples VS Code from the npm/Chrome/Firefox release pipeline. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ryanbas21
force-pushed
the
fix/vscode-version-semver
branch
from
4cc6c94 to
d3de900
Compare
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
release.yml(Firefox, VS Code)extensionworkflow input (no longer used)SNAPSHOTenv var from snapshot build (no extension uploads)publish-vscodejob frompublish-extension.ymlpublish-vscode.ymltriggered byworkflow_dispatchSnapshot job now only handles npm snapshot publishes. Extension publishing is cleanly separated:
publish-extension.yml(on GH release)publish-extension.yml(on GH release)publish-vscode.yml(manual dispatch)Release process
manifest.jsonversion, merge, let changesets create a GH release which triggerspublish-extension.ymlpackage.jsonversion, merge, manually triggerpublish-vscode.ymlTest plan
release.ymlsnapshot job only does npm snapshotsrelease.ymlrelease job unchanged (changesets + Chrome manifest stamping)publish-extension.ymlonly has Chrome + Firefox jobspublish-vscode.ymlis standalone workflow_dispatch🤖 Generated with Claude Code