Publish to npm with trusted publishing - #17
Merged
Merged
Conversation
Add a release job that publishes through GitHub Actions OIDC, with no stored registry token and no approval per release. Document the one-time registry setup a maintainer does before the job can publish. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Adds a release job that publishes to npm through GitHub Actions OIDC trusted publishing. No registry token is stored and no one approves a release. Nothing is published by this change.
The job does nothing until the one-time registry setup in
CONTRIBUTING.mdis done: npm only lets trusted publishing update a package that already exists.🤖 Generated with Claude Code