Update gradle/actions action to v4 #349
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #349 +/- ##
=======================================
Coverage 79.23% 79.23%
=======================================
Files 44 44
Lines 496 496
Branches 55 55
=======================================
Hits 393 393
Misses 90 90
Partials 13 13 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
from
70773ee
to
1974361
Compare
| datasource | package | from | to | | ----------- | -------------- | ------ | ------ | | github-tags | gradle/actions | v3.5.0 | v4.1.0 |
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
from
1974361
to
7589ca9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.1.0Release Notes
gradle/actions (gradle/actions)
v4.1.0Compare Source
This release brings some minor improvements:
develocity-token-expiryparameter had no effect (#381)Full Changelog: gradle/actions@v4.0.1...v4.1.0
v4.0.1Compare 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
Full Changelog: gradle/actions@v4.0.0...v4.0.1
v4.0.0Compare Source
Final release of
v4.0.0of thesetup-gradle,dependency-submissionandwrapper-validationactions provided undergradle/actions.This release is available under the
v4tag.Major changes from the
v3releaseThe
argumentsparameter has been removedUsing the action to execute Gradle via the
argumentsparameter was deprecated inv3and 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-gradleanddependency-submissionactions.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-gradleaction was enhanced to support Gradle wrapper validation, removing the need to use a separate workflowfile with the
gradle/actions/wrapper-validationaction.With this release, wrapper validation has been significantly improved, and is now enabled by default (#12):
allow-snapshot-wrappersmakes it possible to validate snapshot wrapper jars usingsetup-gradle.wrapper-validationfor 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-validationfinds 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-projectsanddependency-graph-include-projects: select which Gradle projects will contribute to the generated dependency graph.dependency-graph-exclude-configurationsanddependency-graph-include-configurations: select which Gradle configurations will contribute to the generated dependency graph.Other improvements
read-onlyordisabled(#255)setup-gradlerequests a specific Gradle version, the action will no longer download and install that version if it is already available on thePATHof the runner (#270)setup-gradleanddependency-submissionactions now attempt to use theD:drive for Gradle User Home if it is available (#290)Deprecations and breaking changes
gradle-home-cache-cleanupinput parameter has been deprecated and replaced bycache-cleanupdependency-graph: clearparameter has been removed without replacementv3have 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 because a matching PR was automerged previously.
♻ 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.