fix: remove invalid --provenance flag from ci:publish#60
Merged
Conversation
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.
This was referenced Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intent
ci:publishrunschangeset publish --provenance, but--provenanceisn't a valid changesets/npm publish flag - changesets forwards unknown flags straight tonpm publish, which rejects it (EUNKNOWNCONFIG: Unknown cli flag). Every real publish since api 0.7.0 has crashed as a result.--provenancefromci:publish; enable provenance viaNPM_CONFIG_PROVENANCE: truein the release step'senvinstead (npm reads it from config/env, not the CLI).releasescript'schangeset publish --publicdoesn't use--provenance, so it's untouched.Once merged, a maintainer needs to re-run the Publish workflow on
mainto ship the backlog of already-versioned-but-unpublished packages (@teslemetry/api0.7.1,iobroker.teslemetry0.1.11,node-red-contrib-teslemetry0.3.0,@teslemetry/homebridge-teslemetry0.1.11).