Update docker/login-action action to v4.6.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
docker/login-action	action	minor	v4.5.1 → v4.6.0

---

Release Notes

docker/login-action (docker/login-action)

v4.6.0

Compare Source

v4.5.2

Compare Source

---

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

• Branch creation
  • "before 8am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

Claude finished @renovate[bot]'s task in 46s —— View job

---

Review

Single-line version bump of docker/login-action (v4.5.1 → v4.6.0) in .github/workflows/release.yml:34. No inputs changed, and login-action's registry/username/password interface is unchanged in v4, so this is safe to merge as-is.

Notes, none blocking:

• Empty release notes. The Renovate body shows no changelog for either v4.5.2 or v4.6.0 — GitHub returned bare compare links. Worth a glance at the upstream diff before merging, since a minor bump with no published notes gives nothing to review against. Low risk here: this step only does a ghcr.io login with the ephemeral GITHUB_TOKEN.
• Tag pinning vs. SHA pinning. Every third-party action in this repo is pinned to a mutable tag (docker/login-action@v4.6.0, goreleaser/goreleaser-action@v7.2.3, golangci/golangci-lint-action@v9), so this PR is consistent with existing convention. But release.yml runs with packages: write, attestations: write, and id-token: write, and tags can be repointed — SHA pinning would matter most in exactly this workflow. That's a repo-wide policy call, not something this PR introduces; Renovate supports it via pinDigests: true if you want it. Fix this →

No Go code touched, so nothing to say on test coverage or performance. Note this workflow only fires on v* tag pushes, so CI on this PR does not exercise the changed step — the bump is first validated at the next release.

I can't modify files under .github/workflows/ (the GitHub App lacks workflow write permission), so I'd have no way to apply changes here even if requested — see the FAQ.
• branch renovate/all