Skip to content

Conversation

@KATO-Hiro
Copy link
Collaborator

@KATO-Hiro KATO-Hiro commented Jan 18, 2026

close #3062

Summary by CodeRabbit

  • Documentation

    • Reworked dev notes into an upgrade-focused resolution: renamed and expanded the guidance for moving to pnpm v10.28.0, clarified commands and packageManager updates, replaced workaround emphasis with a concise upgrade narrative, and added explicit verification results for dev, tests, and build.
  • Chores

    • Updated pnpm package manager to v10.28.0.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Jan 18, 2026

Walkthrough

This PR updates pnpm from v10.26.2 to v10.28.0 in package.json and replaces a downgrade-focused doc with an upgrade-focused dev note documenting the 10.27 regression and the recommended resolution via upgrading to v10.28.0, including verification steps and success results.

Changes

Cohort / File(s) Summary
pnpm Version Upgrade
package.json
Updated packageManager field from pnpm@10.26.2 to pnpm@10.28.0.
Regression Documentation
docs/dev-notes/2026-01-02/pnpm-10.27-regression/report.md
Reworked report to emphasize upgrade to v10.28.0: renamed resolution section, added v10.28.0 patch details and behavioral change (store/project registry handling), replaced downgrade workaround with upgrade procedure (package.json/packageManager changes and commands), updated verification/results, and reorganized supporting references.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 A tiny hop to ten-point-eight,
I nibbled bugs and changed the state.
Docs refreshed and versions clear,
The registry sings, the path is near.
Upgrade done — let carrots cheer! 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Out of Scope Changes check ⚠️ Warning The PR includes changes to both package.json (pnpm version bump) and a documentation file (report.md with upgrade-focused updates), which extends beyond the stated scope of bumping pnpm version in package.json only. Remove the documentation file changes or clarify in the PR objectives whether documentation updates are intended as part of this version bump.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating pnpm from 10.27 to 10.28 in package.json, which is the primary objective of the PR.
Linked Issues check ✅ Passed The PR successfully updates package.json to reference pnpm 10.28.0 as required by issue #3062, fulfilling the linked issue requirement.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

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

Copy link
Collaborator Author

@KATO-Hiro KATO-Hiro left a comment

Choose a reason for hiding this comment

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

LGTM

@KATO-Hiro KATO-Hiro merged commit 7c16748 into staging Jan 18, 2026
4 checks passed
@KATO-Hiro KATO-Hiro deleted the #3062 branch January 18, 2026 06:48
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.

[Chore] Bump pnpm from 10.27 to 10.28 in package.json

2 participants