Skip to content

for windows ci tests migrate to windows-2025-vs2026 base image#2

Merged
IlmLV merged 1 commit into
mainfrom
feature/windows-base-image-migration
May 16, 2026
Merged

for windows ci tests migrate to windows-2025-vs2026 base image#2
IlmLV merged 1 commit into
mainfrom
feature/windows-base-image-migration

Conversation

@IlmLV
Copy link
Copy Markdown
Owner

@IlmLV IlmLV commented May 16, 2026

As previously announced, the "windows-latest" and “windows-2025” labels in GitHub Actions will be migrated to use Visual Studio 2026 by default.

This change will be rolled out over a week beginning June 8, 2026 and will complete by June 15, 2026.

During this period your workflows will gradually switch over to the new image with Visual Studio 2026 as the default. If you want to do advance testing prior to the migration, you can follow the instructions below.

[IMPORTANT] The switch to Visual Studio 2026 may break your workflows if you depend on Visual Studio 2022.

What you need to do:

You do not need to do anything at this time if you want your workflows to migrate to the latest Visual Studio version.

If you want to test the new image:

update the runs-on: target in your YAML workflow file to windows-2025-vs2026.

If you want to remain on VS 2022:

update the runs-on: target in your YAML workflow file to windows-2022.

For more information or if you have questions head to the runner-images repository.

@IlmLV IlmLV self-assigned this May 16, 2026
@IlmLV IlmLV merged commit 44445a8 into main May 16, 2026
3 checks passed
@IlmLV IlmLV deleted the feature/windows-base-image-migration branch May 16, 2026 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant