Live
Cloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AICloudflare Images Analytics Dashboard Adds 30‑Day Delivery VisibilityAmazon ECS Adds Native Blue/Green, Canary, and Linear Deployments for Safer Container RolloutsGemini agentic tools add LLM‑driven automation to Partner Marketing StudioGitHub Actions makes RHEL 9/10 runner images generally available for larger workloadsIntegrating Decider Models to Reduce Latency and Cost in AI Agent WorkflowsAWS Emulator Enables Local Testing of 200+ Services, but Lacks IAM ValidationSageMaker AI monitoring adds automatic latency drift, idle GPU, and configuration gap detection for inference endpointsEmbedding Proactive Governance into Enterprise‑Scale Agentic AI
GitHub

GitHub Hosted Windows ARM64 Runners Shift to Visual Studio 2026

AI SummaryPowered by AI

The GitHub-hosted windows-11-arm runner image has been updated with Visual Studio 2026 and is now generally available for standard and larger runners. Practitioners must proactively update workflow definitions or risk breaking pipelines during the mandatory migration window starting September 21, 2026.

GitHub Actions workflows running on Windows ARM architecture are facing a significant infrastructure shift as Visual Studio 2026 becomes available in standard and larger hosted runners. This change is not merely an update; it represents a hardening of the build environment that will force all existing pipelines to adapt or fail by late September.

What Changed

The windows-11-vs2026-arm runner image has reached general availability. While GitHub plans to gradually migrate workflows currently using the legacy windows-11-arm image (which relies on Visual Studio 2022) by September 30, 2026, this transition is a breaking change for any workflow dependent on specific tooling from VS2022.

To prepare immediately without waiting for GitHub's automated rollout, engineers should update their runs-on target in the YAML file to explicitly use windows-11-vs2026-arm. This allows teams to validate compatibility before the forced migration begins on September 21.

Mitigation and Migration Strategy

If your organization intends to continue using Visual Studio 2022, you must take active steps now. For standard runners, this involves editing workflow files to target a different runner image that supports the legacy environment. Similarly, for larger runners assigned specific images, administrators need to change the underlying configuration.

Teams should consult the DevOps pillar resources regarding how to handle these infrastructure dependencies in their CI/CD pipelines before September 21st arrives.

What This Means For Practitioners

This update highlights a critical operational risk: relying on default runner images without explicit versioning can lead to unexpected pipeline failures. Platform teams must audit all workflows using Windows ARM runners and decide whether they require the legacy Visual Studio 2026 environment or if an alternative image is necessary.

Originally published atGitHub Changelog