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

Update docker/metadata-action action to v5.6.1 #340

Merged
merged 1 commit into from
Nov 19, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 19, 2024

This PR contains the following updates:

Package Type Update Change
docker/metadata-action action minor v5.5.1 -> v5.6.1

Release Notes

docker/metadata-action (docker/metadata-action)

v5.6.1

Compare Source

v5.6.0

Compare Source


Configuration

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

🚦 Automerge: Enabled.

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 requested a review from vladgh as a code owner November 19, 2024 15:40
@renovate renovate bot added the dependencies Updates a dependency label Nov 19, 2024
@renovate renovate bot force-pushed the renovate/docker-metadata-action-5.x branch from f843593 to 6f24c7d Compare November 19, 2024 19:51
@renovate renovate bot changed the title Update docker/metadata-action action to v5.6.0 Update docker/metadata-action action to v5.6.1 Nov 19, 2024
@renovate renovate bot merged commit f2cd3a4 into main Nov 19, 2024
3 checks passed
@renovate renovate bot deleted the renovate/docker-metadata-action-5.x branch November 19, 2024 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Updates a dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants