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