Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update windows runner in release workflow #402

Merged
merged 1 commit into from
Apr 28, 2022
Merged

Conversation

bertschneider
Copy link
Contributor

windows-2016 runners were removed (actions/runner-images#4312).

@fmeum
Copy link
Contributor

fmeum commented Apr 28, 2022

The idea behind the choice of release runners is that the binaries we generate with them should be as compatible as possible. Ideally, this would mean using the oldest still supported version of each OS.

@bertschneider
Copy link
Contributor Author

Then we should probably also test changes with the oldest versions in addition to the newest ones. I reverted the PR to only update the runner from windows-2016 to windows-2019.

@bertschneider bertschneider changed the title Use same runners in release as in test workflow Update windows runner in release workflow Apr 28, 2022
@fmeum fmeum merged commit 3b40a06 into main Apr 28, 2022
@fmeum fmeum deleted the update-release-workflow branch April 28, 2022 14:22
@fmeum
Copy link
Contributor

fmeum commented Apr 28, 2022

@bertschneider We could also set up the release flow to run the test suite before actually producing release binaries. The macOS runners are already flaky enough that introducing another factor of 2 to our test matrix could be a net negative. It's very unlikely that tests would break on older OS versions after all.

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