Update gradle/gradle-build-action action to v3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
gradle/gradle-build-action	action	major	v2.11.1 -> v3.0.0

---

Release Notes

gradle/gradle-build-action (gradle/gradle-build-action)

v3.0.0

Compare Source

This is the first release of gradle/gradle-build-action available with the v3 version tag.

[!IMPORTANT]
As of v3 this action has been superceded by gradle/actions/setup-gradle.
Any workflow that uses gradle/gradle-build-action@v3 will transparently delegate to gradle/actions/setup-gradle@v3.

Users are encouraged to update their workflows, replacing:

uses: gradle/gradle-build-action@v3

with

uses: gradle/actions/setup-gradle@v3

See the setup-gradle documentation for up-to-date documentation for gradle/actions/setup-gradle.

Changes from gradle-build-action@v2

This release brings some useful and much requested features, including:

• save and restore the Gradle configuration-cache data
• add the Job summary content as a PR comment
• easily publish Build Scans® to the free Gradle Build Scan service
• compatibility with Node 20

The only major breaking change from gradle-build-action@v2.12.0 is the update to require a Node 20 runtime environment.
Aside from that change, this release should generally serve as a drop-in replacement for gradle-build-action@v2.

Changelog

• [NEW] - Run with NodeJs 20.x https://github.com/gradle/gradle-build-action/issues/9466)
• [NEW] - Support for save & restore of configuration-cache data https://github.com/gradle/gradle-build-action/issues/9666)
• [NEW] - Support for automatic adding PR comment with Job Summary content https://github.com/gradle/gradle-build-action/issues/10200)
• [NEW] - Make it easy to publish a Build Scan® to https://scans.gradle.com https://github.com/gradle/gradle-build-action/issues/10444)
• [NEW] - Added dependency-graph-continue-on-failure input, which can be set to false to force the Job to fail when dependency graph submission fails (https://github.com/gradle/gradle-build-action/issues/1036). Failure modes include:
  • Fail build step if version of Gradle being executed is not supported for dependency-graph generation (https://github.com/gradle/gradle-build-action/issues/1034)
  • Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API (https://github.com/gradle/gradle-build-action/issues/997)
• [NEW] - Add dependency-graph: clear option to clear any dependency-graph previously submitted by the job
• [FIX] Allow cache entries to be reused by jobs with the same ID in different workflows https://github.com/gradle/gradle-build-action/issues/10177)
  • Workflow name remains part of the cache key, but cache entries generated by the same job id in a different workflow may be restored
• [FIX] Register pre-installed JDKs in Maven toolchains.xml file https://github.com/gradle/gradle-build-action/issues/10244)
  • This allows pre-installed JDKs to be auto-detected by Gradle Toolchain support on Windows
• [FIX] - Update the Gradle Enterprise injection configuration for product rename to Develocity https://github.com/gradle/gradle-build-action/issues/9955)
• [FIX] - Avoid submitting an empty dependency graph when state is loaded from configuration-cache
• [FIX] - Update to GitHub Dependency Graph Gradle Plugin v1.2.0
• [DEPRECATION] - Deprecation of the arguments parameter https://github.com/gradle/gradle-build-action/issues/9966)
• [BREAKING CHANGE] - Remove the gradle-executable input parameter. Use a separate workflow Step to execute a Gradle from a custom location.

v2.12.0

Compare Source

Adds a new option to clear a previously submitted dependency-graph.

steps:
- uses: gradle/gradle-build-action@v2
  with:
    dependency-graph: clear

This may prove useful when migrating to a workflow using the upcoming gradle/actions/dependency-submission action.

Full-changelog: gradle/gradle-build-action@v2.11.1...v2.12.0

---

Configuration

📅 Schedule: 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 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 has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ad70201) 81.46% compared to head (c6fedaf) 81.46%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   81.46%   81.46%           
=======================================
  Files          18       18           
  Lines        2066     2066           
  Branches      218      218           
=======================================
  Hits         1683     1683           
  Misses        183      183           
  Partials      200      200           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bmarty]

Done in #11

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.