Enable OIDC trusted publishing for npm packages #28
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
Configure GitHub Actions workflow to use OIDC authentication instead of NPM_TOKEN for publishing packages. This provides better security by eliminating long-lived secrets and enables automatic provenance attestation. Changes: - Add publish environment and id-token: write permission - Remove NPM_TOKEN from workflow configuration - Keep GITHUB_TOKEN for git operations Ticket: VL-3686
lcovar
approved these changes
Nov 5, 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.
Context
Configures the publish workflow to use OIDC authentication for npm publishing instead of long-lived NPM_TOKEN secrets. This provides better security and enables automatic provenance attestation.
Changes
publishenvironment to the workflowid-token: writeandcontents: readpermissionsNext Steps
After merging, trusted publishing must be configured on npm.com for each package:
References
Ticket: VL-3686