github-actions: bump docker/login-action from 4.5.2 to 4.6.0 - #679
Merged
bgentry merged 1 commit intoSep 2, 2026
Merged
Conversation
Bumps [docker/login-action](https://github.com/docker/login-action) from 4.5.2 to 4.6.0. - [Release notes](https://github.com/docker/login-action/releases) - [Commits](docker/login-action@v4.5.2...v4.6.0) --- updated-dependencies: - dependency-name: docker/login-action dependency-version: 4.6.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
bgentry
approved these changes
Sep 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/login-action:4.5.2→4.6.0- Reviewed head:
bf1d2d6d72d454fdca06e0ff4096363920921107
Security review
- Compared signed, immutable upstream action commits
371161bbe7024a29a25c5e19bfcbc0804fe9ad2cand
dbcb813823bdd20940b903addbd779551569679f, including action metadata,
source archives, the generated bundle/source map, lockfile churn, registry
integrity, maintainers, provenance, and advisories. action.ymlis unchanged. Runtime changes add path-containment validation
for registry/scope-derived Docker config paths and coherent AWS/Smithy
refreshes. Static review found no new endpoint, credential source, process
spawning, native code, install hook, or unexpected network behavior.- This is security-relevant: the shipped bundle moves
js-yamlfrom vulnerable
5.2.1to patched5.2.2for CVE-2026-73643 and adds traversal hardening.
Computed npm artifact hashes match registry SHA-512 metadata.
Compatibility verification
- The River UI amd64/arm64 image jobs and manifest job exercised the updated
action's default GHCR login path successfully. The Go matrix, JavaScript
checks, lint, release, and public image workflow are green. - The exact head was checked out in isolation. Its non-workflow tree is
byte-identical to the already validated PR #677 tree, so the unaffected
npm ci, lint, 233-test suite, production build, and Storybook build results
were reused. - The River Pro failure occurs earlier while Dependabot attempts to assume the
private AWS role; it never reaches the changed live-registry login step and
is an unavailable bot-authored check.
Residual risk
- Low: River references an immutable release tag rather than a full commit SHA,
and the generated bundle was inspected with its source map rather than
rebuilt. Two intermediate generated-content commits are unsigned, while the
final tag commit is verified. Upstream build-onlypostcss/nanoid
advisories are absent from the prebuilt runtime bundle River executes.
bgentry
deleted the
dependabot/github_actions/docker/login-action-4.6.0
branch
September 2, 2026 02:06
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/login-action from 4.5.2 to 4.6.0.
Release notes
Sourced from docker/login-action's releases.
Commits
dbcb813Merge pull request #1051 from docker/dependabot/npm_and_yarn/aws-sdk-dependen...5bcb015[dependabot skip] chore: update generated contentb30b2f2build(deps): bump the aws-sdk-dependencies group across 1 directory with 2 up...9087f1eMerge pull request #1057 from docker/dependabot/npm_and_yarn/js-yaml-5.2.20009830[dependabot skip] chore: update generated content2325523build(deps): bump js-yaml from 5.2.1 to 5.2.24ec1d4aMerge pull request #1056 from docker/dependabot/npm_and_yarn/postcss-8.5.225fc99baMerge pull request #1053 from docker/dependabot/github_actions/aws-actions/co...e512bd5Merge pull request #1052 from docker/dependabot/github_actions/codeql-actions...a146c91Merge pull request #1059 from crazy-max/harden-buildx-scope-pathsDependabot 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)