Conversation
joaopedrodcf
approved these changes
May 5, 2026
Contributor
joaopedrodcf
left a comment
joaopedrodcf
left a comment
There was a problem hiding this comment.
Maybe we can in another PR increase the version of node to 22 and migrate to pnpm 11
Collaborator
Author
We could definitely consider bumping v3 to 22 now 20 is EOL! Let's think about it in a follow up as we need to consider consumers of |
gameroman
approved these changes
May 5, 2026
Collaborator
Author
|
yolo |
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
4 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.
🔗 Linked issue
n/a
📚 Description
Switch the repo to use pnpm as it's currently npm. I picked pnpm 10 as we still support Node 20 and pnpm 11 doesn't.