Repository navigation
ci: publish to npm with trusted publishing instead of a token - #7
Merged
Merged
Conversation
The package now has a trusted publisher on npmjs.com for this workflow, so npm verifies the run through GitHub's OIDC token (id-token: write) and NPM_TOKEN is no longer needed. The previous token had expired, and direct publishing with granular tokens that bypass 2FA ends in January 2027. The current Node LTS ships npm 11.20, above the 11.5.1 that trusted publishing needs. The same change already published @moulibheemaneti/docfold 0.1.1 through trusted publishing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ewn3bYVbsq8jq7B4eP2C47
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.
Summary
@moulibheemaneti/commitguardnow has a trusted publisher on npmjs.com (GitHub Actions,moulibheemaneti/commitguard,publish.yml). npm can verify a publish run through GitHub's OIDC token, so the workflow no longer needsNPM_TOKEN.NODE_AUTH_TOKEN/NPM_TOKENfrom the publish step.id-token: write, which trusted publishing and provenance both use, and update the comments.lts/*is Node 26.13 with npm 11.20, above the 11.5.1 that trusted publishing needs.Why: the previous
NPM_TOKENhad expired, granular tokens last at most 90 days, and npm stops direct publishing with 2FA-bypass tokens in January 2027.The same change already published
@moulibheemaneti/docfold@0.1.1through trusted publishing (moulibheemaneti/docfold#4). npm validates a new trusted publisher on its first publish, so the next commitguard release is that check.Checklist
bun testpasses locally (workflow-only change)bun tsc --noEmitreports no type errors (workflow-only change)CHANGELOG.mdupdated under[Unreleased]: release-please writes itpackage.json(if this is a release-worthy change): release-please does itfeat:,fix:,chore:, etc.)Generated by Claude Code