Skip to content

chore: bump pnpm to 11.1.2 #1609

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Boshen wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

chore: bump pnpm to 11.1.2 #1609

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2d09bb7
chore: bump pnpm to 11.1.2
Boshen May 17, 2026
8f2f56b
chore: dedupe lockfile
fengmk2 May 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,5 +44,5 @@
"engines": {
"node": ">=22.18.0"
},
"packageManager": "pnpm@10.33.2"
"packageManager": "pnpm@11.1.2"
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep pnpm version pins aligned across workspaces

Updating only the root packageManager to pnpm@11.1.2 introduces a split with docs/package.json (still pnpm@10.33.2), so Corepack will run different pnpm majors depending on the working directory (cd docs vs repo root). This makes local docs installs and CI docs installs (pnpm -C docs ... from root) non-reproducible across environments and can lead to lockfile/behavior drift that is hard to diagnose.

Useful? React with 👍 / 👎.

}
Loading
Loading