chore: move to pnpm 12.4.2 - #47
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The change is a straightforward pnpm pin bump with consistent lockfile updates and no application dependency re-resolution indicated.
Review effort: Lite
Findings: None
What changed in this PR
Updates the repository’s pinned package manager to keep the toolchain current and reproducible, while preserving the existing dependency resolution/lockfile schema.
Changes:
- Bump
packageManagerinpackage.jsonfrompnpm@12.0.0topnpm@12.4.2. - Update
pnpm-lock.yamlpackageManagerDependenciesentries (and associated@pnpm/exe.*snapshots) to match the new pinned pnpm version.
| File | Description |
|---|---|
| package.json | Updates the pinned packageManager version to pnpm@12.4.2. |
| pnpm-lock.yaml | Refreshes lock entries for the pinned pnpm executable packages to 12.4.2 while keeping lockfileVersion unchanged. |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
🎉 This PR is included in version 2.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Problem
The repo pinned
pnpm@12.0.0; 12.4.2 is current.Solution
Bump
packageManager. The lockfile diff is entirely the pinned pnpm exe entries —packageManagerDependenciestracks pnpm itself, so no application dependency re-resolves andlockfileVersionstays9.0.Proof
pnpm run verifyexit 0: 40 files formatted, no lint warnings in 20 files, smoke{"ok":true,...}, 114 passed / 1 skipped.