Update gradle/actions action to v4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
gradle/actions	action	major	v3.4.2 -> v4.2.1

---

Release Notes

gradle/actions (gradle/actions)

v4.2.1

Compare Source

This patch release fixes some issues with Develocity and Build Scan integration:

• Build scan links not captured in project using plugin com.gradle.enteprise:3.18.2 (#​449)
• Enabling build-scan-publish causes some Develocity injection parameters to be ignored (#​447)
• Setting develocity-ccud-plugin-version parameter is ignored (#​446)

What's Changed

• Do not fail wrapper-validation on filename with illegal characters #​438
• Bump references to Develocity Gradle plugin from 3.18.1 to 3.18.2 by @​bot-githubaction in https://github.com/gradle/actions/pull/441
• Bump Gradle from 8.10.2 to 8.11 in https://github.com/gradle/actions/pull/443
• Develocity injection fixes in https://github.com/gradle/actions/pull/448
• Adapt build-result-capture script for GE plugin 3.17+ in https://github.com/gradle/actions/pull/450
• ci: add scorecard by @​nitrocode in https://github.com/gradle/actions/pull/384

New Contributors

• @​nitrocode made their first contribution in https://github.com/gradle/actions/pull/384

Full Changelog: gradle/actions@v4.2.0...v4.2.1

v4.2.0

Compare Source

This release fixes a bug that prevents cache-cleanup from working with Gradle 8.11.
A number of improvements to cache reporting are also included.

What's Changed

• Fix cache-cleanup with Gradle 8.11 (https://github.com/gradle/actions/pull/430)
• Update known wrapper checksums to include Gradle 8.11 (https://github.com/gradle/actions/pull/424)
• Include cache save/restore times in Job Summary (https://github.com/gradle/actions/pull/389)
• Improve cache logging by @​bigdaz (https://github.com/gradle/actions/pull/392)
• Correctly handle multiline patterns for extracted entries (https://github.com/gradle/actions/pull/393)
• Numerous dependency updates

Full Changelog: gradle/actions@v4.1.0...v4.2.0

v4.1.0

Compare Source

This release brings some minor improvements:

• The latest release of Gradle is no longer required to perform cache-cleanup. If Gradle is found to on the PATH and the version meets minimum version requirements, then the version on PATH is used for cache-cleanup and Gradle is not downloaded.
• Fixes a bug where setting the develocity-token-expiry parameter had no effect (#​381)
• Numerous NPM dependency updates

Full Changelog: gradle/actions@v4.0.1...v4.1.0

v4.0.1

Compare Source

This patch release updates a number of dependencies, and fixes a bug that caused Gradle version '8.1' to be confused with '8.10'.

What's Changed

• Dependency-updates by @​bigdaz in https://github.com/gradle/actions/pull/326, https://github.com/gradle/actions/pull/356
• NPM dependency updates by @​dependabot in https://github.com/gradle/actions/pull/330, https://github.com/gradle/actions/pull/349
• Include Gradle 8.10 in known wrapper checksums in https://github.com/gradle/actions/pull/341
• Differentiate Gradle 8.1 from 8.10 when checking version by @​bigdaz in https://github.com/gradle/actions/pull/358

Full Changelog: gradle/actions@v4.0.0...v4.0.1

v4.0.0

Compare Source

Final release of v4.0.0 of the setup-gradle, dependency-submission and wrapper-validation actions provided under gradle/actions.
This release is available under the v4 tag.

Major changes from the v3 release

The arguments parameter has been removed

Using the action to execute Gradle via the arguments parameter was deprecated in v3 and this parameter has been removed.
See here for more details.

Cache cleanup enabled by default

After a number of fixes and improvements, this release enables cache-cleanup by default for all Jobs using the setup-gradle and dependency-submission actions.

Improvements and bugfixes related cache cleanup:

• By default, cache cleanup is not run if any Gradle build fails (#​71)
• Cache cleanup is not run after configuration-cache reuse (#​19)

This feature should help to minimize the size of entries written to the GitHub Actions cache, speeding up builds and reducing cache usage.

Wrapper validation enabled by default

In v3, the setup-gradle action was enhanced to support Gradle wrapper validation, removing the need to use a separate workflow
file with the gradle/actions/wrapper-validation action.

With this release, wrapper validation has been significantly improved, and is now enabled by default (#​12):

• The allow-snapshot-wrappers makes it possible to validate snapshot wrapper jars using setup-gradle.
• Checksums for nightly and snapshot Gradle versions are now validated (#​281).
• Valid wrapper checksums are cached in Gradle User Home, reducing the need to retrieve checksum values remotely (#​172).
• Reduce network calls in wrapper-validation for new Gradle versions: By only fetching wrapper checksums for Gradle versions that were not known when this action was released, this release reduces the likelihood that a network failure could cause failure in wrapper validation (#​171)
• Improved error message when wrapper-validation finds no wrapper jars (#​284)

Wrapper validation is important for supply-chain integrity. Enabling this feature by default will increase the coverage of wrapper
validation on projects using GitHub Actions.

New input parameters for Dependency Graph generation

Some dependency-graph inputs that could previously only be configured via environment variables now have dedicated action inputs:

• dependency-graph-report-dir: sets the location where dependency-graph reports will be generated
• dependency-graph-exclude-projects and dependency-graph-include-projects: select which Gradle projects will contribute to the generated dependency graph.
• dependency-graph-exclude-configurations and dependency-graph-include-configurations: select which Gradle configurations will contribute to the generated dependency graph.

Other improvements

• In Job summary, the action now provides an explanation when cache is set to read-only or disabled (#​255)
• When setup-gradle requests a specific Gradle version, the action will no longer download and install that version if it is already available on the PATH of the runner (#​270)
• To attempt to speed up builds, the setup-gradle and dependency-submission actions now attempt to use the D: drive for Gradle User Home if it is available (#​290)

Deprecations and breaking changes

• The gradle-home-cache-cleanup input parameter has been deprecated and replaced by cache-cleanup
• The undocumented dependency-graph: clear parameter has been removed without replacement
• The following parameters deprecated in v3 have been removed:
  • arguments
  • build-scan-terms-of-service-url and build-scan-terms-of-service-agree

Changelog

• Only fetch checksums for unknown wrapper versions by @​bigdaz in https://github.com/gradle/actions/pull/292
• Isolate 'dependency-submission' action from 'setup-gradle' by @​bigdaz in https://github.com/gradle/actions/pull/293
• Caching improvements by @​bigdaz in https://github.com/gradle/actions/pull/294
• Config cache cleanup by @​bigdaz in https://github.com/gradle/actions/pull/295
• Delete excluded paths on restore Gradle Home by @​bigdaz in https://github.com/gradle/actions/pull/298
• Use faster D: drive on windows for Gradle User Home and Gradle downloads by @​bigdaz in https://github.com/gradle/actions/pull/299
• Always set the GRADLE_USER_HOME env var by @​bigdaz in https://github.com/gradle/actions/pull/300
• Fix windows by @​bigdaz in https://github.com/gradle/actions/pull/302
• Use pre-installed Gradle when available by @​bigdaz in https://github.com/gradle/actions/pull/301
• Prepare for v4 release by @​bigdaz in https://github.com/gradle/actions/pull/303
• Include RUNNER_ARCH in cache key by @​bigdaz in https://github.com/gradle/actions/pull/305
• Introduce dependency graph params by @​bigdaz in https://github.com/gradle/actions/pull/304
• Finish enabling cache-cleanup by default by @​bigdaz in https://github.com/gradle/actions/pull/306
• Bump references to Develocity Gradle plugin from 3.17.5 to 3.17.6 by @​bot-githubaction in https://github.com/gradle/actions/pull/315
• Group cache-cleanup log messages by @​bigdaz in https://github.com/gradle/actions/pull/319
• Enable wrapper-validation by default in setup-gradle by @​bigdaz in https://github.com/gradle/actions/pull/318
• Improve error messages for min-wrapper-count by @​bigdaz in https://github.com/gradle/actions/pull/321

Full Changelog: gradle/actions@v3.5.0...v4.0.0

v3.5.0

Compare Source

This release contains a major upgrade to gradle-home-cache-cleanup as well as improvements to dependency-submission.

What's Changed

• Include Gradle 8.9 in known wrapper checksums (avoiding the need to download) (#​266)
• Improvements to cache-cleanup
  • Provision latest Gradle version to use for cache-cleanup (#​33, #​271)
  • Avoid use of timestamp manipulation for cache-cleanup (#​24, #​272)
  • Cleanup artifact transforms cache in Gradle home (#​47)
  • More logging from cache-cleanup operation (#​169)
• Use latest dependency graph plugin (#​269)
  • Avoid resolving configurations that are deprecated for resolving (https://github.com/gradle/github-dependency-graph-gradle-plugin/pull/129)
  • Avoid circular task dependency when build includes itself (https://github.com/gradle/github-dependency-graph-gradle-plugin/issues/141)
• Automatically upload dependency graph file on submission failure (#​291)

Full Changelog: gradle/actions@v3.4.2...v3.5.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 was generated by Mend Renovate. View the repository job log.