vercel/ncc

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

已关闭

#1,309 创建于 2026年3月1日

在 GitHub 查看
 (4 条评论) (0 个反应) (0 位负责人)JavaScript (273 个派生)batch import
help wanted

仓库指标

星标
 (8,841 个星标)
PR 合并指标
 (平均合并 31天 15小时) (30 天内合并 7 个 PR)

描述

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:

贡献者指南

研究方向
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.
技术栈
javascripttypescriptgithub actions
领域
devopsci cd
议题类型
维护
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
半天
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
活跃
清晰度议题是否清楚说明期望改动、验收标准和下一步。
清晰
前置要求
basic GitHub Actions knowledgeYAML workflow syntax
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
55