chore: upgrade packageManager to pnpm@11.9.0#504
Open
panish16 wants to merge 6 commits into
Open
Conversation
panish16
force-pushed
the
feat/upgrade-pnpm-v11
branch
2 times, most recently
from
89e3682 to
ffa3656
Compare
panish16
requested review from
kialj876,
pwei1018 and
thorwolpert
as code owners
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
1 participant
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.
Sets
packageManagertopnpm@11.9.0inweb/registry-home/package.jsonas part of the pnpm v11 upgrade (ticket #33875).The Cloud Build CI trigger has already been updated to use
pnpm@11.9.0.