From 7b091f8ded45e81e309938aa47f6f4680805a3cd Mon Sep 17 00:00:00 2001 From: Abraham Date: Tue, 28 Jul 2026 18:10:41 -0700 Subject: [PATCH] fix(visimer): pass npm provenance via config, not a changeset flag (#2974) The first release run died on 'Unknown flag for publish: --provenance'; this repo's @changesets/cli has no such flag. npm reads NPM_CONFIG_PROVENANCE when changesets shells out to publish. GitOrigin-RevId: 4fbb9bfbac2dd527aced5847ca0243a84ff4e160 --- .github/workflows/release.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 2d54afd..1220ec0 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -98,8 +98,11 @@ jobs: if: steps.detect.outputs.has_changesets == 'false' run: | set -euo pipefail - # --provenance required for npm Trusted Publishing attestations. - pnpm changeset publish --provenance | tee /tmp/publish.log + # Provenance is required for npm Trusted Publishing attestations. + # This repo's @changesets/cli does not know a --provenance flag + # (that errored the first release run), so it goes through npm + # config instead — npm reads it when changesets shells out. + pnpm changeset publish | tee /tmp/publish.log # Changesets emits "packages published successfully" after >=1 # package ships; a no-op run (nothing ahead of npm) does not. @@ -149,3 +152,4 @@ jobs: git push origin --tags env: HUSKY: 0 + NPM_CONFIG_PROVENANCE: "true"