Update gradle/actions action to v4 #37
Open
Conversation
This file contains hidden or 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}
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
from
9446b17 to
d551eec
Compare
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
from
d551eec to
8e52383
Compare
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
2 times, most recently
from
3bdaa2b to
0d4cbc3
Compare
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
from
0d4cbc3 to
5cffe4c
Compare
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
from
5cffe4c to
96ce59c
Compare
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
from
96ce59c to
6d8881f
Compare
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
from
6d8881f to
355c0c8
Compare
renovate
bot
force-pushed
the
renovate/gradle-actions-4.x
branch
from
355c0c8 to
48f5cda
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.4.1Release Notes
gradle/actions (gradle/actions)
v4.4.1Compare Source
This patch release fixes a bug in Develocity Injection with a custom plugin repository.
The
gradle-plugin-repository-*action parameters were not being correctly mapped to environment variables that are read by the Develocity Injection init script.This issue has been fixed by setting the correct environment variables:
gradle-plugin-repository-urlis mapped toDEVELOCITY_INJECTION_PLUGIN_REPOSITORY_URLgradle-plugin-repository-usernameis mapped toDEVELOCITY_INJECTION_PLUGIN_REPOSITORY_USERNAMEgradle-plugin-repository-passwordis mapped toDEVELOCITY_INJECTION_PLUGIN_REPOSITORY_PASSWORDAdditionally, these parameters can now be used to configure a custom plugin repository for the GitHub Dependency Graph Gradle Plugin, required for dependency submission.
What's Changed
Full Changelog: gradle/actions@v4.4.0...v4.4.1
v4.4.0Compare Source
This release updates 2 downstream components:
DEVELOCITY_INJECTION_. Check the docs for more details.What's Changed
New Contributors
Full Changelog: gradle/actions@v4.3.1...v4.4.0
v4.3.1Compare Source
This release fixes a couple of minor issues, as well as keeping dependencies up to date.
Fixed issues
What's Changed
develocity-allow-untrusted-serveris enabled by @remcomokveld in https://github.com/gradle/actions/pull/575New Contributors
Full Changelog: gradle/actions@v4.3.0...v4.3.1
v4.3.0Compare Source
This release brings some significant improvements to cache-cleanup and dependency-submission:
dependency-submission(#519)build-scan-publish: trueor Develocity injection (#543)What's Changed
cache-reporting.tsby @SimonMarquis in https://github.com/gradle/actions/pull/492New Contributors
Full Changelog: gradle/actions@v4.2.2...v4.3.0
v4.2.2Compare Source
This patch release updates a bunch of dependency versions and fixes a deprecation warning emitted with Gradle 8.12.
What's Changed
New Contributors
Full Changelog: gradle/actions@v4.2.1...v4.2.2
v4.2.1Compare Source
This patch release fixes some issues with Develocity and Build Scan integration:
build-scan-publishcauses some Develocity injection parameters to be ignored (#447)develocity-ccud-plugin-versionparameter is ignored (#446)What's Changed
New Contributors
Full Changelog: gradle/actions@v4.2.0...v4.2.1
v4.2.0Compare 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
Full Changelog: gradle/actions@v4.1.0...v4.2.0
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
🔕 Ignore: Close this PR and you won't be reminded about these updates again.