Skip to content

Conversation

@staaldraad
Copy link
Member

Minor workflow changes to use GitHub OIDC for trusted publishing to npm.

Allows using two GITHUB_TOKENS, one needed for OIDC + npm release. And the other that has permission to create tags. If we used just one, the token would either not have OIDC permissions (can't read id_token) or wouldn't have permission to create tags.

Relies on --> https://docs.npmjs.com/trusted-publishers

Minor workflow changes to use GitHub OIDC for trusted publishing to npm.

Allows using two GITHUB_TOKENS, one needed for OIDC + npm release. And
the other that has permission to create tags. If we used just one, the
token would either not have OIDC permissions (can't read id_token) or
wouldn't have permission to create tags.
@staaldraad staaldraad requested review from a team as code owners October 3, 2025 09:39
@mandarini mandarini self-assigned this Oct 3, 2025
@mandarini mandarini changed the title feat: enable trusted publishing feat(release): enable trusted publishing Oct 3, 2025
@mandarini mandarini merged commit b053559 into master Oct 3, 2025
1 check passed
@mandarini mandarini deleted the etienne/sec-549-use-trusted-publishing-for-npm-packages branch October 3, 2025 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants