Update cloudposse/github-action-docker-promote action to v1 by renovate[bot] · Pull Request #39 · cloudposse/slack-notifier

renovate · 2026-03-20T14:10:52Z

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-docker-promote	action	major	`0.3.0` → `v1.3.1`

Release Notes

cloudposse/github-action-docker-promote (cloudposse/github-action-docker-promote)

`v1.3.1`

Compare Source

Update GitHub Action YAML config query version @goruha (#42)

what

Update GitHub Action YAML config query version

why

Want to get all the minor updates

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#20)

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.3.0`

Compare Source

Upgrade yaml-config-query to v1, assert-action to v3, add test concurrency @[renovate[bot]](https://redirect.github.com/apps/renovate) (#27)

what

Upgrade cloudposse/github-action-yaml-config-query from 0.1.3 to v1.0.0
Upgrade nick-fields/assert-action from v2 to v3.0.0
Quote true/false in jq queries (required by yaml-config-query v1 migration)
Add concurrency settings to all test workflows to prevent parallel runs on the same ref

why

yaml-config-query v1 is a TypeScript rewrite that avoids pulling a Docker image from hub.docker.com and improves performance
v1 requires quoting boolean-like query keys (.true → ."true") due to an upstream jq-tools limitation
assert-action v3 is the latest major version
Test workflow concurrency groups (cancel-in-progress: false) prevent resource contention when multiple test runs target the same commit

Migration notes

The yaml-config-query v1 upgrade is a breaking change for queries containing bare true/false keys. All queries in action.yml have been updated with the required quoting.

chore(deps): update actions/checkout action to v6 - autoclosed @[renovate[bot]](https://redirect.github.com/apps/renovate) (#37)

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	`v4` → `v6`

Release Notes

actions/checkout (actions/checkout)

`v6`

Compare Source

`v5`

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.

chore(deps): update cloudposse/github-action-docker-build-push action to v3 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#40)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-docker-build-push	action	major	`1.14.0` → `v3.0.0`

Release Notes

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

`v3.0.0`

Compare Source

Enhance Docker image summary with structured inspect output @goruha (#98)

what

Replace raw JSON metadata dump in step summary with a rich, structured markdown summary
Add new summary input (default true) to control step summary generation independently from inspect
Add new inspect output exposing the full docker inspect JSON
Change metadata output to use docker/build-push-action metadata directly instead of a separate shell step
Remove the old Get Metadata step entirely
Disable inspect in test workflows (test-docker-build.yml, test-docker-build-multi-platform.yml)
Control DOCKER_BUILD_SUMMARY env var based on inspect and summary inputs

why

The previous raw JSON summary was hard to read in GitHub Actions job summaries
The new format surfaces key image details at a glance: size, architecture, OS, license, tag, digest, revision, source, runtime config, env vars, labels, and layers — each in collapsible sections
Separating summary from inspect gives users finer control over what gets generated

references

https://github.com/docker/build-push-action

`v2.7.0`

Compare Source

Bump cloudposse/github-action-jq from 0.4.0 to 0.4.1 @goruha (#99)

what

Bump cloudposse/github-action-jq from 0.4.0 to 0.4.1

why

Pick up the latest patch release with bug fixes and improvements

references

https://github.com/cloudposse/github-action-jq

chore(deps): update actions/checkout action to v6 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#88)

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	`v5` → `v6`

Release Notes

actions/checkout (actions/checkout)

`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.

chore(deps): update docker/setup-qemu-action action to v4 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#94)

This PR contains the following updates:

Package	Type	Update	Change
docker/setup-qemu-action	action	major	`v3` → `v4`

Release Notes

docker/setup-qemu-action (docker/setup-qemu-action)

`v4`

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.

`v2.6.0`

Compare Source

chore(deps): update docker/setup-buildx-action action to v4 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#95)

This PR contains the following updates:

Package	Type	Update	Change
docker/setup-buildx-action	action	major	`v3` → `v4`

Release Notes

docker/setup-buildx-action (docker/setup-buildx-action)

`v4`

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.

chore(deps): update docker/metadata-action action to v6 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#97)

This PR contains the following updates:

Package	Type	Update	Change
docker/metadata-action	action	major	`v5` → `v6`

Release Notes

docker/metadata-action (docker/metadata-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.

`v2.5.0`

Compare Source

chore(deps): update docker/login-action action to v4 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#93)

This PR contains the following updates:

Package	Type	Update	Change
docker/login-action	action	major	`v3` → `v4`

Release Notes

docker/login-action (docker/login-action)

`v4`

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.

`v2.4.0`

Compare Source

chore(deps): update docker/build-push-action action to v7 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#96)

This PR contains the following updates:

Package	Type	Update	Change
docker/build-push-action	action	major	`v5` → `v7`

Release Notes

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

`v7`

Compare Source

`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.

`v2.3.0`

Compare Source

Fix handling metadata with single quotes (#90) @goruha (#91)

what

Change the way how docker build output metadata is processed to handle escape character

why

Metadata JSON from docker-build-push-action contains head/merge commit details including message which might include single quotes
get-metadata step wraps the JSON in single quotes causing the build step to break if merge commit contains a single quote character (e.g. as part of commit description):

Run metadata=$(echo '{
...
/home/runner/work/_temp/b76bb997-9a9b-4a18-ac9f-321762ea58ba.sh: line 79: syntax error near unexpected token `('
Error: Process completed with exit code 2.

# OR
/home/runner/_work/_temp/5912f8a7-4a6e-4f73-a4c5-b6730c3ebf58.sh: line 456: unexpected EOF while looking for matching `"'
Error: Process completed with exit code 2.

Simple way to reproduce the error locally:

metadata=$(echo '{ "message": "that's fine" }' | jq -c)

The native bash way to escape single quotes would be to replace ' with '', however, GHA provide toJSON method which automatically escape characters when used in ENV (reference below)

references

`v2.2.0`

Compare Source

Update login condition for Docker action @goruha (#87)

what

Update login condition for Docker action

why

Unable to push to ECR via role

references

https://github.com/cloudposse/github-action-docker-build-push/issues/86

`v2.1.0`

Compare Source

Update Docker actions and login condition @goruha (#84)

what

Rollback Docker action to v5
Allow Docker login for ECR

why

The issue with Docker build and GitHub artifact API v4 is still there.
It used to request ECR auth with AWS credentials. But we want to relax this requirement.

references

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

`v2.0.0`

Compare Source

chore(deps): update docker/build-push-action action to v6 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#76)

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.

chore(deps): update dcarbone/install-jq-action action to v3.2.0 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#79)

This PR contains the following updates:

Package	Type	Update	Change
dcarbone/install-jq-action	action	minor	`v3.0.1` -> `v3.2.0`

Release Notes

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

`v3.2.0`

Compare Source

What's Changed

case sensitive is off by @Rupreht in #19
Adding 1.8.0 stuff by @dcarbone in #20

New Contributors

@Rupreht made their first contribution in #19

Full Changelog: dcarbone/install-jq-action@v3.1.1...v3.2.0

`v3.1.1`

Compare Source

What's Changed

1.7.1 for windows and some small cleanup by @dcarbone in #17

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

`v3.1.0`

Compare Source

What's Changed

bumping default to jq 1.7.1 by @dcarbone in #16

Full Changelog: dcarbone/install-jq-action@v3...v3.1.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.

chore(deps): update actions/checkout action to v5 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#82)

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	`v4` -> `v5`

Release Notes

actions/checkout (actions/checkout)

`v5`

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.

🤖 Automatic Updates

Replace Makefile with atmos.yaml @osterman (#83)

what

Remove Makefile
Add atmos.yaml

why

Replace build-harness with atmos for readme genration

References

DEV-3229 Migrate from build-harness to atmos

Replace Makefile with atmos.yaml @osterman (#81)

what

Remove Makefile
Add atmos.yaml

why

Replace build-harness with atmos for readme genration

References

DEV-3229 Migrate from build-harness to atmos

`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)

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

#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/

`v1.15.0`

Compare Source

Use cloudposse version of jq @goruha (#59)

what

Use cloudposse/github-action-jq@0.4.0 instead of edwardgeorge/jq-action@main

why

edwardgeorge/jq-action@main poor supported

chore(deps): update dcarbone/install-jq-action action to v2.1.0 @renovate (#56)

This PR contains the following updates:

Package	Type	Update	Change
dcarbone/install-jq-action	action	minor	`v2.0.2` -> `v2.1.0`

Release Notes

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

`v2.1.0`

Compare Source

What's Changed

Support running action inside containers by @TaxBusby in https://github.com/dcarbone/install-jq-action/pull/10

New Contributors

@TaxBusby made their first contribution in https://github.com/dcarbone/install-jq-action/pull/10

Full Changelog: dcarbone/install-jq-action@v2.0.2...v2.1.0

chore(deps): update nick-fields/assert-action action to v2 @renovate (#58)

This PR contains the following updates:

Package	Type	Update	Change
nick-fields/assert-action	action	major	`v1` -> `v2`

Release Notes

nick-fields/assert-action (nick-fields/assert-action)

`v2`

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.

`v1.2.0`

Compare Source

chore(deps): update nick-fields/retry action to v4 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#41)

This PR contains the following updates:

Package	Type	Update	Change
nick-fields/retry	action	major	`v3` → `v4`

Release Notes

nick-fields/retry (nick-fields/retry)

`v4`

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.

`v1.1.0`

Compare Source

chore(deps): update docker/login-action action to v4 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#38)

This PR contains the following updates:

Package	Type	Update	Change
docker/login-action	action	major	`v3` → `v4`

Release Notes

docker/login-action (docker/login-action)

`v4`

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.

`v1.0.0`

Compare Source

chore(deps): update docker/metadata-action action to v6 @[renovate[bot]](https://redirect.github.com/apps/renovate) (#39)

This PR contains the following updates:

Package	Type	Update	Change
docker/metadata-action	action	major	`v5` → `v6`

Release Notes

docker/metadata-action (docker/metadata-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.

`v0.5.0`

Compare Source

`feature` Retry Logic improvements. @Benbentwo (#35)

This pull request updates the configuration for the promotion retry mechanism in the GitHub Action defined in `action.yml`. The main focus is on making the retry logic more robust and configurable.

Enhancements to retry configuration:

Increased the default value of promote-retry-timeout-seconds from 15 to 3000 to allow more time for retry attempts.
Introduced a new input parameter promote-retry-wait-seconds with a default value of 30, allowing configuration of the wait time between retries.
Updated the runs section to use the new promote-retry-wait-seconds input for retry_wait_seconds.
Changed the retry_on condition from timeout to any, so the action will retry on any failure, not just timeouts.

`v0.4.1`: Retry Logic Improvments

Compare Source

Improvements to Retry exposed parameters and default values

`v0.4.0`

Compare Source

What's Changed

Use GitHub Action Workflows from cloudposse/.github Repo by @osterman in #24
Use GitHub Action Workflows from cloudposse/.github Repo by @osterman in #25
Update release workflow to allow pull-requests: write by @osterman in #26
Update .github/settings.yml by @osterman in #28
Replace Makefile with atmos.yaml by @osterman in #29
Replace Makefile with atmos.yaml by @osterman in #31
Retry logic by @Benbentwo in #33

New Contributors

@osterman made their first contribution in #24
@Benbentwo made their first contribution in #33

Full Changelog: cloudposse/github-action-docker-promote@0.3.0...0.4.0

Configuration

📅 Schedule: (UTC)

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 is behind base branch, 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.

renovate bot force-pushed the renovate/cloudposse-github-action-docker-promote-1.x branch from 03d46a7 to 6760ee9 Compare March 26, 2026 19:53

chore(deps): update cloudposse/github-action-docker-promote action to v1

4cad930

renovate bot force-pushed the renovate/cloudposse-github-action-docker-promote-1.x branch from 6760ee9 to 4cad930 Compare March 26, 2026 23:01

renovate bot changed the title ~~chore(deps): update cloudposse/github-action-docker-promote action to v1~~ Update cloudposse/github-action-docker-promote action to v1 Apr 8, 2026

Uh oh!

Conversation

renovate bot commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

what

why

🤖 Automatic Updates

what

why

what

why

Migration notes

Release Notes

Configuration

Release Notes

what

why

references

what

why

references

Release Notes

Configuration

Release Notes

Configuration

Release Notes

Configuration

Release Notes

Configuration

Release Notes

Configuration

Release Notes

Configuration

what

why

references

what

why

references

what

why

references

Release Notes

Configuration

Release Notes

What's Changed

New Contributors

What's Changed

What's Changed

Configuration

Release Notes

Configuration

🤖 Automatic Updates

what

why

References

what

why

References

🚀 Enhancements

what

why

references

what

why

Screenshot

🤖 Automatic Updates

what

why

Release Notes

What's Changed

What's Changed

Configuration

Release Notes

Configuration

what

why

what

why

renovate bot commented Mar 20, 2026 •

edited

Loading