Add OpenID permissions in publish workflow #297
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
|
promeris
approved these changes
Dec 17, 2025
LaberionAjvazi
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
NPMjs changed the policy on classic tokens, and now only allows 90 day tokens. For CI/CD workflows, it has provided an oauth link (with OpenID) between the workflow and the registry. The link got created in the registry, and based on their guide, we need to add
id-token: writepermissions to the workflow, which allows GitHub Actions to generate OIDC tokens.Relevant links
NPMjs documentation for trusted publishing
Checklist