chore(ci): enable trusted publishing#143
Merged
vados-cosmonic merged 1 commit intobytecodealliance:mainfrom Mar 5, 2026
Merged
Conversation
This commit lightly refactors the `release.yml` CI flow and enables trusted publishing for NPM
tschneidereit
approved these changes
Mar 5, 2026
Member
tschneidereit
left a comment
tschneidereit
left a comment
There was a problem hiding this comment.
I agree that landing this still makes sense, yes
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
2 participants
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.
This commit lightly refactors the
release.ymlCI flow and enables trusted publishing for NPM.We are absolutely moving publishing to upstream wasmtime, so this PR might be moot, but given that we no longer need an NPM token any more to make releases,
release.ymlshould still be right for upstream usage.