Update gradle/actions action to v3.3.2

[renovate[bot]]

This PR contains the following updates:

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

---

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

gradle/actions (gradle/actions)

### [`v3.3.2`](https://togithub.com/gradle/actions/releases/tag/v3.3.2) [Compare Source](https://togithub.com/gradle/actions/compare/v3.3.1...v3.3.2) This patch release fixes a bug in both `dependency-submission` and `setup-gradle` ([#​196](https://togithub.com/gradle/actions/issues/196) introduced in v3.3.1), which resulted in "No dependency-graph files found to submit" when using the `download-and-submit` function. A number of other minor issues have also been addressed: #### What's Changed - \[dependency-submission] Fix bug finding dependency-graph files with 'download-and-submit' ([#​199](https://togithub.com/gradle/actions/issues/199)) - \[dependency-submission] Use Gradle logger instead of println in dependency graph init script ([#​191](https://togithub.com/gradle/actions/issues/191) from [@​aleksandrserbin](https://togithub.com/aleksandrserbin)) - \[dependency-submission] Retain and log full stacktrace for dependency submission errors ([#​192](https://togithub.com/gradle/actions/issues/192)) - \[setup-gradle] Improve build scan badge readability with long task names ([#​200](https://togithub.com/gradle/actions/issues/200) from [@​gabrielfeo](https://togithub.com/gabrielfeo)) **Full Changelog**: https://github.com/gradle/actions/compare/v3.3.1...v3.3.2 ### [`v3.3.1`](https://togithub.com/gradle/actions/releases/tag/v3.3.1) [Compare Source](https://togithub.com/gradle/actions/compare/v3.3.0...v3.3.1) This patch release fixes a bug in setting the report dir for `dependency-submission`, and updates the plugin versions applied in Develocity injection. #### What's Changed - Bump Develocity and CCUD plugin versions ([#​185](https://togithub.com/gradle/actions/issues/185)) - Support custom `DEPENDENCY_GRAPH_REPORT_DIR` variable for dependency-submission ([#​188](https://togithub.com/gradle/actions/issues/188)) **Full Changelog**: https://github.com/gradle/actions/compare/v3.3.0...v3.3.1 ### [`v3.3.0`](https://togithub.com/gradle/actions/releases/tag/v3.3.0) [Compare Source](https://togithub.com/gradle/actions/compare/v3.2.1...v3.3.0) This release includes a new action, and improvements to the existing actions. Highlights include: - New [wrapper-validation](https://togithub.com/gradle/actions/tree/main/wrapper-validation) action to replace the [gradle/wrapper-validation-action](https://togithub.com/gradle/wrapper-validation-action) action - Converted [dependency-submission](https://togithub.com/gradle/actions/tree/main/dependency-submission) action to Typescript. This enabled other important features, like submitting the dependency graph in the same step that it is generated. - Better caching support for Gradle 8.6+ in [setup-gradle](https://togithub.com/gradle/actions/tree/main/setup-gradle) > \[!IMPORTANT] > The caching protocol version has changed in this release, so cache entries written with previous versions of the action will not be reused. This means that jobs will effectively start with an empty cache after switching to this release. ##### Changelog ##### NEW action `gradle/actions/wrapper-validation` - \[NEW] Add replacement for `wrapper-validation-action` ([#​160](https://togithub.com/gradle/actions/issues/160)) ##### Improvements to `gradle/actions/setup-gradle` - \[NEW] Cache paths have been updated for Gradle 8.6+ ([#​45](https://togithub.com/gradle/actions/issues/45), [#​163](https://togithub.com/gradle/actions/issues/163)) - \[NEW] `setup-gradle` action can now perform wrapper-validation automatically ([#​161](https://togithub.com/gradle/actions/issues/161), [#​162](https://togithub.com/gradle/actions/issues/162)) - \[FIX] Make cache-keys more consistent ([#​131](https://togithub.com/gradle/actions/issues/131)). - \[FIX] Avoid listing old build results in Job Summary on self-hosted runner ([#​127](https://togithub.com/gradle/actions/issues/127)) - \[FIX] Deprecation warnings are emitted when using deprecated inputs ([#​108](https://togithub.com/gradle/actions/issues/108)) - \[FIX] Generate correct `toolchains.xml` file on ARM runners ([#​89](https://togithub.com/gradle/actions/issues/89)) ##### Improvements to `gradle/actions/depenency-submission` - \[NEW] Action is now implemented directly in TypeScript, and does not delegate to `setup-gradle` ([#​116](https://togithub.com/gradle/actions/issues/116)) - \[NEW] Allow dependency resolution task name to be specified ([#​125](https://togithub.com/gradle/actions/issues/125)) - \[NEW] Dependency-graph is submitted immediately with `dependency-submission` action ([#​123](https://togithub.com/gradle/actions/issues/123)) - \[FIX] `setup-gradle` and `dependency-submission` can be used in the same Job ([#​36](https://togithub.com/gradle/actions/issues/36)) **Full Changelog**: https://github.com/gradle/actions/compare/v3.2.1...v3.3.0 ##### Actions Summary Release includes `v3.3.0` of the following, available under the `v3` version tag: - [gradle/actions/setup-gradle](https://togithub.com/gradle/actions/tree/main/setup-gradle) - [gradle/actions/dependency-submission](https://togithub.com/gradle/actions/tree/main/dependency-submission) - [gradle/actions/wrapper-validation](https://togithub.com/gradle/actions/tree/main/wrapper-validation) > \[!NOTE] > The `gradle/actions/setup-gradle` action supersedes `gradle/gradle-build-action`. > The `gradle/actions/wrapper-validation` action supersedes `gradle/wrapper-validation-action`. ### [`v3.2.1`](https://togithub.com/gradle/actions/releases/tag/v3.2.1) [Compare Source](https://togithub.com/gradle/actions/compare/v3.2.0...v3.2.1) The recent update to use `com.develocity.gradle` plugin resulted in many deprecation warnings being triggered by the init-scripts bundled with this action. This patch release updates these init-scripts to avoid these deprecation warnings. ##### What's Changed - Fix Develocity deprecation warnings in v3.2.1 ([#​126](https://togithub.com/gradle/actions/issues/126)) by [#​129](https://togithub.com/gradle/actions/issues/129) **Full Changelog**: https://github.com/gradle/actions/compare/v3.2.0...v3.2.1 ### [`v3.2.0`](https://togithub.com/gradle/actions/releases/tag/v3.2.0) [Compare Source](https://togithub.com/gradle/actions/compare/v3.1.0...v3.2.0) ##### Changelog ##### General improvements - \[NEW] Support authentication for plugin repositories ([#​31](https://togithub.com/gradle/actions/issues/31)) - \[FIX] Improve rendering of build results table with long values ([#​35](https://togithub.com/gradle/actions/issues/35)) ##### Improvements to Dependency Submission - \[FIX] Do not attempt to resolve dependency configurations that are excluded via env var ([#​107](https://togithub.com/gradle/actions/issues/107)) ##### Improvements to Develocity injection - \[NEW] Use `com.develocity.gradle` plugin version `3.17` by default - \[NEW] Can configure capture of file-fingerprint ([#​58](https://togithub.com/gradle/actions/issues/58)) - \[FIX] Reduce log-level of messages emitted by Develocity injection ([#​60](https://togithub.com/gradle/actions/issues/60)) ##### Note Release includes `v3.2.0` of `gradle/actions/setup-gradle` and `gradle/actions/dependency-submission`. Available under the `v3` version tag. The `gradle/actions/setup-gradle` action supersedes `gradle/gradle-build-action`. The `gradle/gradle-build-action@v3.2.0` version will be released in parallel, and will delegate to this release of `gradle/actions/setup-gradle`. **Full Changelog**: https://github.com/gradle/actions/compare/v3.1.0...v3.2.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 has been generated by Mend Renovate. View repository job log here.

[performance-testing-bot[bot]]

Unable to locate .performanceTestingBot config file

[coderabbitai[bot]]

[!IMPORTANT]

Auto 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.

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

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.` 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 a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration 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.

[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.

[senior-dev-bot[bot]]

Hi there! :wave: Thanks for opening a PR. :tada: To get the most out of Senior Dev, please sign up in our Web App, connect your GitHub account, and add/join your organization AdamOswald. After that, you will receive code reviews beginning on your next opened PR. :rocket:

[difflens[bot]]

View changes in DiffLens

[pull-request-quantifier-deprecated[bot]]

This PR has 6 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Extra Small Size : +3 -3 Percentile : 2.4% Total files changed: 2 Change summary by file extension: .yml : +3 -3 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[pull-request-quantifier-deprecated[bot]]

This PR has 6 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Extra Small Size : +3 -3 Percentile : 2.4% Total files changed: 2 Change summary by file extension: .yml : +3 -3 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[pull-request-quantifier-deprecated[bot]]

This PR has 6 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Extra Small Size : +3 -3 Percentile : 2.4% Total files changed: 2 Change summary by file extension: .yml : +3 -3 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[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