Sourced fromgradle/actions's releases.

v4.0.0

Final release ofv4.0.0 of thesetup-gradle,dependency-submission andwrapper-validation actions provided undergradle/actions.This release is available under thev4 tag.

Major changes from thev3 release

Thearguments parameter has been removed

Using the action to execute Gradle via theargumentsparameter was deprecated inv3 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 enablescache-cleanup by default for all Jobs using thesetup-gradle anddependency-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

Inv3, thesetup-gradle action was enhanced to support Gradle wrapper validation, removing the need to use a separate workflowfile with thegradle/actions/wrapper-validation action.

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

• Theallow-snapshot-wrappers makes it possible to validate snapshot wrapper jars usingsetup-gradle.
• Checksums fornightly 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 inwrapper-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 whenwrapper-validation finds no wrapper jars (#284)

Wrapper validation is important for supply-chain integrity. Enabling this feature by default will increase the coverage of wrappervalidation 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 anddependency-graph-include-projects:select which Gradle projects will contribute to the generated dependency graph.
• dependency-graph-exclude-configurations anddependency-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 toread-only ordisabled (#255)
• Whensetup-gradle requests a specific Gradle version, the action will no longer download and install that version if it is already available on thePATH of the runner (#270)
• To attempt to speed up builds, thesetup-gradle anddependency-submission actions now attempt to use theD: drive for Gradle User Home if it is available (#290)

Deprecations and breaking changes

... (truncated)

• 06832c7 Bump the github-actions group across 2 directories with 2 updates
• b7b029e Bump com.google.guava:guava from 33.4.5-jre to 33.4.6-jre in /.github/workflo...
• a0bd2ca [bot] Update dist directory
• 7974541 Dependency updates (#579)
• a581639 Update DSL samples to use test suites
• acd2925 Update java-toolchain sample to use Kotlin DSL
• aa88309 Update gradle-plugin sample to use Kotlin DSL
• 086c9e4 Revert update to eslint-plugin-github
• d31b818 Update patch file for actions/cache@v4.0.3
• 2778b4a Bump the npm-dependencies group across 1 directory with 8 updates
• Additional commits viewable incompare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)