Skip to content

ci: fix pnpm/action-setup version conflict on main - #35

Merged
adriannoes merged 3 commits into
mainfrom
fix/ci-pnpm-action-version
Jul 19, 2026
Merged

adriannoes merged 3 commits into
mainfrom
fix/ci-pnpm-action-version

Conversation

@adriannoes

@adriannoes adriannoes commented Jul 19, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Let pnpm/action-setup use packageManager (no dual version pin).
  • Bump CI Node 20 → 22 (pnpm@11.9.0 needs ≥22.13).
  • Add direct deps @eslint/js + typescript-eslint (required under pnpm strict linking).
  • Stop redeclaring react-hooks plugin in eslint.config.mjs (already from eslint-config-next).
  • Ignore pnpm-lock.yaml in Prettier.

Test plan

  • Local: lint, format:check, tsc, test:run, build
  • CI green on this PR

pnpm@11.9.0 requires Node >= 22.13; Node 20 fails with ERR_UNKNOWN_BUILTIN_MODULE (node:sqlite).
Under pnpm, @eslint/js and typescript-eslint must be direct dependencies; eslint-config-next already registers react-hooks.
@adriannoes
adriannoes merged commit b4870c9 into main Jul 19, 2026
1 check passed
@adriannoes
adriannoes deleted the fix/ci-pnpm-action-version branch July 19, 2026 04:28
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