Update gradle/actions action to v4

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
gradle/actions	action	major	v3.3.2 -> v4.1.0

---

Release Notes

gradle/actions (gradle/actions)

### [`v4.1.0`](https://redirect.github.com/gradle/actions/releases/tag/v4.1.0) [Compare Source](https://redirect.github.com/gradle/actions/compare/v4.0.1...v4.1.0) This release brings some minor improvements: - The latest release of Gradle is no longer required to perform cache-cleanup. If Gradle is found to on the PATH and the version meets minimum version requirements, then the version on PATH is used for cache-cleanup and Gradle is not downloaded. - Fixes a bug where setting the `develocity-token-expiry` parameter had no effect ([#​381](https://redirect.github.com/gradle/actions/issues/381)) - Numerous NPM dependency updates **Full Changelog**: https://github.com/gradle/actions/compare/v4.0.1...v4.1.0 ### [`v4.0.1`](https://redirect.github.com/gradle/actions/releases/tag/v4.0.1) [Compare Source](https://redirect.github.com/gradle/actions/compare/v4.0.0...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](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/326](https://redirect.github.com/gradle/actions/pull/326), [https://github.com/gradle/actions/pull/356](https://redirect.github.com/gradle/actions/pull/356) - NPM dependency updates by [@​dependabot](https://redirect.github.com/dependabot) in [https://github.com/gradle/actions/pull/330](https://redirect.github.com/gradle/actions/pull/330), [https://github.com/gradle/actions/pull/349](https://redirect.github.com/gradle/actions/pull/349) - Include Gradle 8.10 in known wrapper checksums in [https://github.com/gradle/actions/pull/341](https://redirect.github.com/gradle/actions/pull/341) - Differentiate Gradle 8.1 from 8.10 when checking version by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/358](https://redirect.github.com/gradle/actions/pull/358) **Full Changelog**: https://github.com/gradle/actions/compare/v4.0.0...v4.0.1 ### [`v4.0.0`](https://redirect.github.com/gradle/actions/releases/tag/v4.0.0) [Compare Source](https://redirect.github.com/gradle/actions/compare/v3.5.0...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](https://redirect.github.com/gradle/actions/blob/v4.0.0-rc.1/docs/deprecation-upgrade-guide.md#using-the-action-to-execute-gradle-via-the-arguments-parameter-is-deprecated). ##### Cache cleanup enabled by default After a number of fixes and improvements, this release enables [cache-cleanup](https://redirect.github.com/gradle/actions/blob/v4.0.0-rc.1/docs/setup-gradle.md#configuring-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](https://redirect.github.com/gradle/actions/issues/71)) - Cache cleanup is not run after configuration-cache reuse ([#​19](https://redirect.github.com/gradle/actions/issues/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](https://redirect.github.com/gradle/actions/issues/12)): - The `allow-snapshot-wrappers` makes it possible to validate snapshot wrapper jars using `setup-gradle`. - Checksums for [nightly and snapshot Gradle versions](https://services.gradle.org/distributions-snapshots/) are now validated ([#​281](https://redirect.github.com/gradle/actions/issues/281)). - Valid wrapper checksums are cached in Gradle User Home, reducing the need to retrieve checksum values remotely ([#​172](https://redirect.github.com/gradle/actions/issues/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](https://redirect.github.com/gradle/actions/issues/171)) - Improved error message when `wrapper-validation` finds no wrapper jars ([#​284](https://redirect.github.com/gradle/actions/issues/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](https://redirect.github.com/gradle/actions/blob/v4.0.0-rc.1/docs/dependency-submission.md#selecting-gradle-projects-that-will-contribute-to-the-dependency-graph). - `dependency-graph-exclude-configurations` and `dependency-graph-include-configurations`: [select which Gradle configurations will contribute to the generated dependency graph](https://redirect.github.com/gradle/actions/blob/v4.0.0-rc.1/docs/dependency-submission.md#selecting-gradle-configurations-that-will-contribute-to-the-dependency-graph). ##### Other improvements - In Job summary, the action now provides an explanation when cache is set to `read-only` or `disabled` ([#​255](https://redirect.github.com/gradle/actions/issues/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](https://redirect.github.com/gradle/actions/issues/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](https://redirect.github.com/gradle/actions/issues/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](https://redirect.github.com/gradle/actions/blob/v4.0.0-rc.1/docs/deprecation-upgrade-guide.md#using-the-action-to-execute-gradle-via-the-arguments-parameter-is-deprecated) - [build-scan-terms-of-service-url and build-scan-terms-of-service-agree](https://redirect.github.com/gradle/actions/blob/v4.0.0-rc.1/docs/deprecation-upgrade-guide.md#the-build-scan-terms-of-service-input-parameters-have-been-renamed) ##### Changelog - Only fetch checksums for unknown wrapper versions by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/292](https://redirect.github.com/gradle/actions/pull/292) - Isolate 'dependency-submission' action from 'setup-gradle' by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/293](https://redirect.github.com/gradle/actions/pull/293) - Caching improvements by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/294](https://redirect.github.com/gradle/actions/pull/294) - Config cache cleanup by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/295](https://redirect.github.com/gradle/actions/pull/295) - Delete excluded paths on restore Gradle Home by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/298](https://redirect.github.com/gradle/actions/pull/298) - Use faster D: drive on windows for Gradle User Home and Gradle downloads by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/299](https://redirect.github.com/gradle/actions/pull/299) - Always set the GRADLE_USER_HOME env var by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/300](https://redirect.github.com/gradle/actions/pull/300) - Fix windows by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/302](https://redirect.github.com/gradle/actions/pull/302) - Use pre-installed Gradle when available by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/301](https://redirect.github.com/gradle/actions/pull/301) - Prepare for v4 release by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/303](https://redirect.github.com/gradle/actions/pull/303) - Include RUNNER_ARCH in cache key by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/305](https://redirect.github.com/gradle/actions/pull/305) - Introduce dependency graph params by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/304](https://redirect.github.com/gradle/actions/pull/304) - Finish enabling cache-cleanup by default by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/306](https://redirect.github.com/gradle/actions/pull/306) - Bump references to Develocity Gradle plugin from 3.17.5 to 3.17.6 by [@​bot-githubaction](https://redirect.github.com/bot-githubaction) in [https://github.com/gradle/actions/pull/315](https://redirect.github.com/gradle/actions/pull/315) - Group cache-cleanup log messages by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/319](https://redirect.github.com/gradle/actions/pull/319) - Enable wrapper-validation by default in setup-gradle by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/318](https://redirect.github.com/gradle/actions/pull/318) - Improve error messages for min-wrapper-count by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/321](https://redirect.github.com/gradle/actions/pull/321) **Full Changelog**: https://github.com/gradle/actions/compare/v3.5.0...v4.0.0 ### [`v3.5.0`](https://redirect.github.com/gradle/actions/releases/tag/v3.5.0) [Compare Source](https://redirect.github.com/gradle/actions/compare/v3.4.2...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](https://redirect.github.com/gradle/actions/issues/266)) - Improvements to cache-cleanup - Provision latest Gradle version to use for cache-cleanup ([#​33](https://redirect.github.com/gradle/actions/issues/33), [#​271](https://redirect.github.com/gradle/actions/issues/271)) - Avoid use of timestamp manipulation for cache-cleanup ([#​24](https://redirect.github.com/gradle/actions/issues/24), [#​272](https://redirect.github.com/gradle/actions/issues/272)) - Cleanup artifact transforms cache in Gradle home ([#​47](https://redirect.github.com/gradle/actions/issues/47)) - More logging from cache-cleanup operation ([#​169](https://redirect.github.com/gradle/actions/issues/169)) - Use latest dependency graph plugin ([#​269](https://redirect.github.com/gradle/actions/issues/269)) - Avoid resolving configurations that are deprecated for resolving ([https://github.com/gradle/github-dependency-graph-gradle-plugin/pull/129](https://redirect.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](https://redirect.github.com/gradle/github-dependency-graph-gradle-plugin/issues/141)) - Automatically upload dependency graph file on submission failure ([#​291](https://redirect.github.com/gradle/actions/issues/291)) **Full Changelog**: https://github.com/gradle/actions/compare/v3.4.2...v3.5.0 ### [`v3.4.2`](https://redirect.github.com/gradle/actions/releases/tag/v3.4.2) [Compare Source](https://redirect.github.com/gradle/actions/compare/v3.4.1...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](https://redirect.github.com/alextu) in [https://github.com/gradle/actions/pull/260](https://redirect.github.com/gradle/actions/pull/260) **Full Changelog**: https://github.com/gradle/actions/compare/v3.4.1...v3.4.2 ### [`v3.4.1`](https://redirect.github.com/gradle/actions/releases/tag/v3.4.1) [Compare Source](https://redirect.github.com/gradle/actions/compare/v3.4.0...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](https://redirect.github.com/cdsap) in [https://github.com/gradle/actions/pull/258](https://redirect.github.com/gradle/actions/pull/258) - Simplify requesting short-lived Develocity access tokens by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/259](https://redirect.github.com/gradle/actions/pull/259) **Full Changelog**: https://github.com/gradle/actions/compare/v3.4.0...v3.4.1 ### [`v3.4.0`](https://redirect.github.com/gradle/actions/releases/tag/v3.4.0) [Compare Source](https://redirect.github.com/gradle/actions/compare/v3.3.2...v3.4.0) This release improves the integration with Gradle Develocity®, as well as updating a number of key dependencies. - The new `develocity-access-key` input 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-validation` with Gradle 8.8 wrappers. #### What's Changed - Add support for short-lived tokens by [@​alextu](https://redirect.github.com/alextu) in [https://github.com/gradle/actions/pull/224](https://redirect.github.com/gradle/actions/pull/224) - Update known wrapper checksums by [@​github-actions](https://redirect.github.com/github-actions) in [https://github.com/gradle/actions/pull/240](https://redirect.github.com/gradle/actions/pull/240) - Update to Gradle 8.8 by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/251](https://redirect.github.com/gradle/actions/pull/251) - Adding Develocity input actions by [@​cdsap](https://redirect.github.com/cdsap) in [https://github.com/gradle/actions/pull/244](https://redirect.github.com/gradle/actions/pull/244) - Fail on invalid boolean for Develocity inputs by [@​bigdaz](https://redirect.github.com/bigdaz) in [https://github.com/gradle/actions/pull/252](https://redirect.github.com/gradle/actions/pull/252) #### New Contributors - [@​serieznyi](https://redirect.github.com/serieznyi) made their first contribution in [https://github.com/gradle/actions/pull/216](https://redirect.github.com/gradle/actions/pull/216) - [@​lokalpage-safe](https://redirect.github.com/lokalpage-safe) made their first contribution in [https://github.com/gradle/actions/pull/205](https://redirect.github.com/gradle/actions/pull/205) - [@​alextu](https://redirect.github.com/alextu) made their first contribution in [https://github.com/gradle/actions/pull/224](https://redirect.github.com/gradle/actions/pull/224) - [@​bot-githubaction](https://redirect.github.com/bot-githubaction) made their first contribution in [https://github.com/gradle/actions/pull/227](https://redirect.github.com/gradle/actions/pull/227) - [@​antonmos](https://redirect.github.com/antonmos) made their first contribution in [https://github.com/gradle/actions/pull/234](https://redirect.github.com/gradle/actions/pull/234) - [@​cdsap](https://redirect.github.com/cdsap) made their first contribution in [https://github.com/gradle/actions/pull/244](https://redirect.github.com/gradle/actions/pull/244) **Full Changelog**: https://github.com/gradle/actions/compare/v3.3.2...v3.4.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.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[secure-code-warrior-for-github[bot]]

Micro-Learning Topic: Race condition (Detected by phrase)

Matched on "race condition"

What is this? (2min video)

A race condition is a flaw that produces an unexpected result when the timing of actions impact other actions.

Try a challenge in Secure Code Warrior

[performance-testing-bot[bot]]

Unable to locate .performanceTestingBot config file

[senior-dev-bot[bot]]

Hi there! :wave: Thanks for opening a PR. It looks like you've already reached the 5 review limit on our Basic Plan for the week. If you still want a review, feel free to upgrade your subscription in the Web App and then reopen the PR

[guide-bot[bot]]

Thanks for opening this Pull Request! We need you to:

1. Fill out the description.

   Action: Edit description and replace <!- ... --> with actual values.

2. Complete the activities.

   Action: Complete If you want to rebase/retry this PR, check this box

   If an activity is not applicable, use '\~activity description\~' to mark it not applicable.

[coderabbitai[bot]]

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The updates involve upgrading the version of the Gradle actions used in GitHub Actions workflows from 3.3.2 to 4.0.1. This change enhances functionality and performance in the CI/CD pipeline without altering the existing workflow logic. The modifications reflect improvements in the build process and configuration options, ensuring a smoother integration and deployment experience.

Changes

Files	Change Summary
.github/workflows/gradle-publish.yml, .github/workflows/gradle.yml	Updated setup-gradle and dependency-submission actions from version 3.3.2 to 4.0.1, likely introducing enhancements and bug fixes. No changes to workflow logic.

Poem

🐇 In the meadow, changes bloom,
Gradle's new version clears the gloom.
Actions dance with a brand new beat,
CI/CD now feels complete!
Hops of joy, let’s celebrate,
With every build, we elevate! 🌼✨

---

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 using 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. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[difflens[bot]]

View changes in DiffLens

[lang-ci[bot]]

Issues Summary

1. Cannot locate Gradle Wrapper script

Logs Summary: Error: Cannot locate Gradle Wrapper script at '/home/runner/work/PokeTown_Test/PokeTown_Test/gradlew'. Specify 'gradle-version' for projects without Gradle wrapper configured.

Failing Step:

Run ./gradlew build

Related Source Files: None

Related Failures: Java CI with Gradle / build Java CI with Gradle / dependency-submission

---

2. No file matched in target repository

Logs Summary: No file in /home/runner/work/PokeTown_Test/PokeTown_Test matched to [**/*.gradle*,**/gradle-wrapper.properties,buildSrc/**/Versions.kt,buildSrc/**/Dependencies.kt,gradle/*.versions.toml,**/versions.properties], make sure you have checked out the target repository

Failing Step:

Post job cleanup

Related Source Files: None

Related Failures: Android CI / build

---

3. Specify a project or solution file

Logs Summary: MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.

Failing Step:

Run dotnet restore

Related Source Files: None

Related Failures: .NET / build

---

4. MSBUILD error

Logs Summary: MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.

Failing Step:

Run dotnet test

Related Source Files: None

Related Failures: .NET Core Desktop / build (Debug)

---

ℹ️ Help

(You can turn this bot off by adding a comment /ai off, or force a refresh of this report with /ai ...) For more support, join our Discord channel

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens