Repository navigation
chore: update pnpm to 12.11.2 - #374
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
joshblack
approved these changes
Oct 12, 2026
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The version and integrity hashes are consistent, and the reported build failure is isolated to resource exhaustion.
0 open findings
What changed in this PR
Updates the repository’s Corepack-managed pnpm version from 12.9.1 to 12.11.2.
Changes:
- Updates the canonical pnpm version and integrity hash.
- Regenerates matching pnpm lockfile entries.
| File | Description |
|---|---|
package.json |
Pins pnpm 12.11.2. |
pnpm-lock.yaml |
Updates pnpm and platform executable entries. |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Summary
Updates the pinned pnpm version via Corepack.
pnpm@12.9.1pnpm@12.11.2The new version comes from the stable
latestnpm distribution tag (verified viacorepack use pnpm@latest, which resolved to12.11.2; no prerelease versions were selected).corepack use pnpm@12.11.2regeneratedpackage.json'spackageManagerfield with Corepack's canonical version string and integrity hash, and updatedpnpm-lock.yamlaccordingly (bumping the@pnpm/exe.*platform package entries and thepnpmpackage entry to12.11.2with matching integrity hashes). No dependency versions were changed.Validation
pnpm install --frozen-lockfilepnpm run build005-agent-enables-theme-switching#buildexited with code 137 (OOM kill) during parallel Turbo execution. All other 10 build tasks (including@primer/agent-eval,@primer/agent-eval-website, and other scenario packages) completed successfully. This appears to be a sandbox memory/resource constraint from running many Next.js builds in parallel, not a regression from the pnpm bump — memory was available again immediately afterward.pnpm run format:diffpnpm exec turbo run lintpnpm exec turbo run lint:npmpnpm test --runpnpm exec turbo run type-checkNotes
package.jsonandpnpm-lock.yamlwere modified; no package dependencies were updated.