mirror of
https://github.com/sharevb/it-tools.git
synced 2026-11-20 21:23:08 +03:00
* ci: use pnpm/setup for pnpm setup and install Replace the corepack bootstrap + actions/setup-node + separate `pnpm install` steps with a single `pnpm/setup` step, which installs pnpm (version read from package.json `packageManager`), installs Node, caches the pnpm store and runs `pnpm install`. Node 24 stays pinned via `runtime: node@24`, and the GitHub Pages workflow drops `pnpm/action-setup` in favour of the same step (it now caches the store too). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * chore: pin Node in package.json, bump pnpm to 11.22.0 Move the Node version out of the workflows and into package.json, so the `pnpm/setup` steps are just `cache: true`: - `engines.node` pins Node 24 as package metadata. - `devEngines.runtime` is the field `pnpm/setup` actually reads to pick the runtime, and pnpm itself uses it to run scripts, so it is needed for the pin to take effect. Bump `packageManager` from pnpm 11.11.0 to 11.22.0 (latest 11.x). pnpm records the runtime in the lockfile (`node@runtime:24.19.0`), and the 11.22.0 resolver writes peer suffixes differently from 11.11.0, so pnpm-lock.yaml is regenerated. Lint, typecheck, unit tests and build all pass on the updated lockfile. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA * chore: bump .nvmrc to Node 24.19.0 The repo was already on Node 24 everywhere else (Dockerfile, workflows, and now engines/devEngines in package.json) while .nvmrc still selected 22.19.0. Align it with the rest, matching the node@runtime:24.19.0 version pnpm resolved into the lockfile. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YAwAJ6L3Mai8eSxXf5e6SA --------- Co-authored-by: Claude <noreply@anthropic.com>
2 lines
8 B
Plaintext
2 lines
8 B
Plaintext
24.19.0
|