GitHub Actions removals · checked

windows-2019 runner removed on 30 Jun 2025: what to use instead

Windows Server 2019 runner image: removed 30 Jun 2025, 466 days ago. Jobs that ask for windows-2019 are terminated with an error: the image is gone. The fix: Change runs-on to windows-2025 or windows-2022. Check your workflows now, with nothing to install: grep -rnE "windows-2019" .github/workflows

$ grep -rnE "windows-2019" .github/workflows

Run it from the repository root; it needs nothing installed and sends nothing anywhere. It finds each name as written in your workflow files; a value set in another file and passed in (a matrix from JSON, a reusable workflow's input) needs a look of its own. The fix is in the first paragraph above. The dates come from this data.

The facts

What
Windows Server 2019 runner image
Matches
Runner labels windows-2019, in runs-on or a matrix
Effect
Breaks a job
Announced
15 April 2025
In effect since
30 Jun 2025removed 30 Jun 2025, 466 days ago
After the date
Jobs that ask for windows-2019 are terminated with an error: the image is gone.
The fix
Change runs-on to windows-2025 or windows-2022.
Replace
windows-2019 → windows-2025

Sources

An email before each brownout, for the repos you watch, is not built.

It would re-read your workflows every day and email you a week and a day before each brownout or removal that would hit them, with no change to your repo. agentcheck's free hourly watch covers MCP servers only today. If you would pay for this one, say so with one click. The click is counted; nothing else is sent or stored.

Other GitHub Actions removals

Every removal, by date

actions-eol is a free tool from agentcheck, which runs scheduled checks of your endpoints and alerts you when an answer changes. Dates come from GitHub's own pages, read on the day shown; github.com only, since GitHub Enterprise Server keeps its own schedule.