chore: update pnpm to v12 - #872
Merged
Merged
Conversation
Co-authored-by: fengmk2 <156269+fengmk2@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
fengmk2
August 18, 2026 14:22
View session
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #872 +/- ##
=======================================
Coverage 94.24% 94.24%
=======================================
Files 10 10
Lines 747 747
Branches 235 235
=======================================
Hits 704 704
Misses 40 40
Partials 3 3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s package manager tooling by pinning pnpm v12 via packageManager and regenerating the lockfile accordingly, aligning local development and CI installs with pnpm 12’s new lockfile behavior.
Changes:
- Bumped
packageManagerinpackage.jsonfrompnpm@11.20.0topnpm@12.0.0-rc.7. - Regenerated
pnpm-lock.yamlwith pnpm 12, introducing the new multi-document YAML stream format (environment lockfile + dependency graph).
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pnpm-lock.yaml | Regenerated with pnpm 12; now includes a new first YAML document that pins the pnpm toolchain itself. |
| package.json | Updates the packageManager pin to pnpm 12 so Corepack / setup tooling selects the intended pnpm version. |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates pnpm from v11 (
11.20.0) to v12 (12.0.0-rc.7, the latest v12 release — v12 currently ships only pre-releases on thenext-12dist-tag).Changes
package.json— bumpedpackageManagertopnpm@12.0.0-rc.7; this pin drives Corepack andpnpm/action-setup(which reads it when no explicit version is set, as in the CodSpeed workflow)pnpm-lock.yaml— regenerated with pnpm 12Lockfile format note
pnpm 12 now writes
pnpm-lock.yamlas a multi-document YAML stream:The first document is the new "environment lockfile" pinning the package manager itself (
packageManagerDependencies); the second holds the project dependency graph.lockfileVersionstays'9.0'and dependency resolution is unchanged. Tooling that parses the lockfile must read all YAML documents rather than only the first.