🔧 chore(deps): bump pnpm to 11.12.0#38
Merged
Merged
Conversation
- 🔧 keep the package manager current
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s pinned Corepack package manager version in package.json, keeping the project aligned with the current pnpm 11.x line while leaving the lockfile/dependency graph unchanged.
Changes:
- Bump
packageManagerfrompnpm@11.10.0topnpm@11.11.0. - Update the associated Corepack integrity hash in the
packageManagerstring.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- 🔧 keep the package manager current
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.
Summary
Why
This keeps the repository on the current pnpm 11 release after the fresh-release safety window. The change is limited to the Corepack package-manager version and verified integrity hash.
Impact
No dependency ranges, resolved packages, runtime code, or migration steps change.
Validation