ci: modify workflow .yaml to work with Trusted Publisher #17
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.
Summary:
This PR updates the GitHub Actions release workflow to use npm Trusted Publishing (OIDC) instead of long-lived
NPM_TOKEN
secrets.Changes:
id-token: write
for OIDC-based publishing.NPM_TOKEN
from the release job.Why:
This change aligns with BitGo’s initiative to eliminate long-lived tokens and use GitHub’s OIDC-based authentication for npm publishing.
Trusted Publishers were configured in npmjs for all relevant repos.
Expected outcome:
Ticket: DX-2081