Skip to content

fix(ci): run the config validator with pnpm instead of npx - #19

Merged
setchy merged 1 commit into
mainfrom
fix/validator-pnpm
Oct 29, 2026
Merged

setchy merged 1 commit into
mainfrom
fix/validator-pnpm

Conversation

@setchy

@setchy setchy commented Oct 29, 2026

Copy link
Copy Markdown
Member

Problem

The Validate Renovate config job fails for every consumer repository:

npm error code EBADDEVENGINES
npm error Invalid name "pnpm" does not match "npm" for "packageManager"

Consumers (gitify, electron-menubar, website, gnome) declare a pnpm devEngines.packageManager in package.json. With Node 26 / npm 11.20+, npm validates that field and refuses to run npx inside the project, so the validator never starts.

Fix

  • Set up pnpm (and Node, still from the consumer's .nvmrc) with pnpm/setup.
  • Run the validator with pnpm --package=renovate@44.182.2 dlx renovate-config-validator … instead of npx.
  • install: false since the job only needs the CLI.
  • Refreshed .github/workflows/actions.lock.

Same fix as setchy/renovate-config#33, verified end to end on setchy/thoughtworks-tech-radar-volumes#1220.

Consumer repositories declare a pnpm devEngines.packageManager in their
package.json, and npm refuses to exec anything inside such a project
(EBADDEVENGINES). Switch the validator to pnpm/setup and pnpm dlx so it
runs regardless of the consumer's package manager.
@setchy
setchy requested a review from afonsojramos as a code owner October 29, 2026 12:25
@setchy
setchy merged commit fe1d5e9 into main Oct 29, 2026
1 check passed
@setchy
setchy deleted the fix/validator-pnpm branch October 29, 2026 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant