ci: enable npm trusted publishing with OIDC#23
Merged
Conversation
Remove NPM_TOKEN secret dependency and switch to npm's native OIDC-based trusted publishing. GitHub Actions will authenticate via OIDC token, improving security and eliminating the need for manual token rotation.
m9tdev
force-pushed
the
m9tdev/npm-trusted-publish
branch
from
d7f96b9 to
2989a56
Compare
m9tdev
changed the title
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.
Remove NPM_TOKEN secret dependency and switch to npm's native OIDC-based trusted publishing. GitHub Actions will now authenticate via OIDC token, improving security by eliminating the need for manual token rotation.
Setup required on npmjs.com:
m9tdev, Repo:effect-prisma-generator, Workflow:release-please.yml