Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

chore: try windows-2025-vs2026 runner ahead of windows-latest VS 2026 migration#17106

Draft
avidit with Copilot wants to merge 2 commits into
masterDynamoDS/Dynamo:masterfrom
copilot/update-workflow-yaml-runs-onDynamoDS/Dynamo:copilot/update-workflow-yaml-runs-onCopy head branch name to clipboard
Draft

chore: try windows-2025-vs2026 runner ahead of windows-latest VS 2026 migration#17106
avidit with Copilot wants to merge 2 commits into
masterDynamoDS/Dynamo:masterfrom
copilot/update-workflow-yaml-runs-onDynamoDS/Dynamo:copilot/update-workflow-yaml-runs-onCopy head branch name to clipboard

Conversation

Copilot AI commented May 13, 2026

Copy link
Copy Markdown
Contributor

GitHub is migrating windows-latest / windows-2025 to default to Visual Studio 2026. This PR proactively pins all Windows CI jobs to windows-2025-vs2026 to validate build compatibility before that rollout lands.

Affected workflows

  • build_dynamo_all.yml
  • build_dynamo_core.yml
  • codeql_analysis.yml
  • dynamo_bin_diff.yml
  • validate_agent_skills.yml

If CI fails on windows-2025-vs2026, the fallback is windows-2022.

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.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.