Skip to content

chore(ci): update runners, removing windows-2019 and adding windows-2025 #1672

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

Conversation

KevinEady
Copy link
Contributor

Remove windows-2019 as it has been removed from GitLab-hosted runners. Example failed run shows:

Windows Server 2019 has been retired. The Windows Server 2019 image has been removed as of 2025-06-30. For more details, see actions/runner-images#12045

Add the most recent Windows runner, windows-2025.

@KevinEady
Copy link
Contributor Author

question: do we need windows-2025? I think we added windows-2019 because there was some MSVC compilation issues in 2019 that we wanted to solve and test against. Could we just use windows-latest (which resolves to windows-2022, see docs).

@miguelmarcondesf
Copy link
Contributor

question: do we need windows-2025? I think we added windows-2019 because there were some MSVC compilation issues in 2019 that we wanted to solve and test against. Could we just use windows-latest (which resolves to windows-2022, see docs).

The blame doesn't provide much context about when windows-2019 was added, only stating "Revert window CI to running on 2019".
It makes sense to use windows-latest like you mentioned, reading the issue related to runner-images, it seems to be the standard approach to maintain only the latest two stable versions.

@legendecas
Copy link
Member

Given that the test is passed, i think it is fine to keep with windows-2025 as it tests newer version of windows.

@legendecas legendecas merged commit 2941941 into nodejs:main Jul 1, 2025
53 checks passed
@github-project-automation github-project-automation bot moved this from Need Triage to Done in Node-API Team Project Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

3 participants