fix(ci): switch to npm trusted publishing for automated releases #1
+5
−2
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
Replace NPM_TOKEN-based authentication with OIDC trusted publishing, which bypasses 2FA requirements and eliminates the need for long-lived npm tokens. This is the recommended modern approach for npm publishing from GitHub Actions. Changes: - Remove NPM_TOKEN from release workflow environment - Add npm audit signatures step for security verification - Enable provenance in package.json publishConfig
github-actions bot
added a commit
that referenced
this pull request
Jan 14, 2026
## [2.0.1](v2.0.0...v2.0.1) (2026-01-14) ### Bug Fixes * **ci:** switch to npm trusted publishing for automated releases ([#1](#1)) ([4da7636](4da7636))
3 tasks
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
Replaces
NPM_TOKEN-based authentication with OIDC trusted publishing to resolve the 2FA/OTP requirement that was blocking automated npm releases. This is the modern recommended approach for npm publishing from GitHub Actions, eliminating the need for long-lived npm tokens.Changes
NPM_TOKENenvironment variable since trusted publishing uses OIDC tokens automaticallynpm audit signaturesstep to verify dependency provenanceprovenance: trueinpublishConfigfor explicit attestation documentationSetup Required
Before merging, the trusted publisher must be configured on npmjs.com (already completed):
TxnLabhaystack-jsrelease.ymlTest Plan
main