Repository navigation
Automate Open VSX releases and prepare VSIX for Microsoft - #4
Merged
Merged
Conversation
adrilasar
changed the title
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.
Stable GitHub releases run the existing Linux/Windows CI, validate the tag against the packaged version, attach one tested VSIX with its checksum, and publish it to Open VSX using trusted publishing. Microsoft stays manual: upload the release VSIX in its publisher portal. Manual workflow runs only validate and package.
The workflow uses restricted permissions and pinned actions. Open VSX trusted publishing and the tag-restricted
publishenvironment are configured. The officialovsxdevelopment client shares the pinnedvsceto avoid an older vulnerable duplicate. No Microsoft publishing job, cross-platform package comparison, or archive-preservation logic remains.The README adds installation badges for both registries and removes editor product names. Runtime behavior and version remain unchanged.
Validation: TypeScript build, 17 extension tests, 5 release tests, actionlint and preparation of a real packaged VSIX pass locally. Linux/Windows CI also passes, including current/minimum editor integration. Registry uploads have not been exercised by this workflow; its first real release will verify them. Badge image requests received HTTP 403 in this environment.
Related: #3. No new extension version has been published.