ci: publish to npm via Trusted Publisher (OIDC) instead of token#32
Merged
Conversation
Switch npm-publish workflow to OIDC-based Trusted Publishing, removing the NPM_TOKEN secret dependency. Also collapse the separate build and publish jobs into a single job (one npm install, then test then publish), bump actions to v6, and update Node to 24. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
Trusted Publishing signs provenance, which requires package.json "repository.url" to match the GitHub repo. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Overview
Switch npm publishing from a token (
NPM_TOKEN) to Trusted Publisher (OIDC), so CI authenticates to npm without a stored secret. This fixes the publish failure, which was a token auth error.Related
@tacc/html-filter-sortChanges
NPM_TOKENsecret dependency@v6and Node to24Testing
Tip
Successfully tested.
@tacc/core-components: ownerTACC, repoCore-Components, workflownpm-publish.yml.workflow_dispatch, and confirm it succeeds without a token.Notes
Tip
This repo on GitHub is a Trusted Publisher for this NPM package.