You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Outdated and broken runner image links in the GitHub-hosted runners tables #46946
What part(s) of the article would you like to see updated?
The runner label tables come from data/reusables/actions/supported-github-runners.md. Some README links in them point to the wrong image, one returns a 404, and one label is missing from the private repositories table.
In the private repositories table, windows-11-vs2026-arm links to Windows11-Arm64-VS2026-Readme.md, which returns a 404. The file is named Windows11-VS2026-Arm64-Readme.md, and the public table already links to it.
In both tables, windows-latest and windows-2025 link to Windows2025-Readme.md. The runner-images README lists windows-latest, windows-2025 and windows-2025-vs2026 as one image and links all three to Windows2025-VS2026-Readme.md (changed in Remove duplicate Windows Server 2025 entry actions/runner-images#14330).
windows-2025-vs2026 appears in the public repositories table but not in the private one. The runner-images README doesn't limit it to public repositories.
The old README files for items 2 and 3 still exist, so those links don't 404. They describe a different image, though: the old pages list Visual Studio 2022, and the runners have Visual Studio 2026.
Expected outcome: each label links to the README of the image it runs on, and both tables list the same labels.
Additional information
I checked every runner-images link in the file. These are the only ones that are broken or point to the wrong image, and no other page in the docs links to the outdated READMEs. I'd like to open a pull request with these changes.
Activity