Upgrade PNPM to latest version #731
Merged
Conversation
This file contains 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
The PNPM version was ancient (released ~4 years ago) thus it commit upgrades it to the latest version. This also helps us ensure consistency in our package managers and JS/TS projects across our organization.
|
I see the CIs are failing, I will update them once I have time 👍 |
This upgrade the `pnpm/action-setup` action to latest, and removes the explicit `version` field in order to tell it to read `packageManager` field in the `package.json`.
Node.js v16 is not supported by latest version of PNPM, and Node.js 16 is EOL thus it is now removed in favor of v18.
NyanKiyoshi
force-pushed
the
deps/update-pnpm
branch
from
60db0ec to
5e24640
Compare
krzysztofzuraw
approved these changes
Feb 18, 2025
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.
The PNPM version was ancient (released ~4 years ago) thus it commit upgrades it to the latest version. This also helps us ensure consistency in our package managers and JS/TS projects across our organization.
Changes were tested locally:
pnpm build✅pnpm test✅pnpm lint✅Changes made:
actions/setup-nodeandpnpm/action-setupversion to latest (to ensure compatibility with more recent engines and to fix techdebt)versionfield forpnpm/action-setup, instead it will readpackageManagerfield in thepackage.jsonI have: