Repository navigation
ci: publish releases through trusted publishing - #33
Merged
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.
Publishing stays owner-controlled: pushing a release tag still only creates the GitHub Release. This PR adds a
publishjob torelease.ymlthat the owner dispatches manually with an existing release tag.The job downloads the released VSIX and its SHA-256 file, verifies the checksum, and publishes the same artifact to the Visual Studio Marketplace with
vsce publish --oidcand to Open VSX withovsx publish --trusted-publishing. Both registries authenticate through OIDC trusted publishing, so no long-lived publisher token is stored in the repository or in GitHub Actions secrets.The release notes and maintainer documentation are updated to match the new flow.