Skip to content

build(publish): make provenance CI-only (drop publishConfig.provenance)#14

Merged
bdelanghe merged 1 commit into
mainfrom
conformance/provenance-ci-only
Jun 29, 2026
Merged

build(publish): make provenance CI-only (drop publishConfig.provenance)#14
bdelanghe merged 1 commit into
mainfrom
conformance/provenance-ci-only

Conversation

@bdelanghe

Copy link
Copy Markdown
Contributor

Tiny pre-publish cleanup. The publish workflow already passes npm publish --provenance explicitly, so publishConfig.provenance: true was redundant — and it forced every publish (including a local first npm publish to claim the scope) to attempt provenance, which only works under CI OIDC. Dropping it: CI still publishes with provenance (the workflow flag), and a manual npm publish just works.

🤖 Generated with Claude Code

The publish workflow already passes `npm publish --provenance` explicitly, so
publishConfig.provenance:true was redundant — and it forced ALL publishes (incl. a
local first `npm publish` to claim the scope) to attempt provenance, which only
works under CI OIDC. Dropping it: CI still publishes with provenance (the workflow
flag), and a manual `npm publish` just works.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@bdelanghe bdelanghe merged commit 837cc91 into main Jun 29, 2026
1 check passed
@bdelanghe bdelanghe deleted the conformance/provenance-ci-only branch June 29, 2026 01:56
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