ci(release): swap pnpm for npm for trusted-publisher OIDC#119
Merged
stackbilt-admin merged 1 commit intomainfrom Apr 18, 2026
Merged
ci(release): swap pnpm for npm for trusted-publisher OIDC#119stackbilt-admin merged 1 commit intomainfrom
stackbilt-admin merged 1 commit intomainfrom
Conversation
…OIDC pnpm 9's `--provenance` attaches attestations via OIDC but still uses NODE_AUTH_TOKEN for publish auth. npm CLI's `--provenance` does the full OIDC-based publish auth that npm trusted publishers expect. v0.12.0 release attempts returned `E404` on the first package (@stackbilt/adf) — npm's stealth 404 for trusted-publisher auth rejection. Trusted-publisher config verified identical across all 11 packages; hypothesis is that pnpm's token-auth path is being rejected by npm for packages with trusted-publisher configured. `npm publish --workspaces` iterates all non-private packages in `packages/*/` (root package.json declares the workspace glob). NODE_AUTH_TOKEN retained as belt-and-braces for any package without a trusted publisher. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced Apr 18, 2026
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.
Summary
publish-npmwithE404on@stackbilt/adf— npm's stealth 404 for trusted-publisher auth rejection. Trusted-publisher config on all 11 packages verified identical (OrgStackbilt-dev, Repocharter, Workflowrelease.yml, Env blank).--provenancesigns attestations via OIDC but still authenticates the publish request withNODE_AUTH_TOKEN. When a package has a trusted publisher configured, npm may require the publish auth itself to be OIDC-based — and rejects token auth with a 404.actions/setup-node@v6.3.0) has first-class trusted-publisher OIDC support:npm publish --provenancedoes the full OIDC-based publish auth that trusted publishers expect.pnpm -r publish --access public --no-git-checks --provenance→npm publish --workspaces --access public --provenance.Why
npm publish --workspacesworksRoot
package.jsondeclares"workspaces": ["packages/*"], sonpm publish --workspacesiterates every non-private workspace and publishes each. All 11@stackbilt/*packages have"private": false+"publishConfig": { "access": "public" }.NODE_AUTH_TOKENenv retained as belt-and-braces in case any package doesn't yet have a trusted publisher — harmless otherwise.Test plan
gh workflow run release.yml -f tag=v0.12.0. Idempotent — no 0.12.0 tarballs have shipped yet.@stackbilt/*packages at 0.12.0 on npm.--provenanceas a hotfix) — trusted-publisher config has a deeper issue beyond the three visible UI fields.Related
🤖 Generated with Claude Code