Ship universal VSIX without bundled CLI binary#2
Merged
MelbourneDeveloper merged 1 commit intomainfrom Feb 27, 2026
Merged
Conversation
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.
TLDR;
Simplify the release pipeline to produce a single universal VSIX that no longer bundles the platform-specific CLI binary.
Details
build-vsixjob — now builds one universal VSIXdotnet publishstep from VSIX packagingbin/directory from the VSIX via.vscodeignorebuild-clijob is unaffected and continues to produce platform-specific CLI artifactsHow do the tests prove the change works
Pipeline change — verified by successful CI build and VSIX packaging on push.