You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Address feedback: make package.json the single source of truth for node
and pnpm versions where possible, and bump pnpm to the latest release.
- package.json: bump `packageManager` to `pnpm@10.33.1` (pinned with
the upstream sha512 integrity hash so corepack/pnpm verify the binary).
- package.json: tighten `engines.node` from `>=22` to `22.14.0` so
dev's built-in node-version validator catches any drift against
dev.yml on every `dev up`.
- dev.yml: bump to `package_manager: pnpm@10.33.1` and add a comment
noting the versions must stay in lockstep with package.json.
- .github/actions/setup: read node from `engines.node` via
`node-version-file: package.json`, and let `pnpm/action-setup`
read the version from the `packageManager` field (drop the hardcoded
`version: 10.28.0` and `node-version: 22.22.1`).
dev.yml itself is plain YAML (no ERB/interpolation) and the node task
requires an explicit `version:` + `package_manager:`, so full
deduplication into a single literal isn't supported upstream. Every
other pnpm-using zone in World mirrors the value. The setup we have
here — package.json as SoT, dev's validator as the enforcer, CI
reading directly from package.json — is the closest equivalent.
Requested by Kieran Osgood <kieran.osgood@shopify.com>
0 commit comments