chore(ci): restore NPM_TOKEN env on publish step#62
Merged
Conversation
Re-attaches NODE_AUTH_TOKEN: secrets.NPM_TOKEN to the publish step. The OIDC-only approach blocked on a 2FA-on-publish org enforcement that can't be flipped quickly; a fresh automation token (no-2FA scope) replaces the rotated/expired secret that has been failing since v0.29.0. --provenance + id-token: write retained so each publish still ships a signed Sigstore attestation alongside the token-authed publish. Unblocks v0.31.0 (541 adapters) reaching npm.
tangletools
approved these changes
May 31, 2026
tangletools
left a comment
tangletools
left a comment
Contributor
There was a problem hiding this comment.
Restoring token-auth as a pragmatic unblock; OIDC + provenance retained on the publish step so we don't lose the signed-attestation benefit. Approved as tangletools.
tangletools
added a commit
that referenced
this pull request
Jun 1, 2026
Drop NPM_TOKEN env path, always pass --provenance, simplify error message to point at the trusted-publisher config. Mirrors the cleanup in tangle-network/agent-dev-container#1550 that flips publish-sandbox-sdk/-cli/hub-sdk to OIDC-only. Prerequisite: /package/@tangle-network/agent-integrations/access trusted publisher entry must be at PACKAGE level with workflow=publish.yml env=blank. The trusted-publisher entry from session-earlier #61 may still be there (it was reverted to NPM_TOKEN in #62 but the npm-side config is decoupled). If publish fails after merge, verify the entry exists at the package level. Co-authored-by: Drew Stone <hello@tangle.tools>
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
2 participants
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.
Re-attaches
NODE_AUTH_TOKEN: secrets.NPM_TOKENto the publish step. The OIDC-only approach blocked on a 2FA-on-publish org enforcement that can't be flipped quickly; a fresh automation token (no-2FA scope) replaces the rotated/expired secret that has been failing since v0.29.0.--provenance+id-token: writeare retained so each publish still ships a signed Sigstore attestation alongside the token-authed publish.Unblocks v0.31.0 (541 adapters) reaching npm.