Bump gradle/actions from 3 to 4

[dependabot]

Bumps gradle/actions from 3 to 4.

Release notes

Sourced from gradle/actions's releases.

v4.0.0-rc.1

First release candidate for v4 of the setup-gradle, dependency-submission and wrapper-validation actions provided under gradle/actions. This is the first release available under the v4 tag.

Major changes from the v3 release

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-wrappers makes it possible to validate snapshot wrapper jars using setup-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-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 when 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 generated
• dependency-graph-exclude-projects and dependency-graph-include-projects: select which Gradle projects will contribute to the generated dependency graph.
• dependency-graph-exclude-configurations and dependency-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-only or disabled (#255)
• When setup-gradle requests a specific Gradle version, the action will no longer download and install that version if it is already available on the PATH of the runner (#270)
• To attempt to speed up builds, the setup-gradle and dependency-submission actions now attempt to use the D: drive for Gradle User Home if it is available (#290)

Deprecations and breaking changes

• The gradle-home-cache-cleanup input parameter has been deprecated and replaced by cache-cleanup
• The undocumented dependency-graph: clear parameter has been removed without replacement
• The following parameters deprecated in v3 have been removed:
  • arguments

... (truncated)

Commits

• af1da67 Prevent concurrent jobs in integ-test-full
• f8ba43c Better names for suite workflows
• bcd07e6 Refactor integ-tests into suites
• d74ee73 Refactor integ-tests
• fb2e693 [bot] Update dist directory
• 0719002 Improve error messages for min-wrapper-count (#321)
• ac3aebd Improve error messages for min-wrapper-count
• d473db0 Add tests for wrapper-validation with insufficient wrappers
• 833b05f [bot] Update dist directory
• 06905c7 Enable wrapper-validation by default in setup-gradle (#318)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

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)

Summary by CodeRabbit

• Chores
  • Updated the Gradle wrapper validation action to version v4 in multiple GitHub Actions workflows. This may enhance the validation process and improve reliability during build and deployment tasks.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[coderabbitai]

Walkthrough

The recent changes involve upgrading the version of the Gradle wrapper validation action in multiple GitHub Actions workflow files from v3 to v4. This update enhances the validation process during CI/CD execution, potentially introducing new features, improvements, or bug fixes that ensure the Gradle wrapper is correctly configured and reliable.

Changes

File(s)	Change Summary
.github/workflows/gradle-wrapper-validation.yml, .github/workflows/publish-maven-central.yml, .github/workflows/publish-snapshot.yml, .github/workflows/release-maven-central.yml	Upgraded gradle/actions/wrapper-validation from v3 to v4.

Poem

Hop, skip, and jump, oh what a delight,
Upgrading the wrapper brings new features in sight!
With versions now fresh, our builds soar and play,
A joyful leap forward in every way! 🐰✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2c70941 and ec8b51c.

Files selected for processing (4)

• .github/workflows/gradle-wrapper-validation.yml (1 hunks)
• .github/workflows/publish-maven-central.yml (1 hunks)
• .github/workflows/publish-snapshot.yml (1 hunks)
• .github/workflows/release-maven-central.yml (1 hunks)

Additional comments not posted (4)

.github/workflows/gradle-wrapper-validation.yml (1)

10-10: Approve the version update but verify compatibility.

The update from gradle/actions/wrapper-validation@v3 to v4 is approved. Ensure that the new version does not introduce any breaking changes or require additional configurations.

.github/workflows/publish-snapshot.yml (1)

22-22: Approve the version update but verify compatibility.

The update from gradle/actions/wrapper-validation@v3 to v4 is approved. Ensure that the new version does not introduce any breaking changes or require additional configurations.

.github/workflows/publish-maven-central.yml (1)

27-27: Approve the version update but verify compatibility.

The update from gradle/actions/wrapper-validation@v3 to v4 is approved. Ensure that the new version does not introduce any breaking changes or require additional configurations.

.github/workflows/release-maven-central.yml (1)

32-32: Verify compatibility with gradle/actions/wrapper-validation@v4.

Ensure that the upgrade from v3 to v4 does not introduce any breaking changes or require additional configurations. Review the release notes for v4.0.0-rc.1 to confirm compatibility.