ci: bump docker/metadata-action from 5 to 6#35
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
Conversation
Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 5 to 6. - [Release notes](https://github.com/docker/metadata-action/releases) - [Commits](docker/metadata-action@v5...v6) --- updated-dependencies: - dependency-name: docker/metadata-action dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
nitecon
reviewed
Apr 13, 2026
Owner
nitecon
left a comment
nitecon
left a comment
There was a problem hiding this comment.
Eventic PR Review — docker/metadata-action v5 → v6
Overview
Single-line bump in .github/workflows/release.yml updating docker/metadata-action from v5 to v6. Dependabot-generated, no code changes.
Key Changes in v6
- Node 24 runtime — requires Actions Runner v2.327.1+. GitHub-hosted runners already meet this; self-hosted runners must be updated if applicable.
- Comment handling —
#inside list input values is now preserved (only full-line#treated as comments). Check yourtags:block if you rely on inline#comments. - ESM migration — internal to the action, no consumer-facing API breakage.
- Dependency bumps — lodash, @actions/core 3.0, @actions/github 9.0, @docker/actions-toolkit 0.79.
Risk Assessment
- Breaking change risk: Low. The tag configuration in this workflow uses standard
type=directives with no inline#comments, so the comment-handling change is a no-op here. - Runner compatibility: Low risk for GitHub-hosted. If this repo uses self-hosted runners for releases, verify runner version ≥ v2.327.1.
- Functional risk: Low. The action's inputs/outputs API is unchanged between v5 and v6.
Concerns
- Major version bump — per policy, this requires manual user approval before merge.
Verdict
Looks good — low-risk major bump driven by Node runtime modernization. All CI checks passing so far (a few still in progress). Recommend merging once all checks complete.
🤖 Reviewed by Eventic SRE Automation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps docker/metadata-action from 5 to 6.
Release notes
Sourced from docker/metadata-action's releases.
... (truncated)
Commits
030e881Merge pull request #607 from crazy-max/allow-comments4b529acchore: update generated contentb0082b3preserve comments in list input values with commentNoInfix7b19fecMerge pull request #604 from docker/dependabot/npm_and_yarn/docker/actions-to...281c9b0chore: update generated content5f43b3btest: stabilize github mock setup since ESM9d53276github class moved since actions-toolkit v0.77.0eaa3d39chore(deps): Bump@docker/actions-toolkitfrom 0.68.0 to 0.77.06b695f7Merge pull request #605 from crazy-max/node24a1afadcnode 24 as default runtimeDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)