Skip to content

ci: advance-test windows-2025-vs2026 before GitHub migration#11

Merged
devAsmodeus merged 1 commit into
mainfrom
ci/test-windows-vs2026
May 13, 2026
Merged

ci: advance-test windows-2025-vs2026 before GitHub migration#11
devAsmodeus merged 1 commit into
mainfrom
ci/test-windows-vs2026

Conversation

@devAsmodeus
Copy link
Copy Markdown
Owner

@devAsmodeus devAsmodeus commented May 13, 2026

Summary

  • Adds one matrix entry (python 3.12 + windows-2025-vs2026) to .github/workflows/ci.yml.
  • GitHub will migrate windows-latest to Visual Studio 2026 between 2026-06-08 and 2026-06-15. This PR runs the new image now so we catch any breakage before the rollout.
  • Hope-Hash is pure Python (no C extensions, no MSBuild), so failure is unlikely — but cheap to verify.

Outcome plan

  • If the new job passes: merge, then drop the matrix entry once the migration completes (or leave it as a regression canary).
  • If it fails: pin windows-latestwindows-2022 before 2026-06-08, file follow-up to investigate.

Test plan

  • CI matrix runs, including new windows-2025-vs2026 / python 3.12 job
  • All matrix entries green

🤖 Generated with Claude Code

GitHub will migrate `windows-latest` to Visual Studio 2026 between
2026-06-08 and 2026-06-15. Add a single advance-test matrix entry
(python 3.12 + windows-2025-vs2026) so we know now whether the new
image breaks the build. If green, drop the entry once migration
completes. If red, pin `windows-latest` -> `windows-2022` before
2026-06-08.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@devAsmodeus devAsmodeus merged commit ec494e1 into main May 13, 2026
11 checks passed
@devAsmodeus devAsmodeus deleted the ci/test-windows-vs2026 branch May 13, 2026 07:42
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