chore: bump pnpm to 10.20.0

[feloy]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

The package.json file is updated to upgrade the specified pnpm package manager version from 10.9.0 to 10.20.0, maintaining the same sha512 hash format.

Changes

Cohort / File(s)	Change Summary
Package Manager Version Update package.json	Updates pnpm version constraint from 10.9.0 to 10.20.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided, making it impossible to evaluate whether it relates to the changeset.	Add a pull request description explaining the purpose and impact of the pnpm version bump.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating pnpm from version 10.9.0 to 10.20.0, which matches the package.json modification.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c346bf0 and f30f603.

📒 Files selected for processing (1)

• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Build / windows-2022
• GitHub Check: Build / ubuntu-24.04
• GitHub Check: Build / macos-14
• GitHub Check: Build extension OCI image

🔇 Additional comments (1)

package.json (1)

78-78: Verify the SHA512 hash for [email protected] matches the official npm registry.

pnpm 10.20.0 is a valid release with no breaking changes and is compatible with Node >= 22.0.0. However, ensure the packageManager hash is correct by running npm pack [email protected] and verifying the computed sha512 matches the value in package.json (without the "sha512." prefix). Alternatively, check the official pnpm registry metadata to confirm the hash authenticity for supply-chain integrity.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}