Repository navigation
ci: publish with npm trusted publishing instead of NPM_TOKEN - #416
Merged
Merged
Conversation
- grant `id-token: write` to the release job so @semantic-release/npm can exchange the GitHub OIDC token for a short-lived npm token - drop the NPM_TOKEN secret from the release step Requires a trusted publisher (FRSOURCE/frs-replace, ci.yml) configured on npmjs.com before merging. Co-Authored-By: Claude Fable 5.1 <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.
Migrates
@frsource/frs-replacefrom theNPM_TOKENsecret to npm trusted publishing (OIDC), same asis-animatedalready does (FRSOURCE/is-animated@d71e9c3).id-token: writeon the release job;@semantic-release/npm13 detects the GitHub OIDC environment and publishes with provenance automaticallyNPM_TOKENremoved from the release stepStatus: trusted publishers are configured on npmjs.com for every package, and the toolkit release (run 36886764279) has already published
@frsource/release-it-config@1.60.0andglobals-vitest@5.0.3through OIDC with signed provenance, so this PR is ready to merge.🤖 Generated with Claude Code