build(deps): Gradle 8.6

[yuriytkach]

Summary by CodeRabbit

• Chores
  • Updated the Gradle distribution to version 8.6 to enhance build performance and compatibility.

[coderabbitai]

Walkthrough

The project's Gradle version has been upgraded from 8.1.1 to 8.6. This update involves changing the distribution URL in the Gradle wrapper properties file, ensuring compatibility with newer features and improvements in build performance and security.

Changes

File Path	Change Summary
gradle/wrapper/gradle-wrapper.properties	Updated Gradle from version 8.1.1 to 8.6

🐇✨
In the realm of code where binaries lay,
A tiny change sweeps old away.
From 8.1 to 8.6 we hop,
With every build, we cannot stop.
Oh, how smooth the builds will flow,
Onward, upward, let us go! 🚀
🐇✨

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 654f024 and d0e763b.

Files selected for processing (1)

• gradle/wrapper/gradle-wrapper.properties (1 hunks)

Files skipped from review due to trivial changes (1)

• gradle/wrapper/gradle-wrapper.properties

---

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.

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

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: Use 'final' keyword for all function parameters and local variables, including exception declarations.
• Apply: Use 'ex' for exception variable in catch clause.
• Apply: Prefer stream api over loops, prefer functional style code.
• Apply: All new business logic should have corresponding unit tests.
• Apply: Refactor large functions to be more modular.
• Apply: Add javadoc to all functions except one-liners.
• Apply: Update the README.md file whenever a new feature is added. Make sure to include a description of the feature and any new commands.
• Apply: Fix Codacy Static Code Analysis issues

This is an automated message generated by Sweep AI.

[github-actions]

Test Results

 23 files   23 suites   10s ⏱️
157 tests 157 ✅ 0 💤 0 ❌
163 runs  163 ✅ 0 💤 0 ❌

Results for commit d0e763b.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 654f0241	✅ ∅ (target: 92.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (654f024)	Report Missing	Report Missing	Report Missing
Head commit (d0e763b)	838	781	93.20%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#260)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy will stop sending the deprecated coverage status from June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩