Skip to content

ci: use OIDC authentication instead of access token for npm publish#4

Open
siddharthvp wants to merge 1 commit intomainfrom
npm-publish
Open

ci: use OIDC authentication instead of access token for npm publish#4
siddharthvp wants to merge 1 commit intomainfrom
npm-publish

Conversation

@siddharthvp
Copy link
Copy Markdown
Member

npm classic access token no longer works (see https://github.blog/changelog/2025-12-09-npm-classic-tokens-revoked-session-based-auth-and-cli-token-management-now-available). Granular access tokens could be used, but they are only valid for 90 days - so would need to be refreshed for almost every update. Switch to OIDC authentication instead (see https://docs.npmjs.com/trusted-publishers), which doesn't require any tokens.

npm classic access token no longer works (see https://github.blog/changelog/2025-12-09-npm-classic-tokens-revoked-session-based-auth-and-cli-token-management-now-available). Granular access tokens could be used, but they are only valid for 90 days - so would need to be refreshed for almost every update. Switch to OIDC authentication instead (see https://docs.npmjs.com/trusted-publishers), which doesn't require any tokens.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant