Update cloudposse/github-action-docker-build-push action to v1.17.2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-docker-build-push	action	minor	1.15.0 -> v1.17.2

---

Release Notes

cloudposse/github-action-docker-build-push (cloudposse/github-action-docker-build-push)

v1.17.2

Compare Source

🚀 Enhancements

Rollback docker/build-push-action to v5 @​goruha (#​75)

what

• Rollback docker/build-push-action to v5

why

• docker/build-push-action@v6 is not compatible with actions/download-artifact@v4

references

• https://github.com/docker/build-push-action/issues/1167

v1.17.1

Compare Source

Output metadata to job summary @​osterman (#​60)

what

• Output Docker Metadata in fenced code block
• Example https://github.com/cloudposse/github-action-docker-build-push/actions/runs/7944946825

why

• Make it easy to see what was produced

Screenshot

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​63)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v1.17.0

Compare Source

chore(deps): update dcarbone/install-jq-action action to v3 @​renovate (#​73)

This PR contains the following updates:

Package	Type	Update	Change
dcarbone/install-jq-action	action	major	v2.1.0 -> v3.0.1

---

Release Notes

dcarbone/install-jq-action (dcarbone/install-jq-action)

v3.0.1

Compare Source

What's Changed

• Use sh in action by @​​dcarbone in https://github.com/dcarbone/install-jq-action/pull/15

Full Changelog: dcarbone/install-jq-action@v3.0.0...v3.0.1

v3.0.0

Compare Source

What's Changed

• updating matrix versions by @​​dcarbone in https://github.com/dcarbone/install-jq-action/pull/12
• trying out posix sh by @​​dcarbone in https://github.com/dcarbone/install-jq-action/pull/14

Full Changelog: dcarbone/install-jq-action@v2...v3.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

v1.16.1

Compare Source

chore(deps): update docker/build-push-action action to v6 @​renovate (#​67)

This PR contains the following updates:

Package	Type	Update	Change
docker/build-push-action	action	major	v5 -> v6

---

Release Notes

docker/build-push-action (docker/build-push-action)

v6

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

ref: default to public ECR for binfmt and buildx @​dudymas (#​72)

what

• ref(qemu-setup): set to public ecr
• ref(diver-opts): hard set to public ecr
• chore(driver-opts,binfmt): update inputs for ecr defaults

why

• Docker hub rate limits can cause issues with more active projects/workflows

feat: add support for build-contexts (#​70) @​goruha (#​71)

what

• Adds support for the build-contexts arg

why

• This is needed in particular circumstances; see https://docs.docker.com/reference/cli/docker/buildx/build/#build-context

references

• https://github.com/cloudposse/github-action-docker-build-push/pull/70

Confirmed on a private project:

🐛 Bug Fixes

fix: create unique image tags for each test in order to avoid race conditions between tests @​korenyoni (#​74)

what

• create unique image tags for each test in order to avoid race condititions

why

This assertion fails because of a race condition between the three tests in this repo.

For example, take a look at this renovate PR:

The manifest produced by each commit in the screenshot are as follows, in order from oldest to newest:

$ docker buildx imagetools inspect registry.hub.docker.com/cloudposse/github-action-docker-build-push:sha-61a55ff023a1813dca90b5ddc2becbb248ff79b9 --raw | jq '.manifests | map(select(.platform.architecture != "unknown") | .platform.os + "/" + .platform.architecture)'
[
  "linux/amd64",
  "linux/arm64"
]
$ docker buildx imagetools inspect registry.hub.docker.com/cloudposse/github-action-docker-build-push:sha-c5f9ccf5aad31e6d255ea1631a4dc2311d88452e --raw | jq '.manifests | map(select(.platform.architecture != "unknown") | .platform.os + "/" + .platform.architecture)'
[
  "linux/amd64"
]
$ docker buildx imagetools inspect registry.hub.docker.com/cloudposse/github-action-docker-build-push:sha-fd863042e23edb3cdea14cd459f4307ed2b29f3d --raw | jq '.manifests | map(select(.platform.architecture != "unknown") | .platform.os + "/" + .platform.architecture)'
[
  "linux/amd64",
  "linux/arm64"
]

As previously mentioned, there is a race condition between the three tests that get dispatched by this action. They all produce an image tag of sha-[sha]. That means that if the test-docker-build-multi-platform.yml build finishes before the test-docker-build.yml build, the multi-platform manifest will be overwritten by the single-platform image.

references

N/A

🤖 Automatic Updates

Update .github/settings.yml @​osterman (#​69)

what

• Update .github/settings.yml
• Drop .github/auto-release.yml files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update release workflow to allow pull-requests: write @​osterman (#​66)

what

• Update workflow (.github/workflows/release.yaml) to have permission to comment on PR

why

• Add comment to PR when it is released

Use GitHub Action Workflows from `cloudposse/.github` Repo @​osterman (#​65)

what

• Update workflows (.github/workflows/settings.yaml) to use shared workflows from .github repo

why

• Reduce nested levels of reusable workflows

Use GitHub Action Workflows from `cloudposse/.github` Repo @​osterman (#​64)

what

• Update workflows (.github/workflows/settings.yaml)

why

• Support new readme generation workflow.
• Generate banners

v1.16.0

Compare Source

Feature: Variable Passthrough & Debug input @​Benbentwo (#​62)

what

• Pass through variables for allow, network, buildkitd-flags, and driver-opts
• Input for debug which adds a debug flag to buildx

why

• Debugging and allowing users to fully customize the build setup

references

• Solves occasional networking issue

v1.15.1

Compare Source

docs: Recommend ECR instead of GHA for buildx caching, update README using `cloudposse/build-harness` @​korenyoni (#​61)

what

• Recommend ECR instead of GHA for buildx caching

why

• ECR remote caching is more appropriate in an AWS environment, as it can lead to better performance (and potentially lower costs if an ECR VPC endpoint is used in conjunction with hosted GHA runners).

references

• https://aws.amazon.com/blogs/containers/announcing-remote-cache-support-in-amazon-ecr-for-buildkit-clients/

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.