Skip to content

chore(deps): bump node from v20 to v22 #27879

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 1, 2025
Merged

chore(deps): bump node from v20 to v22 #27879

merged 1 commit into from
Jul 1, 2025

Conversation

caugner
Copy link
Contributor

@caugner caugner commented Jul 1, 2025

Description

Bumps Node.js from v20 to v22.

Motivation

Node.js v22 is the currently active LTS version.

Additional details

Related issues and pull requests

Same as: mdn/content#40141

Part of mdn/mdn#699.

@caugner caugner requested a review from bsmth July 1, 2025 07:59
@caugner caugner requested a review from a team as a code owner July 1, 2025 07:59
@github-actions github-actions bot added the system Infrastructure and configuration for the project label Jul 1, 2025
Copy link
Member

@bsmth bsmth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ty!

@yin1999
Copy link
Member

yin1999 commented Jul 1, 2025

CIs in #27880 failed. I'm going to merge this for now.

@yin1999 yin1999 merged commit 51aecf3 into main Jul 1, 2025
12 checks passed
@yin1999 yin1999 deleted the node-22 branch July 1, 2025 09:19
@caugner
Copy link
Contributor Author

caugner commented Jul 1, 2025

CIs in #27880 failed. I'm going to merge this for now.

Thanks!

We should probably fix and detangle those workflows so that they use the right node version depending on whether the workflow step runs in the content or translated-content checkout. I just did the same for yari.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
system Infrastructure and configuration for the project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants