[mailersend-renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-java	action	digest	de7274f → b843ebf

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 has been generated by Mend Renovate CLI.

[mailerlite-kritika]

Kritika Review

Bumps actions/setup-java pin from v6.0.1 to v6.1.0

No findings

Confidence 4/5 · medium risk: The change pins actions/setup-java to the v6.1.0 commit, which the review confirmed is the v6 tag with nine commits ahead and none behind, and no reported findings apply. My own concern is that this minor upstream step runs in publish.yaml, which handles Maven Central credentials, and the review summarized the commits from the compare API without reading their code.

Summary

Renovate moves the pinned setup-java SHA in both workflows to b843ebf, which is the v6 tag and v6.1.0. The new commit is 9 commits ahead of the old pin with none behind. The commits are minor features, fixes and dependency bumps. The # v6 comments are still accurate.

Sources consulted

• https://redirect.github.com/actions/setup-java/compare/de7274f081f381c8f8158605e0321c36c376e2e6...b843ebf9b913146b38da2eaa7aeddf76074ae1ad
• https://redirect.github.com/actions/setup-java

Commands offered: curl, fd, gh, jq, rg, yq; run: gh.

_{Reviews (1) · Last reviewed commit: "chore(deps): update actions/setup-java d..." · claude-sonnet-5-5}