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

v1.6.0

Update actions/checkout action to v3 @renovate (#5)

This PR contains the following updates:

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

---

Release Notes

actions/checkout

v3

Compare Source

• Use @​actions/core saveState and getState
• Add github-server-url input

---

Update docker/build-push-action action to v3 @renovate (#6)

This PR contains the following updates:

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

---

Release Notes

docker/build-push-action

v3

Compare Source

---

Update docker/setup-buildx-action action to v2 @renovate (#8)

This PR contains the following updates:

Package	Type	Update	Change
docker/setup-buildx-action	action	major	v1 -> v2

---

Release Notes

docker/setup-buildx-action

v2

Compare Source

---

Update cloudposse/actions action to v0.31.0 @renovate (#21)

This PR contains the following updates:

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

---

Release Notes

cloudposse/actions

v0.31.0: Update Alpine-based actions to Alpine 3.16

Compare Source

What's Changed

• ci: add injection of CloudFlare secrets by @​SweetOps in https://github.com/cloudposse/actions/pull/111
• Add support for Terraform versions 0.15 and 1.x by @​Nuru in https://github.com/cloudposse/actions/pull/118
• test-harness uses different grep than Geodesic default by @​Nuru in https://github.com/cloudposse/actions/pull/119
• Update bats and terratest testing for Terraform 1.x by @​Nuru in https://github.com/cloudposse/actions/pull/121
• Choose Terraform version based requirements of test, not of module by @​Nuru in https://github.com/cloudposse/actions/pull/132
• chore(deps): update dependency alpine to v3.16 by @​renovate in https://github.com/cloudposse/actions/pull/113

Full Changelog: cloudposse/actions@0.30.0...0.31.0

---

Support build target for dockerfile @ozydingo (#23)

what

• Support a build target for the build action
• Add a target input that allows the build target to be specified (see example PR in refs)

why

• We intend to use a multi-stage dockerfile with different targets for different envs or deployments
• The underlying docker/build-push-action action supports a build target; this merely exposes that additional input

references

• docker/build-push-action
• Example build using the target input via the docker_build_target input in our github-actions repo on a corresponding branch
• The PR and specific change relevant to this feature

v1.5.0

Added latest tags @goruha (#20)

what

• Added latest tag

v1.4.0

Added tags inputs @goruha (#18)

what

• Added tags inputs

v1.3.0

Add build args @goruha (#16)

what

• Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
• Use bullet points to be concise and to the point.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Use bullet points to be concise and to the point.

references

• Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
• Use closes #123, if this PR closes a GitHub issue #123