Upgrade buildx
#1041
Merged
Upgrade buildx
#1041
Conversation
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
The `docker/setup-buildx-action@v3` with `version: v0.5.1` is duplicated in 7 actions. The version used for the build system should be specified only once - extracted. Note - this version is [old](https://github.com/docker/buildx/releases/tag/v0.5.1) which is what prompted centralising to make it easier to explore upgrading in future.
This `buildx` version is [5 years old](https://github.com/docker/buildx/releases/tag/v0.5.1) - and not managed by Dependabot. We _could_ update to a newer specific version, but that's still not easily maintainable - instead we should just use `latest` and trust the post-build image smoke tests.
This reverts commit 96ccd5d.
nishaatr
approved these changes
Aug 11, 2025
I don't see that? |
|
Actually, why not dependabot? |
This isn't an action - it's the configuration of an action. Not something dependabot supports. |
ldziedziul
reviewed
Aug 11, 2025
ldziedziul
approved these changes
Aug 12, 2025
JackPGreen
added a commit
that referenced
this pull request
Aug 19, 2025
In #1041, `buildx` was upgraded. [`v10` introduced a breaking change](https://github.com/docker/buildx/releases/tag/v0.10.0), the introduction of `provenance` - this caused the [RedHat publish requests to fail](https://github.com/hazelcast/hazelcast-docker/actions/runs/17074139914/job/48411435645): ``` + echo 'Publishing the image 68a4987ed81a02dbf3d1a549...' ++ curl --fail --silent --show-error --retry 5 --retry-all-errors --request POST --header 'X-API-KEY: ***' --header 'Cache-Control: no-cache' --header 'Content-Type: application/json' --data '{"image_id":"68a4987ed81a02dbf3d1a549" , "operation" : "publish" }' https://catalog.redhat.com/api/containers/v1/projects/certification/id/***/requests/images Publishing the image 68a4987ed81a02dbf3d1a549... curl: (22) The requested URL returned error: 400 ``` Disabling `provenance` addresses this issue. Example execution.
JackPGreen
added a commit
that referenced
this pull request
Aug 21, 2025
In #1041, `buildx` was upgraded. [`v10` introduced a breaking change](https://github.com/docker/buildx/releases/tag/v0.10.0), the introduction of `provenance` - this caused the [RedHat publish requests to fail](https://github.com/hazelcast/hazelcast-docker/actions/runs/17074139914/job/48411435645): ``` + echo 'Publishing the image 68a4987ed81a02dbf3d1a549...' ++ curl --fail --silent --show-error --retry 5 --retry-all-errors --request POST --header 'X-API-KEY: ***' --header 'Cache-Control: no-cache' --header 'Content-Type: application/json' --data '{"image_id":"68a4987ed81a02dbf3d1a549" , "operation" : "publish" }' https://catalog.redhat.com/api/containers/v1/projects/certification/id/***/requests/images Publishing the image 68a4987ed81a02dbf3d1a549... curl: (22) The requested URL returned error: 400 ``` Disabling `provenance` addresses this issue. The root cause of the issue with `provenance` has not been investigated further. [Example execution](https://github.com/hazelcast/hazelcast-docker/actions/runs/17083589973/job/48443063887).
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.
This
buildxversion is 5 years old - and not managed by Dependabot.We could update to a newer specific version, but that's still not easily maintainable - instead we should just use
latestand trust the post-build image smoke tests.Example execution.
Fixes: #1043