ci: use npm trusted publishing (OIDC) instead of NPM_TOKEN - #32
Merged
Conversation
The release job failed with EINVALIDNPMTOKEN because an NPM_TOKEN was still configured, forcing the legacy token auth path. Now that OIDC trusted publishing is set up on the npm package, let @semantic-release/npm perform the OIDC token exchange itself. - Remove the NPM_TOKEN env var so the OIDC path is used - Remove `registry-url` from setup-node, which wrote an .npmrc with an empty authToken and broke authentication - Drop NPM_CONFIG_PROVENANCE: trusted publishing emits provenance automatically - Upgrade npm to latest (trusted publishing requires npm >= 11.5.1) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
🎉 This PR is included in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Contexte
Le job Release échouait avec
EINVALIDNPMTOKEN: unNPM_TOKEN(invalide/vide) était encore configuré, ce qui forçait le chemin d'authentification par token au lieu de l'OIDC.Maintenant que le trusted publishing OIDC est configuré côté package npm, on laisse
@semantic-release/npmréaliser l'échange de token OIDC lui-même (getIDToken("npm:registry.npmjs.org")→ échange avec le registry → skip de la vérif de token).Changements (
release.yaml)NPM_TOKEN→ le chemin OIDC est empruntéregistry-urldanssetup-node: il écrivait un.npmrcavec un_authTokenvide qui cassait l'authentificationNPM_CONFIG_PROVENANCE: le trusted publishing génère la provenance automatiquementid-token: writeetGITHUB_TOKEN(pour la release GitHub) sont conservés.🤖 Generated with Claude Code