From bb4aa7f02bfdf237e5400020d03c511c22aa4e9a Mon Sep 17 00:00:00 2001 From: Brett Adams Date: Wed, 22 Jul 2026 13:56:51 +1000 Subject: [PATCH] fix: remove invalid --provenance flag from changeset publish changeset publish forwards unrecognized flags straight to npm publish, and --provenance isn't a valid npm publish flag (npm expects it via config, not CLI) - this crashed every real publish with EUNKNOWNCONFIG. Provenance is now enabled via NPM_CONFIG_PROVENANCE in the workflow step's env instead. --- .github/workflows/publish.yml | 1 + package.json | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index 047be49..de98b65 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -51,6 +51,7 @@ jobs: title: "chore: version packages" env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + NPM_CONFIG_PROVENANCE: true - name: Check for specific package releases id: check_releases diff --git a/package.json b/package.json index e78c65d..7eb9a00 100644 --- a/package.json +++ b/package.json @@ -19,7 +19,7 @@ "lint:fix": "oxlint . --fix", "changeset": "changeset", "release": "changeset version && git commit -am 'chore(release): ${{changeset.version}}' && changeset publish --public && git push --tags", - "ci:publish": "changeset publish --provenance", + "ci:publish": "changeset publish", "pack": "pnpm -r pack" }, "packageManager": "pnpm@10.18.1",