Add new Dockerfiles for Ubuntu Jammy, Mantic, and Fedora 38 (MinGW) #12
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
janisozaur
approved these changes
Nov 6, 2023
7/mingw32/Dockerfile
Outdated
| @@ -0,0 +1,4 @@ | |||
| FROM fedora:38 | |||
There was a problem hiding this comment.
Fedora 39 is due out tomorrow
There was a problem hiding this comment.
Haha, what timing on my part. Let's wait for the Fedora 39 release, then.
janisozaur
reviewed
Nov 7, 2023
janisozaur
approved these changes
Nov 7, 2023
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.
I've been meaning to add another Ubuntu image to the CI roster since we dropped support for Focal (20.04). Our CI images for MinGW were a bit dated as well, still using Fedora 36.
This PR introduces a new series of Dockerfiles, adding Ubuntu Mantic (23.10) next to Ubuntu Jammy (22.04). In addition, the Fedora image is updated to version 38.
@janisozaur I think some manual action is required to get these available to GitHub Actions. Could you help out with that?