update to pnpm@11 - #116
Closed
ben-polinsky wants to merge 1 commit into
Closed
Conversation
ben-polinsky
requested review from
anmolshres98,
aruniverse and
paulius-valiunas
as code owners
July 16, 2026 13:41
aruniverse
approved these changes
Jul 16, 2026
Collaborator
Author
|
Technically, we should drop node 20 support since pnpm@11 doesn't support it... That would require a major bump (technically). |
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
2 participants
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.
npm has retired the audit endpoint (July 15, 2026) pnpm<=10 uses. Update to pnpm 11 is a solution.
pnpm 11 drops support for the package.json pnpm field