Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update docker/build-push-action action to v6.12.0 #1405

Merged
merged 1 commit into from
Jan 16, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 15, 2025

This PR contains the following updates:

Package Type Update Change
docker/build-push-action action minor v6.11.0 -> v6.12.0

Release Notes

docker/build-push-action (docker/build-push-action)

v6.12.0

Compare Source

Full Changelog: docker/build-push-action@v6.11.0...v6.12.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from b9d1ac1 to 809a4de Compare January 16, 2025 07:14
@renovate renovate bot force-pushed the renovate/docker-build-push-action-6.x branch from 809a4de to 737b064 Compare January 16, 2025 13:14
@GoetzGoerisch GoetzGoerisch added this pull request to the merge queue Jan 16, 2025
Merged via the queue into develop with commit c2370f4 Jan 16, 2025
26 checks passed
@renovate renovate bot deleted the renovate/docker-build-push-action-6.x branch January 16, 2025 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant