github-actions: bump docker/metadata-action from 5 to 6 - #641
Merged
bgentry merged 1 commit intoAug 1, 2026
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>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
bgentry
approved these changes
Aug 1, 2026
bgentry
left a comment
bgentry
left a comment
Contributor
There was a problem hiding this comment.
🤖 Codex review: Approved after dependency security and compatibility review.
Upgrade
docker/metadata-action:v5→v6- Reviewed head:
c41e1870cf4981c8535a66e9d300ea4f940e5aba
Security review
- The mutable refs resolve to GitHub-verified release commits
c299e40c65443455700f0fdfc63efafe5b349051(v5.10.0) anddc802804100637a589fabce1cb79ff13a1411302(v6.2.0). - The action moves from Node 20 to Node 24 and otherwise preserves application behavior, except that list parsing now preserves infix
#characters. River's current inputs are unaffected. - Static source, lock, source-map, and bundle review found no new executed secret read, telemetry, arbitrary endpoint, subprocess, native payload, install hook, or filesystem behavior.
- Default River usage only calls GitHub repository metadata APIs; the optional Git subprocess path is not enabled. No applicable security advisory was identified, so this is routine maintenance.
Compatibility verification
- The v6 action executed successfully in both public
riveruiarchitecture builds and the manifest merge, covering River's current public tags, labels, JSON, and bake outputs. - Exact-head Go/JS CI, Go lint, and release checks passed.
git diff --check— passed.- The
riverprouijob fails before metadata-action because Dependabot cannot assume the AWS OIDC role; Pro-specific outputs were not exercised on this head.
Residual risk
v6is mutable; pinningdc802804100637a589fabce1cb79ff13a1411302would bound the reviewed identity.- The large generated bundle was statically audited but not independently rebuilt. Pro-specific tag/output compatibility remains unverified, with no blocker identified from the shared public execution paths.
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
dc80280Merge pull request #696 from docker/dependabot/npm_and_yarn/docker/actions-to...2b9fe83[dependabot skip] chore: update generated content8128ce3chore(deps): Bump@docker/actions-toolkitfrom 0.91.0 to 0.92.01d1c895Merge pull request #695 from docker/dependabot/npm_and_yarn/semver-7.8.57f0c2ddMerge pull request #694 from docker/dependabot/npm_and_yarn/sigstore-4.1.1025f8c5[dependabot skip] chore: update generated contente98d63cchore(deps): Bump semver from 7.8.1 to 7.8.537d9379chore(deps): Bump sigstore from 4.1.0 to 4.1.1a1b8072Merge pull request #690 from docker/dependabot/npm_and_yarn/sigstore/core-3.2.1e0e3381[dependabot skip] chore: update generated contentDependabot 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)