From 9d9bc16ed5e95d59b0117bcafe7ff5ae314a1688 Mon Sep 17 00:00:00 2001 From: Will Eastcott Date: Wed, 10 Jun 2026 21:00:05 +0100 Subject: [PATCH] fix: pass provenance to changeset publish via npm config The Changesets workflow has failed on every push to main since --provenance was added to the publish command: changeset publish does not recognize that flag (it belongs to npm publish) and exits with "Unknown flag for publish". Drop the flag and set NPM_CONFIG_PROVENANCE=true on the step instead, which npm picks up when changeset publish shells out to it. Provenance is also generated automatically by npm trusted publishing (OIDC), which this workflow already uses, so the original intent is preserved. Co-Authored-By: Claude Fable 5 --- .github/workflows/changesets.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/changesets.yml b/.github/workflows/changesets.yml index a7a7d257..adff5bd0 100644 --- a/.github/workflows/changesets.yml +++ b/.github/workflows/changesets.yml @@ -44,7 +44,8 @@ jobs: with: commit: "chore: update versions" title: "chore: update versions" - publish: pnpm -w changeset publish --provenance + publish: pnpm -w changeset publish createGithubReleases: true env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + NPM_CONFIG_PROVENANCE: true