Closed
Conversation
hhpatel14
force-pushed
the
publishToOpenvsx
branch
from
fa46935 to
7626964
Compare
hhpatel14
force-pushed
the
publishToOpenvsx
branch
from
7626964 to
5dcd981
Compare
hhpatel14
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
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.
Add a step to publish the extension to the Open VSX registry.
Backport this change to the
release-8.0branch and rerun the release workflow to catch up on publishing to the Open VSX registry. Since the v8.0.0 already published to maketplace, the step skips gracefully, logs “already published”, and proceed to the next stepCI kept using deprecated vsce@2.15.0 because no local version existed. The deprecated vsce CLI lacked flag
--changelog-pathand stuck at v2.15.0.@vscode/vscenewer, well maintained and works with Node 20+.