Skip to content

Remove windows-2019 support and CI as such is no longer supported #778

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

Closed
wants to merge 1 commit into from

Conversation

larouxn
Copy link

@larouxn larouxn commented Jul 15, 2025

I noticed in #777 's CI run that this repo still supports and is trying to run windows-2019 in CI, which is no longer supported. See these logs and below for reference. Thus, I'm proposing we remove support for and CI of windows-2019.

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

From the issue linked above ☝️

We will soon start the deprecation process for Windows 2019. While the image is being deprecated, you may experience longer queue times during peak usage hours. Deprecation will begin on 2025-06-01 and the image will be fully unsupported by 2025-06-30.

For reference, below is the error that occurs when trying to run Windows 2019 CI.

```
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
```
@eregon
Copy link
Member

eregon commented Jul 15, 2025

I am sorry, I missed this and removed it myself in a4f8389.

@eregon eregon closed this Jul 15, 2025
@larouxn
Copy link
Author

larouxn commented Jul 15, 2025

All good! Just glad to see it cleaned up. :)

@larouxn larouxn deleted the burn_windows_2019_ci branch July 15, 2025 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants