bump buildx to v0.12.0 and adapt code to changes #11217
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
glours
force-pushed
the
bump-buildx-v0.12.0
branch
2 times, most recently
from
863f412
to
dfd7017
Compare
Signed-off-by: Guillaume Lours <[email protected]>
glours
force-pushed
the
bump-buildx-v0.12.0
branch
from
dfd7017
to
8a9d220
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #11217 +/- ##
==========================================
+ Coverage 56.78% 56.84% +0.06%
==========================================
Files 133 133
Lines 11491 11491
==========================================
+ Hits 6525 6532 +7
+ Misses 4329 4323 -6
+ Partials 637 636 -1 ☔ View full report in Codecov by Sentry. |
ndeloof
approved these changes
Nov 23, 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.
What I did
Bump to
buildxv0.12.0I did the minimal changes to build, we could, in a follow up PR, decide to use directly the new
DisplayModeinstead of a string (I didn't check possible side effects for now)Related issue
(not mandatory) A picture of a cute animal, if possible in relation to what you did