Mish Ushakov
26ee42c10a
Bumps pnpm 9.15.5 → 10.34.5 in all three places it is pinned (`.tool-versions`, the root `packageManager` field, and `codegen.Dockerfile` — pnpm 10 self-manages from `packageManager`, so a mismatched Docker pin would make it re-download itself on every `make generate`) and sets `minimumReleaseAge: 4320` in `pnpm-workspace.yaml`, so a freshly published version is not resolved until it is 3 days old; CI is unaffected because every workflow installs with `--frozen-lockfile` and nothing installs a just-published package. Two pnpm 10 breaking changes needed handling: dependency lifecycle scripts no longer run by default, so `esbuild` and `workerd` are allowlisted via `pnpm.onlyBuiltDependencies` for binary resolution while `bufferutil`, `msw`, and `utf-8-validate` are explicitly declined via `pnpm.ignoredBuiltDependencies` (which also keeps the "Ignored build scripts" warning off every install); and pnpm 10 stopped public-hoisting `*prettier*`/`*eslint*`, which broke `pnpm run format` in both JS packages with `prettier: command not found` — prettier was never declared anywhere and only resolved because pnpm 9 hoisted it out of `json-schema-to-typescript`, so it is now a root devDependency alongside `oxlint`, resolved to the 3.6.2 already in the lockfile for zero formatting churn. `engines.pnpm` moves to `>=10.16.0 <11` so, with `engine-strict`, pnpm 9 fails with an actionable "install the required pnpm version globally" message instead of silently installing. Verified with a clean `node_modules` + `--frozen-lockfile` install and green `lint`, `typecheck`, `format`, and both JS builds, plus a from-scratch re-resolve of the whole tree to confirm `minimumReleaseAgeStrict` (which silently defaults to `true` once the age is set explicitly) does not trap any current range; enforcement was checked empirically — with the setting, `wrangler@^4` resolves to 4.118.0 (6d old) rather than 4.119.0 (1d old). The lockfile diff is limited to the prettier entry plus pnpm 10's importer-section reordering and new `libc:` fields, with no dependency version drift. No changeset: nothing in a published package changed. A follow-up to pnpm 11 is deliberately out of scope — it removes both build-script fields in favor of `allowBuilds`, restricts `.npmrc` to auth/registry settings, and replaces the npm-delegating `pnpm publish`, which the release flow depends on. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
6 lines
61 B
Plaintext
6 lines
61 B
Plaintext
deno 2.8.1
|
|
nodejs 22.18.0
|
|
pnpm 10.34.5
|
|
python 3.10
|
|
uv 0.10.0
|