Update cloudposse/github-action-docker-image-exists action to v0.2.0 by renovate[bot] · Pull Request #67 · cloudposse-archives/github-actions-workflows

renovate · 2023-07-03T22:32:15Z

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-docker-image-exists	action	minor	`0.1.0` -> `0.2.0`

Release Notes

cloudposse/github-action-docker-image-exists (cloudposse/github-action-docker-image-exists)

`v0.2.0`

Compare Source

Update cloudposse/github-action-docker-build-push action to v1.14.0 @renovate (#15)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-docker-build-push	action	minor	`1.13.0` -> `1.14.0`

Release Notes

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

`v1.14.0`

Compare Source

chore(deps): update docker/metadata-action action to v5 @renovate (#46)

This PR contains the following updates:

Package	Type	Update	Change
docker/metadata-action	action	major	`v4` -> `v5`

Release Notes

docker/metadata-action (docker/metadata-action)

`v5`

Compare Source

Update dcarbone/install-jq-action action to v2 @renovate (#49)

This PR contains the following updates:

Package	Type	Update	Change
dcarbone/install-jq-action	action	major	`v1.0.1` -> `v2.0.2`

Release Notes

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

`v2.0.2`

Compare Source

What's Changed

use curl instead of wget to avoid download failure on macOS by @vaidyakhil in https://github.com/dcarbone/install-jq-action/pull/8

Update actions/checkout action to v4 @renovate (#43)

This PR contains the following updates:

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

Release Notes

actions/checkout (actions/checkout)

`v4`

Compare Source

Update docker/login-action action to v3 @renovate (#45)

This PR contains the following updates:

Package	Type	Update	Change
docker/login-action	action	major	`v2` -> `v3`

Release Notes

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

`v3`

Compare Source

Custom Tags allowed as output @Benbentwo (#53)

what

the tags input allows us to add additional tags, but not necessarily use them in the output. this PR fixes that using the priority to sort the output.
adds pass through no-cache option
Fixes Tests with multi arch through docker buildx inspect

why

Custom tagging of applications

References

Duplicate of and closes #52 - testing GHA from non fork

`v1.13.1`

Compare Source

feat: Parameterized DOCKER_METADATA_PR_HEAD_SHA to allow for PR-HEAD tagging @pk-nb (#40 ) (#41)

what

By default, Github Actions uses merge commits during PR events for checkout.
Similarly, the docker-metadata action will use the PR merge commit for the docker SHA tags (referenced via the github.sha variable).
This adds a parameter that allows users to configure docker metadata-action to compute the SHA tags to use github.event.pull_request.head.sha instead.
- Unfortunately the metadata-action does not compute based on a checkout action of the code, so we have to tell it to use the correct event SHA explicitly with this environment variable.
(Folks will also need to update the checkout action in their own workflows to use github.event.pull_request.head.sha)

See https://github.com/docker/metadata-action#environment-variables for documentation.

why

Some users (like us!) find the the default behavior of merge-commits challenging
- Since the merge commit contains code from the target branch, it becomes very difficult to build an image without main branch code in it for hotfixes (with a manual release workflow that we use)
- Merge conflicts cause builds to not be triggered, which is annoying for large / long-running branches
- Some find it unintuitive that the SHAs don't match the PR head
- It is harder to reference tags in the ECR registry since the merge SHAs are more opaque
Parameterized it as other folks may like the tradeoffs of merge commits for "closer to merge" results for testing and don't want to break other workflows.
- Confirmed the paramterization uses a true check so the default of false will work as expected.

Refs

Merge #40 @pk-nb

🤖 Automatic Updates

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

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

Update actions/checkout action to v4 @renovate (#16)

This PR contains the following updates:

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

Release Notes

actions/checkout (actions/checkout)

`v4`

Compare Source

Update docker/login-action action to v3 @renovate (#17)

This PR contains the following updates:

Package	Type	Update	Change
docker/login-action	action	major	`v2` -> `v3`

Release Notes

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

`v3`

Compare Source

`v0.1.2`

Compare Source

Added image-name input @goruha (#14)

what

Added Image name input

why

Allow specifying custom image name (instead of default {org}/{repo name})
To be consistent with https://github.com/cloudposse/github-action-docker-build-push/releases/tag/1.9.0
To be consistent with https://github.com/cloudposse/github-action-docker-promote/releases/tag/0.1.2

Update cloudposse/github-action-yaml-config-query action to v0.1.3 @renovate (#10)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-yaml-config-query	action	patch	`0.1.1` -> `0.1.3`

Release Notes

cloudposse/github-action-yaml-config-query

`v0.1.3`

Compare Source

Use ECR alpine image @goruha (#14)

what

Use ECR alpine image

Avoid docker hub limits hit

🤖 Automatic Updates

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

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

`v0.1.2`

Compare Source

🤖 Automatic Updates

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

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

Update cloudposse/actions action to v0.33.0 @renovate (#12)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/actions	action	minor	`0.31.0` -> `0.33.0`

Release Notes

cloudposse/actions

`v0.33.0`

Compare Source

`v0.32.0`: 0.32.0 Update cloned actions

Compare Source

What's Changed

Use args with status updater instead of env vars, update checkout to v3 by @Nuru in https://github.com/cloudposse/actions/pull/133
Renamed access token by @zdmytriv in https://github.com/cloudposse/actions/pull/137
Update cloned GitHub actions by @Nuru in https://github.com/cloudposse/actions/pull/136
Update cloned actions to current by @Nuru in https://github.com/cloudposse/actions/pull/138

New Contributors

@zdmytriv made their first contribution in https://github.com/cloudposse/actions/pull/137

Full Changelog: cloudposse-archives/actions@0.31.0...0.32.0

Update cloudposse/github-action-docker-build-push action to v1.13.0 @renovate (#13)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-docker-build-push	action	minor	`1.9.0` -> `1.13.0`

Release Notes

cloudposse/github-action-docker-build-push

`v1.13.0`

Compare Source

Expose buildx provenance (#38) (#39) @Sytten

what

Expose provenance buildx parameter

why

Deploy to lambda

references

closes #37
original #38

`v1.12.0`

Compare Source

Update docker/build-push-action action to v4 @renovate (#28)

This PR contains the following updates:

Package	Type	Update	Change
docker/build-push-action	action	major	`v3` -> `v4`

Release Notes

docker/build-push-action

`v4`

Compare Source

Ensure jq 1.6 @goruha (#35)

what

Install jq version 1.6

why

Ensure jq exists and have the right version

Update cloudposse/actions action to v0.33.0 @renovate (#30)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/actions	action	minor	`0.31.0` -> `0.33.0`

Release Notes

cloudposse/actions

`v0.33.0`

Compare Source

`v0.32.0`: 0.32.0 Update cloned actions

Compare Source

What's Changed

Use args with status updater instead of env vars, update checkout to v3 by @Nuru in https://github.com/cloudposse/actions/pull/133
Renamed access token by @zdmytriv in https://github.com/cloudposse/actions/pull/137
Update cloned GitHub actions by @Nuru in https://github.com/cloudposse/actions/pull/136
Update cloned actions to current by @Nuru in https://github.com/cloudposse/actions/pull/138

New Contributors

@zdmytriv made their first contribution in https://github.com/cloudposse/actions/pull/137

Full Changelog: cloudposse-archives/actions@0.31.0...0.32.0

`v1.11.0`

Compare Source

Add Secrets and Secret-files @Benbentwo (#33)

what

Exposes Secrets and Secret Files

references

`v1.10.0`

Compare Source

Support for multi-platform builds @zdmytriv (#32)

what

Introduced new input parameter --platform

why

Support for multi-platform docker builds

references

🤖 Automatic Updates

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

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

`v0.1.1`

Compare Source

Update cloudposse/github-action-docker-build-push action to v1.9.0 @renovate (#7)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-docker-build-push	action	minor	`1.6.0` -> `1.9.0`

Release Notes

cloudposse/github-action-docker-build-push

`v1.9.0`

Compare Source

Add image_name parameter in case $org/$repo isn't acceptable @ozydingo (#27)

what

Adds an image_name input that can be specified if the default ${{ inputs.organization }}/${{ inputs.repository }} is not acceptable.

why

We have a use case where we build multiple targets from the same dockerfile in the same repo.
As currently abstracted, the image name will be the same for these: ${{ inputs.organization }}/${{ inputs.repository }}.
We hacked around this by modifying the value of inputs.repository to include the build target, but this is incorrect (and repository is used on one other place here)
We added a use case for which the above hack does not work -- two docker files, both using the default target.
It would be nice to support the underlying action's image_name as a pass-through.

references

Build using the new image_name var: link
Build using this branch without supplying image_name: link

I suspect tests are failing due to missing secrets in my fork, or something like that.

`v1.8.0`

Compare Source

SSH Forward Key Parameter @milldr (#26)

what

added SSH option

why

Added option for #24

references

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

`v1.7.0`

Compare Source

Feat: Parameterize Cache Options @milldr (#25)

what

parameterize caching options

why

we want to be able to change the fixed values

references

n/a

Update cloudposse/github-action-yaml-config-query action to v0.1.1 @renovate (#8)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-yaml-config-query	action	patch	`0.1.0` -> `0.1.1`

Release Notes

cloudposse/github-action-yaml-config-query

`v0.1.1`

Compare Source

Update alpine Docker tag to v3.17 @renovate (#8)

This PR contains the following updates:

Package	Type	Update	Change
alpine	final	minor	`3.16` -> `3.17`

Fix query @goruha (#9)

what

Fix query

🤖 Automatic Updates

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

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

🤖 Automatic Updates

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

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

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

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

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 has been generated by Mend Renovate. View repository job log here.

Update cloudposse/github-action-docker-image-exists action to v0.2.0

7bf7598

renovate bot force-pushed the renovate/cloudposse-github-action-docker-image-exists-0.x branch from d4a0026 to 7bf7598 Compare February 7, 2024 13:48

renovate bot changed the title ~~Update cloudposse/github-action-docker-image-exists action to v0.1.2~~ Update cloudposse/github-action-docker-image-exists action to v0.2.0 Feb 7, 2024

hans-d approved these changes Mar 3, 2024

View reviewed changes

hans-d merged commit 2630daa into main Mar 3, 2024

hans-d deleted the renovate/cloudposse-github-action-docker-image-exists-0.x branch March 3, 2024 09:34

Conversation

renovate bot commented Jul 3, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Release Notes

Release Notes

Release Notes

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

Release Notes

Release Notes

what

why

References

what

why

Refs

🤖 Automatic Updates

what

why

Release Notes

Release Notes

what

why

Release Notes

what

🤖 Automatic Updates

what

why

🤖 Automatic Updates

what

why

Release Notes

v0.32.0: 0.32.0 Update cloned actions

What's Changed

New Contributors

Release Notes

what

why

references

Release Notes

what

why

Release Notes

v0.32.0: 0.32.0 Update cloned actions

What's Changed

New Contributors

what

references

what

why

references

🤖 Automatic Updates

what

why

Release Notes

what

why

references

what

why

references

what

why

references

Release Notes

what

🤖 Automatic Updates

what

why

🤖 Automatic Updates

what

why

what

why

Configuration

Uh oh!

renovate bot commented Jul 3, 2023 •

edited

Loading

`v0.32.0`: 0.32.0 Update cloned actions

`v0.32.0`: 0.32.0 Update cloned actions