🔧 chore(deps): update pnpm pin#8
Conversation
- 🔧 move the package manager pin to the current registry release - ✅ verify install and lint with the new pnpm version
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
|
| Filename | Overview |
|---|---|
| package.json | 将 packageManager 从 pnpm@10.33.3 升级至 pnpm@11.0.8，SHA-512 hash 长度正确（128 hex 字符），Node.js >=22.22.1 满足 pnpm 11 的 >=22 要求 |
| pnpm-workspace.yaml | 未随 pnpm 11 升级同步迁移：onlyBuiltDependencies 已在 pnpm 11 中移除，需替换为 allowBuilds: esbuild: true |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["corepack use pnpm@11.0.8"] --> B["读取 package.json\npackageManager 字段"]
B --> C{"SHA-512 hash 验证"}
C -- 通过 --> D["pnpm install --frozen-lockfile"]
C -- 失败 --> E["❌ 安装中止"]
D --> F{"读取 pnpm-workspace.yaml\nonlyBuiltDependencies"}
F -- "pnpm 11: 字段已移除" --> G{"strictDepBuilds\n默认 true"}
G -- "esbuild 不在 allowBuilds" --> H["❌ esbuild 安装脚本报错\n或被静默跳过"]
G -- "迁移为 allowBuilds: esbuild: true" --> I["✅ esbuild 安装脚本正常运行"]
D --> J["pnpm run lint\n✅ 通过"]
Comments Outside Diff (1)
-
pnpm-workspace.yaml, line 1-2 (link)pnpm 11 已移除
onlyBuiltDependenciespnpm 11 完全移除了
onlyBuiltDependencies、onlyBuiltDependenciesFile、neverBuiltDependencies、ignoredBuiltDependencies等旧版构建依赖设置，并以allowBuilds替代。同时，pnpm 11 默认启用strictDepBuilds: true，即所有依赖的安装脚本默认被禁止——若esbuild的 postinstall 脚本在安装时触发而未被allowBuilds声明，pnpm 11 将会报错。此 PR 仅更新了package.json中的packageManager字段，未同步迁移pnpm-workspace.yaml，需将onlyBuiltDependencies替换为等效的allowBuilds配置。
Reviews (1): Last reviewed commit: "🔧 chore(deps): update pnpm pin" | Re-trigger Greptile
1 participant
Summary
Breaking-change risk
Verification