chore(deps): update gradle/actions action to v5

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
gradle/actions	action	major	v3 → v5

---

Release Notes

gradle/actions (gradle/actions)

v5

Compare Source

v4

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 9am on monday" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 51s —— View job

---

PR Review

• Gather context
• Review changed workflow files
• Check CI status
• Post final review

---

Summary

This Renovate PR updates gradle/actions/setup-gradle from v3 → v5 (skipping v4) in both CI workflow files. The change is minimal, low-risk, and correct.

Changed lines:

• .github/workflows/android-ci.yml:30 — gradle/actions/setup-gradle@v3 → @v5
• .github/workflows/release.yml:57 — gradle/actions/setup-gradle@v3 → @v5

Assessment

Code quality: ✅ The changes are consistent with the existing action pinning strategy used across both workflows (e.g., actions/checkout@v6, actions/setup-java@v5).

Compatibility: ✅ The setup-gradle action's core interface (no required inputs for basic caching) is unchanged between v3 and v5. These workflows use it without additional configuration inputs, so no breaking changes apply.

Security: ℹ️ All actions in these workflows use floating major-version tags (@v5, @v6) rather than pinned SHAs. This is a project-wide convention rather than an issue introduced by this PR. The gradle/actions action is maintained by the official Gradle organization.

CI status: Android CI and Qodana checks are currently in progress — no failures at the time of this review.

Verdict

This is a safe, routine dependency update. Approved for merge once CI passes.

[github-actions]

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions