Skip to content

use windows-2025 github runners#6189

Open
Fedr wants to merge 5 commits into
masterfrom
github/windows-2025
Open

use windows-2025 github runners#6189
Fedr wants to merge 5 commits into
masterfrom
github/windows-2025

Conversation

@Fedr
Copy link
Copy Markdown
Contributor

@Fedr Fedr commented May 30, 2026

No description provided.

Fedr and others added 4 commits May 30, 2026 17:17
Resolve the VS install path at runtime instead of hardcoding the 2022
Enterprise path, which does not exist on windows-2025 runners.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Pin the VS2022 vcpkg triplet and the matching v143 toolset so the
windows-2025 runner doesn't implicitly pick up a newer toolset. v143
keeps MRCudaVersion at 12.0 (source/platform.props) to match the
installed CUDA 12.0 BuildCustomizations. The triplet is wired through
vcpkg setup, the MSBuild build, and the MRBind generate step.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The same vswhere-based VS lookup was duplicated in build-test-windows
and pip-build. Move it to .github/actions/locate-visual-studio, which
still exports VC_PATH for later steps and also exposes a `path` output.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Replace the single windows-latest runner with a matrix of windows-2022
and windows-2025 so the wheel is exercised on both the image that built
it and the previous one.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant