chore(deps): update actions/upload-artifact action to v7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/upload-artifact	action	major	v6 → v7

---

Release Notes

actions/upload-artifact (actions/upload-artifact)

v7

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 57s —— View job

---

PR Review: Update actions/upload-artifact to v7

• Gather context and read changed files
• Analyze the change and provide review feedback

---

Summary

This is a clean, minimal dependency update. The single-line change updates actions/upload-artifact from v6 to v7 in .github/workflows/android-ci.yml:41.

Review

The update is safe and compatible. All parameters used in this step are fully supported in v7 with no behavior changes:

uses: actions/upload-artifact@v7   # was @v6
with:
  name: coverage-reports
  path: build/reports/jacoco/mergedJacocoReport/
  retention-days: 30

The name, path, retention-days, and if: always() fields have identical semantics in v7. The main change in v7 is a backend infrastructure upgrade (Artifact Service v2), which is transparent for this usage.

One pre-existing issue to be aware of: .github/workflows/android-ci.yml:20 uses actions/checkout@v6, but actions/checkout only exists up to v4. This is unrelated to this PR but could indicate a workflow configuration problem that predates this change.

Verdict

✅ LGTM — The change is correct, minimal, and non-breaking. Safe to merge.

[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