ci: upgrade runners ubuntu-2004 -> ubuntu-2204 #3510
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We were building binaries on Ubuntu 20.04, which made using those binaries on newer platforms (e.g. Debian Stable 12 Bookworm) throw ssl shared object errors. A few folks reported this problem in Discord. Building on the new runners resolves this problem, at least for Debian Stable. I haven't done a full matrix of platform compatibility, nor do I plan to: listening to reports in Discord is data enough for now. Also bumps cargo-dist 0.4.2 -> 0.5.0. Trying to stay on top of cargo-dist version changes, so we don't get surprised by a large diff. Already tested this version in a private fork and it worked great.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We were building binaries on Ubuntu 20.04, which made using those binaries on newer platforms (e.g. Debian Stable 12 Bookworm) throw ssl shared object errors. A few folks reported this problem in Discord. Building on the new runners resolves this problem, at least for Debian Stable. I haven't done a full matrix of platform compatibility, nor do I plan to: listening to reports in Discord is data enough for now.
Also bumps cargo-dist 0.4.2 -> 0.5.0.
Trying to stay on top of cargo-dist version changes, so we don't get surprised by a large diff. Already tested this version in a private fork and it worked great.