commercetools-sdk-java-v2
commercetools-sdk-java-v2 copied to clipboard
chore(deps): update gradle/actions action to v4
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| gradle/actions | action | major | v3.3.2 -> v4.0.1 |
Release Notes
gradle/actions (gradle/actions)
v4.0.1
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: https://github.com/gradle/actions/compare/v4.0.0...v4.0.1
v4.0.0
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-wrappersmakes it possible to validate snapshot wrapper jars usingsetup-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-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) - Improved error message when
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
- In Job summary, the action now provides an explanation when cache is set to
read-onlyordisabled(#255) - When
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) - To attempt to speed up builds, the
setup-gradleanddependency-submissionactions now attempt to use theD:drive for Gradle User Home if it is available (#290)
Deprecations and breaking changes
- The
gradle-home-cache-cleanupinput parameter has been deprecated and replaced bycache-cleanup - The undocumented
dependency-graph: clearparameter has been removed without replacement - The following parameters deprecated in
v3have been removed:
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: https://github.com/gradle/actions/compare/v3.5.0...v4.0.0
v3.5.0
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
- 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: https://github.com/gradle/actions/compare/v3.4.2...v3.5.0
v3.4.2
This patch release fixes a race condition that resulted in the DEVELOCITY_ACCESS_KEY variable not being set in the environment.
What's Changed
- Fix race condition with fetching short lived token by @alextu in https://github.com/gradle/actions/pull/260
Full Changelog: https://github.com/gradle/actions/compare/v3.4.1...v3.4.2
v3.4.1
This patch release fixes a bug introduced in v3.4.0, that prevents build scan publication to Develocity.
The bug results in the removal of the DEVELOCITY_ACCESS_KEY variable being removed, so that Gradle cannot authenticate with the Develocity server.
What's Changed
- Don't clear access key when access token cannot be obtained by @cdsap in https://github.com/gradle/actions/pull/258
- Simplify requesting short-lived Develocity access tokens by @bigdaz in https://github.com/gradle/actions/pull/259
Full Changelog: https://github.com/gradle/actions/compare/v3.4.0...v3.4.1
v3.4.0
This release improves the integration with Gradle Develocity®, as well as updating a number of key dependencies.
- The new
develocity-access-keyinput parameter allows the action to generate a short-lived access token for subsequent communication with Develocity. This reduces the risk of the full (long-lived) access key being compromised, either accidentally or by a malicious action. - New input parameters are available to configure Develocity injection. Previously Develocity injection could only be enabled by setting environment variables.
- Checksums for Gradle 8.8 are now included, so that no network request is required for
wrapper-validationwith Gradle 8.8 wrappers.
What's Changed
- Add support for short-lived tokens by @alextu in https://github.com/gradle/actions/pull/224
- Update known wrapper checksums by @github-actions in https://github.com/gradle/actions/pull/240
- Update to Gradle 8.8 by @bigdaz in https://github.com/gradle/actions/pull/251
- Adding Develocity input actions by @cdsap in https://github.com/gradle/actions/pull/244
- Fail on invalid boolean for Develocity inputs by @bigdaz in https://github.com/gradle/actions/pull/252
New Contributors
- @serieznyi made their first contribution in https://github.com/gradle/actions/pull/216
- @lokalpage-safe made their first contribution in https://github.com/gradle/actions/pull/205
- @alextu made their first contribution in https://github.com/gradle/actions/pull/224
- @bot-githubaction made their first contribution in https://github.com/gradle/actions/pull/227
- @antonmos made their first contribution in https://github.com/gradle/actions/pull/234
- @cdsap made their first contribution in https://github.com/gradle/actions/pull/244
Full Changelog: https://github.com/gradle/actions/compare/v3.3.2...v3.4.0
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.