fix(release): idempotent vsce/ovsx publish + bump vscode to 0.1.0#22
Merged
Conversation
Two changes that unblock the v0.1.0 launch on Marketplaces:
1. vscode extension version bumped 0.0.3 → 0.1.0 to match the
tokenometer + @tokenometer/core npm versions. The Marketplace
already had v0.0.3 published from a prior partial run, so the new
workflow run was hitting "already exists" on a duplicate publish.
2. vsce + ovsx publish steps now wrap the publish call in shell that:
- Captures stdout+stderr.
- Returns 0 if publish succeeded.
- Returns 0 if publish failed but the error message contains
"already exists" / "already published" / "version exists" — these
are benign on idempotent re-runs (e.g. when Marketplace got the
version from a previous run that failed at a later step).
- Re-exits with the original code for any other error.
- `continue-on-error: true` so a real failure doesn't bail the
subsequent ovsx / Marketplace verify / Vercel / smoke-test steps.
Also gitignores `packages/vscode/*.vsix` and removes the previously
committed `tokenometer-vscode-0.0.3.vsix` — generated artifacts shouldn't
live in the repo (they're built fresh in CI).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
faraa2m
added a commit
that referenced
this pull request
May 11, 2026
….0 (#22) Two changes that unblock the v0.1.0 launch on Marketplaces: 1. vscode extension version bumped 0.0.3 → 0.1.0 to match the tokenometer + @tokenometer/core npm versions. The Marketplace already had v0.0.3 published from a prior partial run, so the new workflow run was hitting "already exists" on a duplicate publish. 2. vsce + ovsx publish steps now wrap the publish call in shell that: - Captures stdout+stderr. - Returns 0 if publish succeeded. - Returns 0 if publish failed but the error message contains "already exists" / "already published" / "version exists" — these are benign on idempotent re-runs (e.g. when Marketplace got the version from a previous run that failed at a later step). - Re-exits with the original code for any other error. - `continue-on-error: true` so a real failure doesn't bail the subsequent ovsx / Marketplace verify / Vercel / smoke-test steps. Also gitignores `packages/vscode/*.vsix` and removes the previously committed `tokenometer-vscode-0.0.3.vsix` — generated artifacts shouldn't live in the repo (they're built fresh in CI). Co-authored-by: Claude Opus 4.7 (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
Phase I completion. The v0.1.0 npm publish landed cleanly. The Marketplace publish on the manual workflow run failed because v0.0.3 of `faraa2m.tokenometer-vscode` was already on the Marketplace from a prior partial attempt — vsce returned "already exists", step exited 1, ovsx + downstream all skipped.
Changes
Bump vscode 0.0.3 → 0.1.0 to match the npm package versions. Eliminates the duplicate-publish trip on this run.
Idempotent vsce + ovsx steps. Wrap the publish call so:
Gitignore `packages/vscode/*.vsix` — generated artifacts shouldn't be in the repo. Built fresh in CI each run.
Test plan
🤖 Generated with Claude Code