ci: publish via npm Trusted Publishing (OIDC), drop NPM_TOKEN#4
Merged
Conversation
Switch the release workflow to OIDC trusted publishing: remove the NODE_AUTH_TOKEN/NPM_TOKEN secret and let npm (>=11.5.1, installed in the job) exchange the GitHub Actions id-token for a short-lived publish credential, attaching provenance automatically. Requires a Trusted Publisher configured for the package on npmjs.com (repo lostium/angular-deploy-bunny, workflow publish.yml). Co-Authored-By: Claude Opus 4.7 (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
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.
Switches the release workflow from a long-lived
NPM_TOKENsecret to npm Trusted Publishing (OIDC).env.NODE_AUTH_TOKEN/ theNPM_TOKENsecret dependency.npm@latestin the job to guarantee OIDC support (npm ≥ 11.5.1).id-token: write(already present) lets npm exchange the GitHub Actions OIDC token for a short-lived publish credential and attach provenance automatically.Before the first OIDC release works, two one-time steps are needed (outside this PR):
npm publish(tokenless vianpm login).lostium/angular-deploy-bunny, workflowpublish.yml.After that, every GitHub release publishes via OIDC with no stored secret.
🤖 Generated with Claude Code