GitHub Actions removals · checked
windows-2022 runner deprecated? No date announced (checked 9 Oct 2026)
Windows Server 2022 runner image: no deprecation announced, checked on 9 October 2026. Nothing changes yet. GitHub has announced no deprecation of windows-2022. It keeps two GA images per OS, and Windows Server 2025 and 2022 are the two, so the next Windows Server image to reach GA would start the 2022 image's deprecation. Since June 2026, windows-latest and windows-2025 carry Visual Studio 2026; windows-2022 is where Visual Studio 2022 lives. The fix: Nothing to change yet. Pinning the version keeps the image from moving under you; the scan reports the date the day GitHub announces one. Check your workflows now, with nothing to install: grep -rnE "windows-2022" .github/workflows
$ grep -rnE "windows-2022" .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 2022 runner image
- Matches
- Runner labels
windows-2022, inruns-onor a matrix - Effect
- Nothing yet
- Date
- no dateno deprecation announced (checked 9 Oct 2026)
- After the date
- Nothing changes yet. GitHub has announced no deprecation of windows-2022. It keeps two GA images per OS, and Windows Server 2025 and 2022 are the two, so the next Windows Server image to reach GA would start the 2022 image's deprecation. Since June 2026, windows-latest and windows-2025 carry Visual Studio 2026; windows-2022 is where Visual Studio 2022 lives.
- The fix
- Nothing to change yet. Pinning the version keeps the image from moving under you; the scan reports the date the day GitHub announces one.
Sources
- runner-images: available images (read 9 Oct 2026)
- runner-images #14017: windows-latest uses Visual Studio 2026 (read 9 Oct 2026)
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.
Counted. Thank you; nothing else was sent.Other GitHub Actions removals
- upload-artifact and download-artifact v1 to v3 · stopped working 30 Jan 2025, 617 days ago
- actions/cache v1 and v2, and pins below v3.4.0 or v4.2.0 · stopped working 1 Mar 2025, 587 days ago
- macOS 10.15 runner image · removed 1 Dec 2022, 1408 days ago
- macOS 12 runner image · removed 3 Dec 2024, 675 days ago
- macOS 13 runner image · removed 4 Dec 2025, 309 days ago
- set-env and add-path workflow commands · disabled 16 Nov 2020, 2153 days ago
- Ubuntu 18.04 runner image · removed 3 Apr 2023, 1285 days ago
- Ubuntu 20.04 runner image · removed 15 Apr 2025, 542 days ago
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.