v1.15.0

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

---

v1.14.0

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

New Contributors

• @​vaidyakhil made their first contribution in https://github.com/dcarbone/install-jq-action/pull/8

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

v2.0.1

Compare Source

What's Changed

• using macos as dl link os prefix in lieu of osx by @​dcarbone in https://github.com/dcarbone/install-jq-action/pull/7

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

v2.0.0

Compare Source

What's Changed

• quick & dirty 1.7 support by @​dcarbone in https://github.com/dcarbone/install-jq-action/pull/4

New Contributors

• @​dcarbone made their first contribution in https://github.com/dcarbone/install-jq-action/pull/4

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

---

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

• Support fetching without the --progress option
• Update to node20

---

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

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

v1.13.0

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

what

• Expose provenance buildx parameter

why

• Deploy to lambda

references

• closes #37
• original #38

v1.12.0

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

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

what

• Exposes Secrets and Secret Files

references

• https://docs.docker.com/build/ci/github-actions/secrets/
• https://github.com/docker/build-push-action/blob/v3.3.1/action.yml#L80-L85

v1.10.0

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

what

• Introduced new input parameter --platform

why

• Support for multi-platform docker builds

references

• https://github.com/docker/setup-qemu-action/
• https://docs.docker.com/build/ci/github-actions/multi-platform/

v1.9.0

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

SSH Forward Key Parameter @milldr (#26)

what

• added SSH option

why

• Added option for #24

references

• #24

v1.7.0

Feat: Parameterize Cache Options @milldr (#25)

what

• parameterize caching options

why

• we want to be able to change the fixed values

references

• n/a