vercel/ncc

Prepare for GitHub Actions Visual Studio 2026 rollout in `windows-latest`

Open

#1,309 建立於 2026年3月1日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)JavaScript (8,841 star) (273 fork)batch import
help wanted

描述

What would you like?

Monitor rollout of Visual Studio 2026 in GitHub Actions' Windows runner images and ensure CI tests continue to work.

Why is this needed?

  • https://github.com/actions/runner-images/issues/13638 announces Windows Server 2025 with Visual Studio 2026 using the tag windows-2025-vs2026

  • Windows Server 2025 with Visual Studio 2026 image now available for GitHub-hosted runners (Feb 5, 2026) states:

    A new Windows runner image with Visual Studio 2026 is now available in public preview. This dedicated image runs alongside the current windows-2025 image, providing a safe validation path ahead of the default Windows image migration. Visual Studio 2026 will be integrated into the windows-2025 image when it reaches general availability on May 4, 2026.

    You can test against Visual Studio 2026 without disrupting existing pipelines, identify and fix compatibility issues on your timeline, maintain fallback options (like windows-2022) if needed, and plan migrations with full visibility into the upgrade timeline.

    To use the the new runner image, update the runs-on: target in your YAML workflow file to windows-2025-vs2026. For additional information on the available windows runner images, visit our doucmentation (sic).

  • Workflow ci.yml uses windows-latest

  • Repo / workflows are not compatible with Visual Studio 2026

CI test results

GitHub Runner Image Node.js 20 Node.js 22 Node.js 24
windows-2022 fail pass fail
windows-2025 pass pass fail
windows-2025-vs2026 fail fail fail

windows-latest is currently set to windows-2025 and planned for transition to windows-2025-vs2026 on May 4 12 June 8, 2026

The migration to the new Visual Studio 2026 image will start on June 8, 2026.

Suggestions

Short term

In workflow ci.yml

  • drop support for Node.js 20 with EOL transition on 2026-04-30 and then
  • downgrade from windows-latest to windows-2022

Medium term

Investigate possibilities:

貢獻者指南

技術棧
javascripttypescriptgithub actions
領域
devopsci cd
議題類型
chore
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic GitHub Actions knowledgeYAML workflow syntax
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
The issue requires investigating the GitHub Actions runner image transition for Windows, specifically the move from windows 2025 to windows 2025 vs2026. The main file to modify is `.github/workflows/ci.yml`. The issue provides a table of test results and short term and medium term suggestions. The first step is to understand the current CI matrix and decide whether to drop Node.js 20 support and downgrade to windows 2022 in the short term, or to adapt to Visual Studio 2026 and Node.js 24 in the medium term. Check the linked issue #1308 for Node.js 24 support.