sonarcloud[bot]
commented
9 months ago 
Quality Gate passed
Kudos, no new issues were introduced!
0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication
This PR contains the following updates:
v2.12.0->v3.0.0Release Notes
gradle/gradle-build-action (gradle/gradle-build-action)
### [`v3.0.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v3.0.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.12.0...v3.0.0) 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](https://togithub.com/gradle/actions/tree/main/setup-gradle) 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](https://scans.gradle.com) - 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/946](https://togithub.com/gradle/gradle-build-action/issues/946)6) - \[NEW] - Support for save & restore of configuration-cache data [https://github.com/gradle/gradle-build-action/issues/966](https://togithub.com/gradle/gradle-build-action/issues/966)6) - \[NEW] - Support for automatic adding PR comment with Job Summary content [https://github.com/gradle/gradle-build-action/issues/1020](https://togithub.com/gradle/gradle-build-action/issues/1020)0) - \[NEW] - Make it easy to publish a Build Scan® to https://scans.gradle.com [https://github.com/gradle/gradle-build-action/issues/1044](https://togithub.com/gradle/gradle-build-action/issues/1044)4) - \[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](https://togithub.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](https://togithub.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](https://togithub.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/1017](https://togithub.com/gradle/gradle-build-action/issues/1017)7) - 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/1024](https://togithub.com/gradle/gradle-build-action/issues/1024)4) - 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/995](https://togithub.com/gradle/gradle-build-action/issues/995)5) - \[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](https://togithub.com/gradle/github-dependency-graph-gradle-plugin/releases/tag/v1.2.0) - \[DEPRECATION] - Deprecation of the arguments parameter [https://github.com/gradle/gradle-build-action/issues/996](https://togithub.com/gradle/gradle-build-action/issues/996)6) - \[BREAKING CHANGE] - Remove the `gradle-executable` input parameter. Use a separate workflow Step to execute a Gradle from a custom location.Configuration
📅 Schedule: Branch creation - "after 10pm" in timezone Europe/Prague, 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.
This PR has been generated by Mend Renovate. View repository job log here.