Skip to content

ci: drop --provenance flag from npm publish#3

Merged
mastermanas805 merged 1 commit into
masterfrom
fix/npm-publish-no-provenance
May 12, 2026
Merged

ci: drop --provenance flag from npm publish#3
mastermanas805 merged 1 commit into
masterfrom
fix/npm-publish-no-provenance

Conversation

@mastermanas805
Copy link
Copy Markdown
Member

Summary

The publish workflow was failing with 404 Not Found - PUT https://registry.npmjs.org/instanode-mcp on first-publish. The --provenance flag requires extra OIDC setup; dropping it unblocks the publish. Re-add later when NPM_TOKEN is rotated to a provenance-enabled one.

🤖 Generated with Claude Code

The publish workflow was failing with `404 Not Found - PUT
https://registry.npmjs.org/instanode-mcp` on the first publish attempt
of the unscoped name. The `--provenance` flag requires GitHub OIDC +
specific NPM_TOKEN scope to attest the package on first publish; the
current token doesn't carry that scope. Drop provenance until the
NPM_TOKEN is rotated to one that has the `id-token: write` + provenance
trust set up — provenance is a bonus, not a publish requirement.

After this lands, the next push to master with a version bump should
publish cleanly. Verify via:
  npm view instanode-mcp version

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mastermanas805 mastermanas805 merged commit b8dcfda into master May 12, 2026
1 check passed
@mastermanas805 mastermanas805 deleted the fix/npm-publish-no-provenance branch May 12, 2026 05:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant