Skip to content

🔧 chore(deps): bump pnpm to 11.20.0 - #44

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

🔧 chore(deps): bump pnpm to 11.20.0#44
xdanger merged 1 commit into
mainfrom
chore/pnpm-11-20-0

Conversation

@xdanger

@xdanger xdanger commented Aug 3, 2026

Copy link
Copy Markdown
Member

Summary

  • update the package manager from pnpm 11.18.0 to 11.20.0
  • adopt pnpm security fixes for named-registry substitution and lockfile path traversal
  • keep the lockfile unchanged because this repository does not configure namedRegistries

Validation

  • frozen install with pnpm 11.20.0
  • full repository lint suite

Risk

Low. This is a same-major, packageManager-only update. pnpm 11.20.0 is semi-breaking only for projects using namedRegistries; no migration is required here.

- 🔧 apply the pnpm registry security fix
@claude

claude Bot commented Aug 3, 2026

Copy link
Copy Markdown

Approved

No issues found. This is a straightforward pnpm version bump (11.18.0 → 11.20.0) with an updated integrity hash. LGTM.

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.

🟢 Ready to approve

The change is a straightforward packageManager-only version bump with no other pnpm version pins found in the repo.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

Updates the repository’s declared package manager version so Corepack/pnpm consumers use pnpm 11.20.0, aligning the repo with the latest same-major release and associated security fixes.

Changes:

  • Bumped packageManager in package.json from pnpm 11.18.0 to 11.20.0 (including the integrity hash).
File summaries
File Description
package.json Updates the pinned pnpm version via the packageManager field to 11.20.0.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

@xdanger
xdanger merged commit 1bcb366 into main Aug 3, 2026
5 checks passed
@xdanger
xdanger deleted the chore/pnpm-11-20-0 branch August 3, 2026 18:56

@chatgpt-codex-connector chatgpt-codex-connector Bot 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 49d41a5470

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread package.json
@@ -1,5 +1,5 @@
{
"packageManager": "pnpm@11.18.0+sha512.33d83c77da82f49fba836925c6f1b841181ec3132b670639bd012f7075f5c7cf634c5f870147c19aae7478fac01df09d8892e880454896edd23ee9b33757563c",
"packageManager": "pnpm@11.20.0+sha512.mm8zCpW2ZEbqCI+vFSFAWooB8H/ecSTMmVjf7VLUu0NnN+ZbCPhfN7Rvy6N1CSVYrFEmK4FoRLIvY0Bu0Wa/7g==",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Encode the Corepack integrity hash as hexadecimal

When Corepack is used, the new base64/SRI suffix is not a valid semver build component because it contains characters such as /, +, and =. With Corepack 0.34.6, even pnpm --version from this repository exits with Invalid package manager specification ... expected a semver version, preventing installs and lint commands from running. Corepack's documented packageManager format uses a hexadecimal hash suffix; convert this SHA-512 value to hex or let corepack use pnpm@11.20.0 generate the field.

Useful? React with 👍 / 👎.

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