Skip to content

chore(deps): update docker/metadata-action action to v6#24

Merged
tagoro9 merged 1 commit intomainfrom
c/renovate_docker-metadata-action-6.x
Mar 7, 2026
Merged

chore(deps): update docker/metadata-action action to v6#24
tagoro9 merged 1 commit intomainfrom
c/renovate_docker-metadata-action-6.x

Conversation

@open-turo-bot
Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
docker/metadata-action action major v5 -> v6

Release Notes

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

v6

Compare Source


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 has been generated by Renovate Bot.

@open-turo-bot open-turo-bot requested a review from a team as a code owner March 5, 2026 19:24
@open-turo-bot open-turo-bot force-pushed the c/renovate_docker-metadata-action-6.x branch from af36b19 to 355ec6d Compare March 6, 2026 00:25
@open-turo-bot open-turo-bot force-pushed the c/renovate_docker-metadata-action-6.x branch from 355ec6d to 4235e42 Compare March 7, 2026 00:19
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 7, 2026

Release notes preview

No new release will be created.

If you are expecting a release, you will need to either fix a bug or add a feature.
Chores, CI, docs, refactoring, style and other changes will not trigger a release.

@tagoro9 tagoro9 merged commit aa8ecf1 into main Mar 7, 2026
3 checks passed
@tagoro9 tagoro9 deleted the c/renovate_docker-metadata-action-6.x branch March 7, 2026 00:36
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.

3 participants