ci: Publish releases using OIDC instead of npm token#1224
Open
seb-cr wants to merge 1 commit into
Open
Conversation
curlyfriesplease
approved these changes
Jun 1, 2026
curlyfriesplease
left a comment
curlyfriesplease
left a comment
There was a problem hiding this comment.
Great. I assume the Trusted Publisher configuration has been added on npmjs.com? (I cannot see it myself)
Contributor
Author
|
Yes. For anyone curious, this is how it looks: 
|
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
2 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.
Switches to npm's new trusted publishing mechanism, which removes the need for a long-lived npm token in the publishing workflow.
OpenID Connect (OIDC) support was added in npm v11.5.1 and Semantic Release v25.0.1, hence the updates here. Setting this up also involves manual configuration of the trusted publisher within the package settings on npm.
For more information about trusted publishing, see the npm docs.
Jira: ENG-5181