Update gradle/actions action to v4 #3857
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v3.5.0
->v4.0.0
Release Notes
gradle/actions (gradle/actions)
v4.0.0
Compare Source
Final release of
v4.0.0
of thesetup-gradle
,dependency-submission
andwrapper-validation
actions provided undergradle/actions
.This release is available under the
v4
tag.Major changes from the
v3
releaseThe
arguments
parameter has been removedUsing the action to execute Gradle via the
arguments
parameter 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 enables cache-cleanup by default for all Jobs using the
setup-gradle
anddependency-submission
actions.Improvements and bugfixes related cache cleanup:
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
, thesetup-gradle
action was enhanced to support Gradle wrapper validation, removing the need to use a separate workflowfile with the
gradle/actions/wrapper-validation
action.With this release, wrapper validation has been significantly improved, and is now enabled by default (#12):
allow-snapshot-wrappers
makes it possible to validate snapshot wrapper jars usingsetup-gradle
.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)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 generateddependency-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
read-only
ordisabled
(#255)setup-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)setup-gradle
anddependency-submission
actions now attempt to use theD:
drive for Gradle User Home if it is available (#290)Deprecations and breaking changes
gradle-home-cache-cleanup
input parameter has been deprecated and replaced bycache-cleanup
dependency-graph: clear
parameter has been removed without replacementv3
have been removed:Changelog
Full Changelog: gradle/actions@v3.5.0...v4.0.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.
This PR was generated by Mend Renovate. View the repository job log.