Skip to content

🔧 chore(deps): update pnpm to 11.18.0 - #43

Merged
xdanger merged 1 commit into
mainfrom
chore/pnpm-11-18-0
Aug 1, 2026
Merged

🔧 chore(deps): update pnpm to 11.18.0#43
xdanger merged 1 commit into
mainfrom
chore/pnpm-11-18-0

Conversation

@xdanger

@xdanger xdanger commented Aug 1, 2026

Copy link
Copy Markdown
Member

Summary

  • update the pnpm package-manager pin from 11.17.0 to 11.18.0
  • keep any mise pnpm pin aligned
  • leave pnpm-lock.yaml unchanged

Validation

  • CI=true pnpm install --frozen-lockfile --ignore-scripts
  • repository-declared lint checks

- 🔧 keep the package manager on the stable pnpm release
@greptile-apps

greptile-apps Bot commented Aug 1, 2026

Copy link
Copy Markdown

Greptile Summary

此 PR 将 package.json 中固定的 pnpm 版本从 11.17.0 更新到 11.18.0,并同步更新 integrity hash。

  • 保持现有 Node.js engine 约束不变
  • 保持 pnpm-lock.yaml 不变

Confidence Score: 5/5

此 PR 看起来可以安全合并,未发现由 pnpm pin 更新引入的具体缺陷。

变更仅更新 pnpm 版本及对应 integrity hash,仓库中没有冲突的 pnpm pin,且提供的 frozen-lockfile 安装验证覆盖了主要变更路径。

Important Files Changed

Filename Overview
package.json pnpm 的 packageManager 版本和 integrity hash 已更新,未发现具体且可触达的故障。

Reviews (1): Last reviewed commit: "🔧 chore(deps): update pnpm to 11.18.0" | Re-trigger Greptile

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates the repository’s pinned pnpm version via the packageManager field in package.json, keeping toolchain pinning consistent while intentionally not modifying the lockfile.

Changes:

  • Bump packageManager from pnpm@11.17.0 to pnpm@11.18.0 (including the associated sha512 value).
  • No changes to pnpm-lock.yaml (per PR intent).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@xdanger
xdanger merged commit 15fba95 into main Aug 1, 2026
6 checks passed
@xdanger
xdanger deleted the chore/pnpm-11-18-0 branch August 1, 2026 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants