Skip to content

EOL Node.js 18 (18.20.8) used in windows-latest (windows-2022) #12129

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

Open
2 of 14 tasks
MikeMcC399 opened this issue May 2, 2025 · 2 comments
Open
2 of 14 tasks

EOL Node.js 18 (18.20.8) used in windows-latest (windows-2022) #12129

MikeMcC399 opened this issue May 2, 2025 · 2 comments

Comments

@MikeMcC399
Copy link

Description

Workflows specifying windows-latest currently use windows-2022 with Node.js default 18.20.8. This version of Node.js is no longer supported.

Node.js 18 entered end-of-life status on Apr 30, 2025 and the lowest supported release line is now Node.js 20 (currently Node.js 20.19.1).

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2025

Image version and build link

Image Version: 20250427.1.0

Is it regression?

no

Expected behavior

windows-latest should use a supported version of Node.js as a default - currently Node.js 20

This means either

  • windows-2022 should be updated to Node.js 20 or
  • windows-2025 (default Node.js 22.15.0 LTS) should be declared windows-latest

Actual behavior

windows-latest = windows-2022
Node.js default 18.20.8

Repro steps

  1. Read Node.js end-of-life versions
  2. Read https://github.com/actions/runner-images/blob/main/README.md
  3. Read https://github.com/actions/runner-images/blob/main/images/windows/Windows2022-Readme.md#language-and-runtime
@vidyasagarnimmagaddi
Copy link
Contributor

Hi @MikeMcC399 , Thanks for raising the issue, we will investigate and update .

@MikeMcC399
Copy link
Author

The workaround is to use actions/setup-node to install a supported version of Node.js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants