Clarify NPM Trusted Publishing authentication in release workflow#5
Closed
Copilot wants to merge 1 commit into3-add-release-workflowfrom
Closed
Clarify NPM Trusted Publishing authentication in release workflow#5Copilot wants to merge 1 commit into3-add-release-workflowfrom
Copilot wants to merge 1 commit into3-add-release-workflowfrom
Conversation
5 tasks
Copilot
AI
changed the title
[WIP] Address feedback on commitlint integration in workflow
Clarify NPM Trusted Publishing authentication in release workflow
Jan 15, 2026
bnachtweh
approved these changes
Jan 15, 2026
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
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.
Addressed review comment questioning whether the release workflow requires explicit NPM token configuration. The workflow correctly uses NPM Trusted Publishing (OIDC-based authentication) via the
npm-publishenvironment, eliminating the need for staticNODE_AUTH_TOKENsecrets.Key configuration:
environment: npm-publish- References GitHub environment configured as trusted publisher with NPMpermissions: id-token: write- Enables OIDC token generation for authentication--provenanceflag - Generates attestations as part of trusted publishing flowNo code changes required - clarified that the existing setup is correct for NPM's OIDC authentication method.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.