fix: align pnpm/Node setup in CI to fix npm publish EUNKNOWNCONFIG#62
Merged
Conversation
Root cause of the still-failing publish: pnpm/action-setup@v2 hardcoded pnpm 9 while packageManager declared [email protected]. That mismatch made changeset publish fall through to a plain npm publish, which rejects the --git-checks flag changesets passes for the pnpm path. Mirrors the working setup in the sibling tesla-protocol repo: pnpm/action-setup@v4 (reads packageManager, no hardcoded version), Node 24, packageManager bumped to [email protected].
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
mainafter PR fix: remove invalid --provenance flag from ci:publish #60 and fix: bump @changesets/cli to fix npm publish EUNKNOWNCONFIG #61:npm error EUNKNOWNCONFIG Unknown cli flag: --git-checks. Neither the removed--provenanceflag nor the@changesets/clibump was the actual root cause.pnpm/action-setup@v2hardcodesversion: 9, while rootpackageManagerdeclares[email protected]. That mismatch makeschangeset publishfall through to a plainnpm publishinstead of the pnpm path, and npm rejects the--git-checksflag changesets passes for pnpm.tesla-protocol, which publishes cleanly with the same@changesets/[email protected]and no.npmrc: it usespnpm/action-setup@v4with no hardcoded version (readspackageManager), Node 24,packageManager: [email protected].tesla-protocol's working setup inpublish.ymlandci.yml.pnpm/action-setup@v2(version: 9) →@v4with no hardcoded version.packageManagerbumped to[email protected]to match.ci:publish: changeset publish+NPM_CONFIG_PROVENANCE: trueand PR fix: bump @changesets/cli to fix npm publish EUNKNOWNCONFIG #61's@changesets/[email protected].pnpm install --frozen-lockfile,pnpm -r run build,pnpm lint, andpnpm -r --no-bail tscall pass locally with pnpm 10.30.3.mainafter this merges. It unblocks a growing backlog:@teslemetry/apilocal 0.9.0 vs npm 0.7.0,iobroker.teslemetry's first publish,node-red-contrib-teslemetry0.3.0,homebridge-teslemetry, andn8n-nodes-teslemetry.