chore(workflow): switch to npm trusted publishing; drop NPM_TOKEN env#149
Merged
Conversation
Trusted publishing has been configured per-package on npm (manual web UI step, completed). The OIDC token from 'permissions.id-token: write' authenticates this workflow as a trusted publisher for each @ngaf/* package — no token needed in env. After two consecutive successful trusted-publish releases, you can: - gh secret delete NPM_TOKEN (remove the unused secret from this repo) - Revoke the local token via npm settings Provenance attestations continue to be generated automatically via NPM_CONFIG_PROVENANCE='true'. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Trusted publishing has been configured per-package on npm for all 7 `@ngaf/*` packages. The workflow can now authenticate via OIDC instead of a long-lived token.
Changes
Verification path
After merge, the next workflow trigger will exercise OIDC end-to-end:
If OIDC fails (e.g., trusted publisher not found), the workflow will error at the publish step. Re-add the token env block as a quick rollback if needed.
After two clean releases via trusted publishing
```
gh secret delete NPM_TOKEN
```
Then revoke the local `.env` token at https://www.npmjs.com/settings/blove/tokens.
🤖 Generated with Claude Code