ci(publish): use npm OIDC #176
Merged
Conversation
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
pdesoyres-cc
force-pushed
the
enable-npm-oidc
branch
from
a4c8e56 to
5afee37
Compare
florian-sanders-cc
approved these changes
Oct 20, 2025
Contributor
florian-sanders-cc
left a comment
florian-sanders-cc
left a comment
There was a problem hiding this comment.
Oh well, I didn't think it was that straightforward, great job, thanks for that 🙌
Galimede
approved these changes
Oct 28, 2025
Member
Galimede
left a comment
Galimede
left a comment
There was a problem hiding this comment.
Thanks for handling this, I didn't think it was that simple. 🤯
hsablonniere
approved these changes
Oct 30, 2025
Member
hsablonniere
left a comment
hsablonniere
left a comment
There was a problem hiding this comment.
Wow, same here, I didn't expect something that simple, so nice. Looking forward to use it on our other projects 👏
hsablonniere
added a commit
to CleverCloud/clever-tools
that referenced
this pull request
Nov 12, 2025
Migrate npm publishing to use OIDC-based trusted publishing instead of static tokens, as npm classic tokens will be permanently revoked on November 19, 2025. Changes: - Add top-level OIDC permissions (id-token: write, contents: read) - Add job-level OIDC permissions to publish-npm job - Remove NPM_TOKEN secret usage and NODE_AUTH_TOKEN environment variable - Add --provenance flag to npm publish for package transparency Reference: https://docs.npmjs.com/trusted-publishers/ Implementation based on: CleverCloud/clever-client.js#176 Closes #991
pdesoyres-cc
force-pushed
the
enable-npm-oidc
branch
from
4767b37 to
4c637f0
Compare
pdesoyres-cc
force-pushed
the
enable-npm-oidc
branch
from
4c637f0 to
1c62b5b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What this PR do?
This PR uses the new mechanism introduced by NPM for secured publishing: https://docs.npmjs.com/trusted-publishers
How to review