Add publish-vscode-extension action#2
Open
zackverham wants to merge 19 commits into
Open
Conversation
… bugs - Validate mutual exclusivity of extensionFile and packagePath inputs - Add file existence check when extensionFile is provided - Run vsce package from the extension directory (cd into packagePath) - Use consistent multi-target handling (for loop) in vsce publish - Improve PAT redaction to avoid bash pattern-matching edge cases Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The check for mutual exclusivity of extensionFile and packagePath only compared against "./", missing the case where a user sets packagePath to "." (without trailing slash). Add "." to the default-value comparison so both forms are recognized as the default. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Remove packaging logic from the action — callers are responsible for building the .vsix beforehand. This reduces complexity and the number of inputs to maintain. Update tests to pre-package the fixture extension and target Node 24. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The skipDuplicate input was only applied to vsce publish (VS Marketplace) but silently ignored when publishing to Open VSX registries. Since ovsx supports --skip-duplicate, pass it in both code paths. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…erage Use VSCE_PAT/OVSX_PAT environment variables instead of passing the token as a CLI argument, avoiding process-list exposure. Add set -euo pipefail to all shell steps, extract a resolve step for testability, and add tests for registry URL routing and trailing-slash normalization. Pin Node to 20 LTS. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…versioning docs - Add workflow file path to trigger paths so CI runs on workflow changes - Remove unnecessary Node setup from the missing-file test job - Replace global npm install with npx for vsce/ovsx to avoid conflicts on self-hosted runners - Add CHANGELOG.md and expand versioning section in README Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Newer versions of vsce require activationEvents when a main entry point is specified. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Premature for the current stage of the action. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The ovsx CLI reads its PAT from the OVSX_TOKEN environment variable, not OVSX_PAT. Also replace redundant vsce package steps in resolution test jobs with dummy files since they only verify tool selection. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Unpinned npx calls fetch the latest version on every run, which means a breaking change in either package could silently break the action for all consumers. Pin to @vscode/vsce@2 and ovsx@0 to prevent surprise breakage while still getting patch/minor updates. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Node 24 is not an LTS release. Documentation examples should recommend LTS versions for reliability; Node 22 is the current active LTS line. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Node 24 is not an LTS release (won't be until October 2026). Using the active LTS version (Node 22) avoids transient failures from pre-stability bugs and better reflects what most users of this action will run. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Jun 3, 2026
Closed
Closed
Co-Authored-By: Claude Opus 4.6 <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
publish-vscode-extension) that publishes pre-built.vsixfiles to the VS Marketplace or Open VSX Registry