Repository navigation
ci: build Arm images on native Arm runners, bump Poetry to 2.5.1 - #496
Merged
Merged
Conversation
nanomad
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
ubuntu-24.04-arminstead of emulating them with QEMU on x86 runners. Same change as Build images for Python 3.15 and use native Arm runners nanomad/docker-poetry#9: the runner (Neoverse-N2) runs 32-bit Arm containers natively, and the arm/v7 build of the poetry base image dropped from 8-13 min to about 2-3 min.nanomad/poetry:2.5.1-python-*base image (DockerfilePOETRY_VERSION).Not exercised yet: the image workflow only runs on version tags, so the first real run will be the next release candidate.