🔧 chore(deps): bump pnpm#19
Conversation
- 🔧 align Corepack pin with current pnpm release
|
✅ Approved No new issues found. This is a clean, single-line bump of the Corepack pnpm pin from 10.33.4 → 11.1.2. Notes:
LGTM. |
|
| Filename | Overview |
|---|---|
| package.json | 将 pnpm 从 10.33.4 升级到 11.1.2,并更新了 SHA-512 校验哈希;缺少 engines 字段来声明 pnpm 11 引入的 Node.js >= 22 要求。 |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Developer runs pnpm command] --> B{Corepack checks packageManager field}
B --> C[pnpm 11.1.2 SHA verified]
C --> D{Node.js version check}
D -->|Node 22+| E[OK - pnpm 11 supported]
D -->|Node 18 or 20| F[ERROR - unsupported Node version]
E --> G[pnpm install frozen-lockfile]
G --> H[lockfile v9.0 read compatible]
H --> I[Dependencies installed]
Reviews (1): Last reviewed commit: "🔧 chore(deps): bump pnpm" | Re-trigger Greptile
There was a problem hiding this comment.
Pull request overview
This PR bumps the repository’s Corepack packageManager pin to pnpm 11.1.2, updating the toolchain version used for installs and scripts.
Changes:
- Update
packageManagerinpackage.jsonfrom pnpm 10.33.4 to pnpm 11.1.2 (Corepack pin).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -1,5 +1,5 @@ | |||
| { | |||
| "packageManager": "pnpm@10.33.4+sha512.1c67b3b359b2d408119ba1ed289f34b8fc3c6873412bec6fd264fbdc82489e510fcbecb9ce9d22dae7f3b76269d8441046014bdca53b9979cd7a561ad631b800", | |||
| "packageManager": "pnpm@11.1.2+sha512.415a1cc25974731e75455c1468371be74c5aa5fb7621b50d4056d222451609f11412f23fd602e6169f1e060466641f798597e1be961a10688836a67b16569499", | |||
| @@ -1,5 +1,5 @@ | |||
| { | |||
| "packageManager": "pnpm@10.33.4+sha512.1c67b3b359b2d408119ba1ed289f34b8fc3c6873412bec6fd264fbdc82489e510fcbecb9ce9d22dae7f3b76269d8441046014bdca53b9979cd7a561ad631b800", | |||
| "packageManager": "pnpm@11.1.2+sha512.415a1cc25974731e75455c1468371be74c5aa5fb7621b50d4056d222451609f11412f23fd602e6169f1e060466641f798597e1be961a10688836a67b16569499", | |||
There was a problem hiding this comment.
pnpm 11 要求 Node.js >= 22(放弃对 Node 18/20 的支持),但
package.json 中没有 engines 字段来声明这个约束。使用 Node 18 或 20 的开发者在 Corepack 激活后会遇到不清晰的错误,而不是明确的版本不兼容提示。PR 描述中已经提到了这个风险,建议在 manifest 中显式记录。
| "packageManager": "pnpm@11.1.2+sha512.415a1cc25974731e75455c1468371be74c5aa5fb7621b50d4056d222451609f11412f23fd602e6169f1e060466641f798597e1be961a10688836a67b16569499", | |
| "packageManager": "pnpm@11.1.2+sha512.415a1cc25974731e75455c1468371be74c5aa5fb7621b50d4056d222451609f11412f23fd602e6169f1e060466641f798597e1be961a10688836a67b16569499", | |
| "engines": { | |
| "node": ">=22.13" | |
| }, |
Summary\n- Bump the Corepack pnpm pin from 10.33.4 to 11.1.2.\n\n## Validation\n- pnpm install --frozen-lockfile\n- pnpm outdated --format json => {}\n- pnpm run lint\n\n## Risk\n- pnpm 11 requires Node >=22.13; this repo does not declare a stricter Node engine.