Switch to node 22#3644
Merged
willdurand merged 1 commit intomasterfrom Mar 11, 2026
Merged
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
rpl
approved these changes
Mar 11, 2026
Member
rpl
left a comment
rpl
left a comment
There was a problem hiding this comment.
lgtm, nodejs 20 is going to be EOL soon and so moving nodejs_current to nodejs 22 feels reasonable.
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.
refs mozilla/addons#16064
IIRC we keep the node version in
package.jsonto the previous versionuntil we hit issues because packaging the app for Node 22 shouldn't
really prevent it from running in a Node 20 environment, but maybe I
don't remember very well.