chore(deps): bump pnpm to 11.3.0#24
Conversation
- 🔧 keep package-manager pin current without lockfile churn
|
✅ Approved Scope: Single-line No new findings. This is a minimal, low-risk dependency version bump with no lockfile churn and no code changes. CI static analysis checks are passing. |
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s Corepack packageManager pin to use pnpm@11.3.0, keeping the toolchain version consistent for installs and scripts.
Changes:
- Bump
packageManagerfrompnpm@11.2.2topnpm@11.3.0(with updated integrity hash).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
| Filename | Overview |
|---|---|
| package.json | 将 packageManager 字段从 pnpm@11.2.2 升级至 pnpm@11.3.0,同时更新对应的 SHA512 校验哈希值,无其他改动。 |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["开发者运行 corepack pnpm install"] --> B{"corepack 读取 packageManager 字段"}
B --> C["验证 SHA512 哈希\npnpm@11.3.0"]
C --> D{"哈希匹配?"}
D -- 是 --> E["下载 / 使用缓存的 pnpm 11.3.0"]
D -- 否 --> F["安装失败,拒绝继续"]
E --> G["--frozen-lockfile 安装依赖"]
G --> H["pnpm run lint 通过"]
H --> I["✅ 升级完成"]
Reviews (1): Last reviewed commit: "🔧 chore(deps): bump pnpm to 11.3.0" | Re-trigger Greptile
Summary
packageManagerpin frompnpm@11.2.2topnpm@11.3.0pnpm-lock.yamlunchanged because the frozen install stayed currentVerification
corepack pnpm install --frozen-lockfilecorepack pnpm run lintcorepack pnpm outdated --format json->{}Risk
pnpm@11.3.0keeps the same Node floor (>=22.13), while this repo requires Node>=22.22.1and was validated on Node24.16.0.