Add independent VS Code extension releases - #64139
Draft
Jake Bailey (jakebailey) wants to merge 2 commits into
Draft
Add independent VS Code extension releases#64139Jake Bailey (jakebailey) wants to merge 2 commits into
Jake Bailey (jakebailey) wants to merge 2 commits into
Conversation
Validate the package-lock version before creating a release tag and remove the unsupported test-signing path from the VSIX build pipeline.
typescript-automation
Bot
added
Author: Team
For Uncommitted Bug
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.
WIP, still hacking
The gist is that the VS Code extension is versioned and tagged separately, we trigger a release by running a workflow which then opens a PR, which we then release, which builds, publishes, and then sticks on GitHub releases
Fixes #63924