chore: fixed pnpm version #1362
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
beniaminmunteanu
requested review from
golobitch,
raducristianpopa,
domin191013,
dragosp1011,
Tymmmy,
lengyel-arpad85 and
sanducb
beniaminmunteanu
changed the title
dragosp1011
approved these changes
Jun 10, 2024
sanducb
approved these changes
Jun 11, 2024
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.
This PR implies having a fixed value for pnpm version
This came up after a discussion on a feature PR:
Having pnpm version at latest would force feature PR's to also either update pnpm themselves, or to merge pnpm update beforehand.
I suggest we do the pnpm updates manually, preferably at the same time with upgrading Rafiki, keeping our version on par with the one used in that codebase.