Repository navigation
chore: upgrade pnpm 10.32.1 -> 12.5.1 - #112
Merged
Merged
Conversation
Bumps packageManager (verified hash via `corepack use pnpm@12.5.1`, not hand-edited), engines.pnpm floor, .cursor/Dockerfile's pinned version, and AGENTS.md's matching prose. pnpm/action-setup in CI reads the packageManager field automatically, so no workflow changes needed. Also fixes two things this upgrade surfaced: - cddl2ts's cli-examples:local/remote scripts called bare `pnpm run compile` expecting an implicit fallback to the root's compile script. That's not a documented pnpm behavior - it happened to work under pnpm 10 only when nested inside the recursive `pnpm -r` chain (a cold standalone call fails identically on both 10 and 12, with pnpm 10's own error hinting at the real fix). pnpm 12 removed the nested-context fallback entirely, breaking `checks:all`. Now uses the explicit `pnpm -w run compile`, which works on both and doesn't rely on unspecified behavior. - .cursor/Dockerfile only COPYed package.json for 4 of the 6 workspace packages (cddl2swift/cddl2kotlin missing) - pre-existing, unrelated to the pnpm bump, but would have broken `pnpm install --frozen-lockfile` in a fresh Cursor Cloud container today. Added the missing two. Also includes a safe, verified dependency bump surfaced by `pnpm outdated -r`: yargs 18.1.0 -> 18.2.0 (in-range for every package's existing ^18.0.0, `pnpm update` tightened the floor to match). Full checks:all passes under pnpm 12.5.1. See the follow-up summary for the rest of the outdated-dependency analysis (recast, vitest, @vitest/coverage-v8, release-it) - those need an explicit decision before touching, not included here. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps packageManager (verified hash via
corepack use pnpm@12.5.1, not hand-edited), engines.pnpm floor, .cursor/Dockerfile's pinned version, and AGENTS.md's matching prose. pnpm/action-setup in CI reads the packageManager field automatically, so no workflow changes needed.Also fixes two things this upgrade surfaced:
pnpm run compileexpecting an implicit fallback to the root's compile script. That's not a documented pnpm behavior - it happened to work under pnpm 10 only when nested inside the recursivepnpm -rchain (a cold standalone call fails identically on both 10 and 12, with pnpm 10's own error hinting at the real fix). pnpm 12 removed the nested-context fallback entirely, breakingchecks:all. Now uses the explicitpnpm -w run compile, which works on both and doesn't rely on unspecified behavior.pnpm install --frozen-lockfilein a fresh Cursor Cloud container today. Added the missing two.Also includes a safe, verified dependency bump surfaced by
pnpm outdated -r: yargs 18.1.0 -> 18.2.0 (in-range for every package's existing ^18.0.0,pnpm updatetightened the floor to match).Full checks:all passes under pnpm 12.5.1. See the follow-up summary for the rest of the outdated-dependency analysis (recast, vitest, @vitest/coverage-v8, release-it) - those need an explicit decision before touching, not included here.