Skip to content

Releases: cloudposse/github-action-docker-promote

v0.3.0

08 Feb 00:32
@github-actions github-actions
0.3.0
3f23f40
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.3.0 Latest
Marketplace
Latest
Marketplace
Update nick-fields/assert-action action to v2 @renovate (#21)

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

Contributors

renovate
Assets 2
Loading

v0.2.0

07 Feb 12:52
@github-actions github-actions
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.
Compare
Choose a tag to compare
v0.2.0
Marketplace
Marketplace
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](https://tog...
Read more

Contributors

renovate
Assets 2
Loading

v0.1.2

03 Jul 22:21
@github-actions github-actions
0.1.2
9356ad3
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.1.2
Marketplace
Marketplace
Added Image name input @goruha (#15)

what

  • Added Image name input

why

Update cloudposse/github-action-yaml-config-query action to v0.1.3 @renovate (#11)

This PR contains the following updates:

Package Type Update Change
cloudposse/github-action-yaml-config-query action patch 0.1.1 -> 0.1.3

Release Notes

cloudposse/github-action-yaml-config-query

v0.1.3

Compare Source

Use ECR alpine image @​goruha (#​14)
what
  • Use ECR alpine image

  • Avoid docker hub limits hit
🤖 Automatic Updates
Update README.md and docs @​cloudpossebot (#​11)
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

v0.1.2

Compare Source

🤖 Automatic Updates
Update README.md and docs @​cloudpossebot (#​10)
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 cloudposse/actions action to v0.33.0 @renovate (#13)

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

New Contributors

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

Update cloudposse/github-action-docker-build-push action to v1.13.0 @renovate (#14)

This PR contains the following updates:

Package Type Update Change
cloudposse/github-action-docker-build-push action minor 1.9.0 -> 1.13.0

Release Notes

cloudposse/github-action-docker-build-push

v1.13.0

Compare Source

Expose buildx provenance (#​38) (#​39) @​Sytten
what
  • Expose provenance buildx parameter
why
  • Deploy to lambda
references
  • closes #​37
  • original #​38

v1.12.0

Compare Source

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

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

v1.11.0

Compare Source

Add Secrets and Secret-files @​Benbentwo (#​33)
what
  • Exposes Secrets and Secret Files
references

v1.10.0

Compare Source

Support for multi-platform builds @​zdmytriv (#​32)
what
  • Introduced new input parameter --platform
why
  • Support for multi-platform docker builds
references

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#12)

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

Contributors

goruha, renovate, and cloudpossebot
Assets 2
Loading

v0.1.1

07 Dec 16:45
@github-actions github-actions
0.1.1
bdbcc13
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.1.1
Marketplace
Marketplace
Update cloudposse/github-action-docker-build-push action to v1.9.0 @renovate (#8)

This PR contains the following updates:

Package Type Update Change
cloudposse/github-action-docker-build-push action minor 1.6.0 -> 1.9.0

Release Notes

cloudposse/github-action-docker-build-push

v1.9.0

Compare Source

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

Compare Source

SSH Forward Key Parameter @​milldr (#​26)

what

  • added SSH option

why

  • Added option for #​24

references

v1.7.0

Compare Source

Feat: Parameterize Cache Options @​milldr (#​25)
what
  • parameterize caching options
why
  • we want to be able to change the fixed values
references
  • n/a
Update cloudposse/github-action-yaml-config-query action to v0.1.1 @renovate (#9)

This PR contains the following updates:

Package Type Update Change
cloudposse/github-action-yaml-config-query action patch 0.1.0 -> 0.1.1

Release Notes

cloudposse/github-action-yaml-config-query

v0.1.1

Compare Source

Update alpine Docker tag to v3.17 @​renovate (#​8)

This PR contains the following updates:

Package Type Update Change
alpine final minor 3.16 -> 3.17
Fix query @​goruha (#​9)
what
  • Fix query
🤖 Automatic Updates
Update README.md and docs @​cloudpossebot (#​7)
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

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#10)

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

Contributors

renovate and cloudpossebot
Assets 2
Loading

v0.1.0

16 Nov 00:44
@github-actions github-actions
0.1.0
eb4f228
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.1.0
Initial implementation @goruha (#5)

what

  • Initial implementation
Update cloudposse/actions action to v0.31.0 @renovate (#2)

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

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

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

This PR contains the following updates:

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

Release Notes

actions/checkout

v3

Compare Source

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/feature-branch.yml (github-actions)
  • .github/workflows/main-branch.yaml (github-actions)
  • .github/workflows/test-negative.yml (github-actions)
  • .github/workflows/test-positive.yml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation.
  • If Renovate detects semantic commits, it will use semantic commit type fix for dependencies and chore for all others.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Autodetect whether to pin dependencies or maintain ranges.
  • Rate limit PR creation to a maximum of two per hour.
  • Limit to maximum 10 open PRs at any time.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • A collection of workarounds for known problems with packages.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

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

Update cloudposse/actions action to v0.31.0
  • Schedule: ["at any time"]
  • Branch name: renovate/cloudposse-actions-0.x
  • Merge into: main
  • Upgrade cloudposse/actions to 0.31.0
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

❓ 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.

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#7)

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 README.md and docs @cloudpossebot (#6)

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

Contributors

goruha, renovate, and cloudpossebot
Assets 2
Loading