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

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

v1.2.0

Fix docker create context @goruha (#15)

what

• Fix docker create context

v1.1.0

Added test for non default Dockerfile @goruha (#13)

what

• Added test for non default Dockerfile

v1.0.0

Added `file` parameter as `Dockerfile` @goruha (#11)

what

• Added file parameter as Dockerfile

v0.1.1

Configure Renovate @renovate (#1)

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• .github/workflows/auto-readme.yml (github-actions)
• .github/workflows/bleeding-edge.yaml (github-actions)
• .github/workflows/pull-request.yml (github-actions)
• .github/workflows/test-docker-build.yml (github-actions)
• action.yml (github-actions)

Configuration

🔡 Renovate has detected a custom config for this PR. Feel free to ask for help if you have any doubts and would like it reviewed.

Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.

What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

Update actions/checkout action to v3

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-3.x
• Merge into: main
• Upgrade actions/checkout to v3

Update docker/build-push-action action to v3

• Schedule: ["at any time"]
• Branch name: renovate/docker-build-push-action-3.x
• Merge into: main
• Upgrade docker/build-push-action to v3

Update docker/setup-buildx-action action to v2

• Schedule: ["at any time"]
• Branch name: renovate/docker-setup-buildx-action-2.x
• Merge into: main
• Upgrade docker/setup-buildx-action to v2

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Mend Renovate. View repository job log here.

Fix badges @goruha (#3)

what

• Fix Readme badges

🐛 Bug Fixes

Bug Fix: Create `docker context` before running `buildx` @milldr (#10)

what

• Creates the Docker Context before attempting to run Buildx steps

why

• There's a bug with the action, see actions/actions-runner-controller#893
• To workaround, simply create the context before running buildx

references

• Bug: actions/actions-runner-controller#893

v0.1.0

Added build action @goruha (#2)

what

• Added docker build action

why

• Simplify docker build with GHA