Skip to content

v0.2.0

Marketplace
Marketplace
Compare
Choose a tag to compare
@github-actions github-actions released this 07 Feb 12:52
· 5 commits to refs/heads/main since this release
0.2.0
da5ede5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Update docker/metadata-action action to v5 @renovate (#19)

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 cloudposse/github-action-docker-build-push action to v1.14.0 @renovate (#16)

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
New Contributors

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

v2.0.1

Compare Source

What's Changed

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

v2.0.0

Compare Source

What's Changed
New Contributors

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

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.
Refs
🤖 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 (#17)

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 (#18)

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

Contributors

renovate
Assets 2
Loading