v3.0.0

Release includes v3.0.0 of gradle/actions/setup-gradle and gradle/actions/dependency-submission.
This is the first available under the v3 version tag.

The gradle/actions/setup-gradle action supersedes gradle/gradle-build-action.
The gradle/[email protected] version will be released in parallel, and will delegate to this release of 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 [email protected] 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 (gradle/gradle-build-action#946)
• [NEW] - Support for save & restore of configuration-cache data (gradle/gradle-build-action#966)
• [NEW] - Support for automatic adding PR comment with Job Summary content (gradle/gradle-build-action#1020)
• [NEW] - Make it easy to publish a Build Scan® to https://scans.gradle.com (gradle/gradle-build-action#1044)
• [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 (gradle/gradle-build-action#1036). Failure modes include:
  • Fail build step if version of Gradle being executed is not supported for dependency-graph generation (gradle/gradle-build-action#1034)
  • Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API (gradle/gradle-build-action#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 (gradle/gradle-build-action#1017)
  • 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 (gradle/gradle-build-action#1024)
  • 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 (gradle/gradle-build-action#995)
• [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 (gradle/gradle-build-action#996)
• [BREAKING CHANGE] - Remove the gradle-executable input parameter. Use a separate workflow Step to execute a Gradle from a custom location.