Skip to content

chore(ci): bump docker/login-action from 3.7.0 to 4.1.0#39

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/docker/login-action-4.1.0
Closed

chore(ci): bump docker/login-action from 3.7.0 to 4.1.0#39
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/docker/login-action-4.1.0

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github May 21, 2026

Bumps docker/login-action from 3.7.0 to 4.1.0.

Release notes

Sourced from docker/login-action's releases.

v4.1.0

Full Changelog: docker/login-action@v4.0.0...v4.1.0

v4.0.0

Full Changelog: docker/login-action@v3.7.0...v4.0.0

Commits
  • 4907a6d Merge pull request #930 from docker/dependabot/npm_and_yarn/aws-sdk-dependenc...
  • 1e233e6 chore: update generated content
  • 6c24ead build(deps): bump the aws-sdk-dependencies group with 2 updates
  • ee034d7 Merge pull request #958 from docker/dependabot/npm_and_yarn/lodash-4.18.1
  • 1527209 Merge pull request #937 from docker/dependabot/npm_and_yarn/proxy-agent-depen...
  • d39362a build(deps): bump lodash from 4.17.23 to 4.18.1
  • a6f092b chore: update generated content
  • 60953f0 build(deps): bump the proxy-agent-dependencies group with 2 updates
  • 62c6885 Merge pull request #936 from docker/dependabot/npm_and_yarn/docker/actions-to...
  • 102c0e6 chore: update generated content
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [docker/login-action](https://github.com/docker/login-action) from 3.7.0 to 4.1.0.
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](docker/login-action@c94ce9f...4907a6d)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-version: 4.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github May 21, 2026

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot requested a review from a team as a code owner May 21, 2026 12:04
@github-actions github-actions Bot added the size/XS PR size: XS label May 21, 2026
Copy link
Copy Markdown
Contributor

@lml2468 lml2468 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[APPROVE — self-review, posting as COMMENT] Clean SHA-pinned bump.

docker/login-action 3.7.0 → 4.1.0: SHA updated in both occurrences in docker-publish.yml (c94ce9f4907a6d), version comment updated.
✅ Used in two places (per-arch build job + merge job) — both updated consistently.
✅ actionlint passed.

Ready to merge.

Copy link
Copy Markdown

@Jerry-Xin Jerry-Xin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary: This PR is relevant to Mininglamp-OSS/octo-admin because it updates the Docker publish workflow used by the project, and the pinned action bump is safe in the current workflow context.

🔴 Blocking: None.

💬 Non-blocking: None.

✅ Highlights:

  • .github/workflows/docker-publish.yml:178 and .github/workflows/docker-publish.yml:233 keep the action pinned to a full commit SHA while updating the version comment, preserving the repository’s existing supply-chain hardening pattern.
  • The v4.1.0 runtime change to Node 24 is compatible with the configured GitHub-hosted runners, ubuntu-latest and ubuntu-24.04-arm, so I do not see a runner compatibility blocker.
  • The login inputs and secret handling are unchanged, and the workflow still gates Docker Hub credentials behind the existing docker-hub-publish environment.

Copy link
Copy Markdown
Contributor

@lml2468 lml2468 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[APPROVE — COMMENT due to self-review restriction] Independent cross-review.

Verified:

  1. SHA pin4907a6ddec9925e35a0a9e82d7399ccc52663121 matches docker/login-action tag v4.1.0. ✅
  2. Both occurrences updated — Lines 178 and 233 in docker-publish.yml (build job + merge job). ✅
  3. Usage unchangedusername + password inputs are stable across v3→v4. ✅
  4. CI — All checks green. ✅

No blocking issues. Standard Dependabot action bump, SHA verified.

@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github May 26, 2026

Superseded by #51.

@dependabot dependabot Bot closed this May 26, 2026
@dependabot dependabot Bot deleted the dependabot/github_actions/docker/login-action-4.1.0 branch May 26, 2026 06:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XS PR size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants