chore(ci): bump docker/metadata-action from 5.10.0 to 6.0.0#79
Open
dependabot[bot] wants to merge 1 commit into
Open
chore(ci): bump docker/metadata-action from 5.10.0 to 6.0.0#79dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 5.10.0 to 6.0.0. - [Release notes](https://github.com/docker/metadata-action/releases) - [Commits](docker/metadata-action@c299e40...030e881) --- updated-dependencies: - dependency-name: docker/metadata-action dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
lml2468
approved these changes
May 21, 2026
Contributor
lml2468
left a comment
lml2468
left a comment
There was a problem hiding this comment.
[APPROVE] Version verified against official repo tags. Dependabot SHA-pinned bump — safe to merge.
Jerry-Xin
approved these changes
May 21, 2026
Contributor
Jerry-Xin
left a comment
Jerry-Xin
left a comment
There was a problem hiding this comment.
One-line summary: This PR is project-relevant and safely updates the Docker publish workflow’s docker/metadata-action pin to v6.0.0.
✅ Highlights
.github/workflows/docker-publish.yml:224keeps the action pinned to an immutable commit SHA, and I verified that SHA resolves to thev6.0.0tag.- The changed action runs in the
mergejob onubuntu-latest, so the Node 24 runtime requirement fordocker/metadata-action@v6is compatible with the current GitHub-hosted runner setup. - Existing metadata inputs at
.github/workflows/docker-publish.yml:226-238use supportedimages,flavor, andtagsfields; no migration issue is apparent. git diff --checkpassed.
No blocking issues found.
lml2468
reviewed
May 21, 2026
Contributor
lml2468
left a comment
lml2468
left a comment
There was a problem hiding this comment.
Cross-review (qijingchun) — No issues. SHA-pinned bump (docker/metadata-action v5.10.0 → v6.0.0). COMMENTED.
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
2 participants
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.10.0 to 6.0.0.
Release notes
Sourced from docker/metadata-action's releases.
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)