Skip to content

Migrate workflows to Windows 2025#4819

Closed
guedou wants to merge 1 commit into
masterfrom
guedou/20250817/gha_windows_2022
Closed

Migrate workflows to Windows 2025#4819
guedou wants to merge 1 commit into
masterfrom
guedou/20250817/gha_windows_2022

Conversation

@guedou
Copy link
Copy Markdown
Member

@guedou guedou commented Aug 17, 2025

Update GitHub Actions workflows to use Windows 2025 as the operating system for running tests.

@gpotter2
Copy link
Copy Markdown
Member

Don't we want 2025?

@guedou guedou force-pushed the guedou/20250817/gha_windows_2022 branch from 7d56f98 to 68bfac8 Compare August 17, 2025 19:55
@guedou guedou changed the title Migrate workflows to Windows 2022 Migrate workflows to Windows 2025 Aug 17, 2025
@guedou
Copy link
Copy Markdown
Member Author

guedou commented Aug 17, 2025

@gpotter2 that's a typo in the title. I wanted to first make sure that windows-2022 is the same as windows-latest.

@codecov
Copy link
Copy Markdown

codecov Bot commented Aug 17, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.99%. Comparing base (d6a25bb) to head (68bfac8).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #4819   +/-   ##
=======================================
  Coverage   80.98%   80.99%           
=======================================
  Files         365      365           
  Lines       89112    89112           
=======================================
+ Hits        72167    72174    +7     
+ Misses      16945    16938    -7     

see 9 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@guedou guedou marked this pull request as ready for review August 18, 2025 11:05
Copy link
Copy Markdown
Member

@gpotter2 gpotter2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I would leave windows-latest.

@guedou
Copy link
Copy Markdown
Member Author

guedou commented Aug 20, 2025

No problem.

This PR main goal was to check that nothing will break with the automatic GitHn change from 2022 to 2025. We can close it.

@gpotter2 gpotter2 closed this Aug 20, 2025
@gpotter2 gpotter2 deleted the guedou/20250817/gha_windows_2022 branch November 2, 2025 22:41
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