[pull] master from square:master

[pull]

See Commits and Changes for more details.

---

Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

Summary by CodeRabbit

• New Features

  • Introduced a new Gradle plugin, mavenSympathy, to enhance Maven-related build tasks.
  • Implemented new package rules for better dependency management in the configuration.

• Updates

  • Updated multiple libraries and plugins to their latest versions, improving functionality and security.
  • Upgraded Gradle setup actions in workflows for improved performance and stability.

• Bug Fixes

  • Removed outdated package rules, enhancing overall dependency management clarity.

[coderabbitai]

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

This update enhances dependency management and build configurations across multiple files. Key changes include new package rules in the Renovate configuration for better organization, the addition of the mavenSympathy plugin to the Gradle build script, and numerous version upgrades for dependencies in the libs.versions.toml file. Additionally, updates to the GitHub Actions workflows improve build performance and stability.

Changes

Files	Change Summary
.github/renovate.json	Added new package rules for biz.* and org.graalvm.*; removed outdated rules for Gradle and Android tools.
build.gradle.kts, samples/tlssurvey/build.gradle.kts	Added mavenSympathy plugin; applied it to enhance the build processes.
gradle/libs.versions.toml	Updated multiple dependencies and libraries, including version upgrades and new entries like retrofit.
.github/workflows/build.yml, .github/workflows/containers.yml	Upgraded Gradle setup actions from version 3 to version 4 for improved CI/CD performance.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Renovate
    participant Gradle

    Developer->>Renovate: Add new package rules
    Renovate-->>Developer: Update configuration

    Developer->>Gradle: Apply mavenSympathy plugin
    Gradle-->>Developer: Enhanced build process

Loading

🐇 In the meadow, changes bloom,
New rules and plugins make more room.
With upgrades here and versions bright,
Our project hops to new heights!
Let’s build and play, with code so fine,
A joyful dance in our codebase divine! 🌼

---

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>, please review it.
  -- 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 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 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 54238b4 and 34aa136.

Files selected for processing (7)

• .github/renovate.json (2 hunks)
• build.gradle.kts (2 hunks)
• gradle/libs.versions.toml (2 hunks)
• okhttp/src/main/kotlin/okhttp3/Dispatcher.kt (1 hunks)
• okhttp/src/main/kotlin/okhttp3/Response.kt (1 hunks)
• okhttp/src/test/java/okhttp3/internal/connection/ConnectionPoolTest.kt (2 hunks)
• samples/tlssurvey/build.gradle.kts (2 hunks)

Files skipped from review due to trivial changes (1)

• samples/tlssurvey/build.gradle.kts

Additional comments not posted (10)

build.gradle.kts (2)

29-29: Ensure compatibility of mavenSympathy plugin.

The addition of the mavenSympathy plugin to the classpath is a significant change. Ensure that this plugin is compatible with the existing build setup and does not conflict with other plugins.

---

92-92: Verify the impact of applying mavenSympathy plugin.

Applying the mavenSympathy plugin to subprojects can affect the build process. Verify that it integrates well with existing plugins and configurations.

okhttp/src/test/java/okhttp3/internal/connection/ConnectionPoolTest.kt (1)

233-235: Document the reason for disabling the test.

The connectionPreWarmingHttp2 test is disabled with a link to a GitHub issue. Ensure that the issue is actively tracked and updated to re-enable the test once resolved.

Verification successful

---

The test is appropriately disabled and documented.

The connectionPreWarmingHttp2 test is disabled due to an open issue, which is actively tracked on GitHub. Ensure that the issue is monitored and the test is re-enabled once resolved.

• GitHub Issue: OPEN: Reenable connectionPreWarmingHttp2

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the status of the GitHub issue linked to the disabled test.

# Test: Fetch the status of the GitHub issue.
gh issue view 8451 --json state,title --jq '.state + ": " + .title'

Length of output: 110

okhttp/src/main/kotlin/okhttp3/Response.kt (1)

87-87: Documentation update improves clarity.

The updated documentation for the body property provides a clearer understanding of its behavior. This change enhances the readability and maintainability of the code.

.github/renovate.json (2)

15-20: New package rule for biz.* added.

The addition of a package rule for biz.* with the group name "bnd" enhances dependency management by organizing related packages under a common group. This can streamline updates and improve clarity in the configuration.

---

21-26: New package rule for org.graalvm.* added.

The new package rule for org.graalvm.* with the group name "graalvm" helps in managing dependencies related to GraalVM more effectively. This change aligns with the project's needs for better organization.

gradle/libs.versions.toml (3)

16-16: New dependency retrofit added.

The addition of retrofit indicates an enhancement in network-related functionalities. Ensure that its integration is properly configured and compatible with other network libraries in the project.

Verification successful

---

Retrofit integration is properly configured and used. The retrofit library is actively utilized in the samples/tlssurvey module, with appropriate setup in build.gradle.kts and usage in Kotlin files for network operations. No immediate compatibility issues are evident.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of the new `retrofit` dependency.

# Test: Check for configurations and usages related to `retrofit`.
rg --type toml 'retrofit = "2.11.0"' -A 5

Length of output: 397

---

Script:

#!/bin/bash
# Search for usage of `retrofit` in Java and Kotlin files.
rg 'retrofit' --type java --type kotlin -A 5

Length of output: 2986

---

9-9: New dependency ksp added.

The introduction of ksp with version 1.9.24-1.0.20 suggests new functionality or support for Kotlin Symbol Processing. Ensure that this addition aligns with the project's requirements and does not conflict with existing configurations.

Verification successful

---

KSP Dependency Successfully Integrated

The ksp dependency is referenced in the samples/tlssurvey/build.gradle.kts file, confirming its integration for Kotlin Symbol Processing. No conflicts with existing configurations were found. Ensure that this addition aligns with your project's requirements.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of the new `ksp` dependency.

# Test: Look for usages and configurations related to `ksp`.
rg --type toml 'ksp = "1.9.24-1.0.20"' -A 5

Length of output: 368

---

Script:

#!/bin/bash
# Description: Search for references to `ksp` in build configuration files to verify integration.

# Test: Look for references to `ksp` in build configuration files.
rg 'ksp' -g '*.gradle' -A 5

Length of output: 176

---

Script:

#!/bin/bash
# Description: Search for references to `ksp` in build configuration files to verify integration.

# Test: Look for references to `ksp` in all Gradle files, ensuring the search is comprehensive.
rg 'ksp' -t gradle -A 5

Length of output: 172

---

Script:

#!/bin/bash
# Description: Search for references to `ksp` in all files to verify integration.

# Test: Look for references to `ksp` in all files across the codebase.
rg 'ksp' -A 5

Length of output: 8098

---

3-3: Version upgrade for checkStyle.

The checkStyle version has been updated from 10.15.0 to 10.17.0. This upgrade may include important bug fixes and improvements. Ensure that the new version is compatible with the project's code style configurations.

okhttp/src/main/kotlin/okhttp3/Dispatcher.kt (1)

126-126: Constructor now accepts nullable ExecutorService.

The constructor change allows executorService to be nullable, which increases flexibility. Ensure that all usages of executorService handle null values appropriately to prevent null pointer exceptions.

Verification successful

---

Constructor handles nullable ExecutorService correctly.

The Dispatcher class ensures that executorService is never null when accessed, as it initializes executorServiceOrNull if it is null. This design prevents null pointer exceptions effectively. No further action is needed.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify handling of nullable `executorService`.

# Test: Search for usages of `executorService` and ensure null checks are in place.
rg --type kotlin 'executorService' -A 5

Length of output: 13809

[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 34aa136 and babbf64.

Files selected for processing (1)

• gradle/libs.versions.toml (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• gradle/libs.versions.toml

[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 babbf64 and ee03fc2.

Files selected for processing (1)

• gradle/libs.versions.toml (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• gradle/libs.versions.toml

[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 ee03fc2 and 7da9946.

Files selected for processing (3)

• .github/workflows/build.yml (18 hunks)
• .github/workflows/containers.yml (1 hunks)
• gradle/libs.versions.toml (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• gradle/libs.versions.toml

Additional comments not posted (2)

.github/workflows/containers.yml (1)

36-36: Upgrade to Gradle setup action version 4 is approved.

Updating the Gradle setup action from version 3 to version 4 is a good practice to ensure the workflow uses the latest features and improvements.

.github/workflows/build.yml (1)

38-38: Upgrade to Gradle setup and wrapper validation actions version 4 is approved.

Updating the Gradle setup and wrapper validation actions from version 3 to version 4 across multiple jobs ensures the workflow benefits from the latest improvements and fixes, enhancing overall performance and stability.

Also applies to: 52-52, 82-82, 111-111, 153-153, 181-181, 215-215, 243-243, 271-271, 299-299, 328-328, 357-357, 392-392, 421-421, 450-450, 456-456, 503-503, 575-575, 619-619

[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 7da9946 and 9ed9dfe.

Files selected for processing (1)

• gradle/libs.versions.toml (2 hunks)

Additional comments not posted (27)

gradle/libs.versions.toml (27)

13-13: Upgrade org-jetbrains-coroutines version.

The org-jetbrains-coroutines version has been updated from 1.8.0 to 1.8.1. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new org-jetbrains-coroutines version:

---

3-3: Upgrade checkStyle version.

The checkStyle version has been updated from 10.15.0 to 10.18.0. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new checkStyle version:

---

16-16: Add new dependency retrofit.

The new dependency retrofit has been added with version 2.11.0. Ensure that this new dependency is correctly integrated and does not introduce any issues.

Run the following script to verify the integration of the new retrofit dependency:

---

20-20: Add new dependency amazonCorretto.

The new dependency amazonCorretto has been added with version 2.4.1. Ensure that this new dependency is correctly integrated and does not introduce any issues.

Run the following script to verify the integration of the new amazonCorretto dependency:

Verification successful

---

Integration of amazonCorretto Dependency Verified Successfully

The amazonCorretto dependency is correctly integrated and actively used in the codebase, specifically in the PlatformRule.kt file. Its exclusion in the test configuration appears intentional and does not indicate an integration issue. No further action is required.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of the new `amazonCorretto` dependency.

# Test: Check for any issues with the new dependency.
./gradlew build

Length of output: 202

---

Script:

#!/bin/bash
# Search for usage of the amazonCorretto dependency in the codebase

# Look for import statements or references to AmazonCorrettoCryptoProvider
rg 'import.*AmazonCorrettoCryptoProvider' -A 3
rg 'AmazonCorrettoCryptoProvider' -A 3

Length of output: 3422

---

15-15: Upgrade org-junit-jupiter version.

The org-junit-jupiter version has been updated from 5.10.2 to 5.10.3. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new org-junit-jupiter version:

---

14-14: Upgrade org-jetbrains-kotlin version.

The org-jetbrains-kotlin version has been updated from 1.9.23 to 1.9.25. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new org-jetbrains-kotlin version:

---

26-26: Upgrade animalsniffer-annotations version.

The animalsniffer-annotations version has been updated from 1.23 to 1.24. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new animalsniffer-annotations version:

---

6-6: Upgrade de-mannodermaus-junit5 version.

The de-mannodermaus-junit5 version has been updated from 1.4.0 to 1.5.0. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new de-mannodermaus-junit5 version:

---

9-9: Add new dependency ksp.

The new dependency ksp has been added with version 1.9.24-1.0.20. Ensure that this new dependency is correctly integrated and does not introduce any issues.

Run the following script to verify the integration of the new ksp dependency:

---

47-47: Upgrade gradlePlugin-errorprone version.

The gradlePlugin-errorprone version has been updated from 3.1.0 to 4.0.1. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new gradlePlugin-errorprone version:

---

66-66: Upgrade junit-platform-console version.

The junit-platform-console version has been updated from 1.10.2 to 1.10.3. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new junit-platform-console version:

Verification successful

---

No issues found with junit-platform-console upgrade.

The upgrade from version 1.10.2 to 1.10.3 of junit-platform-console does not appear to introduce any compatibility issues or breaking changes, as there are no specific usages or configurations found in the codebase.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the compatibility of the new `junit-platform-console` version.

# Test: Check for any breaking changes or issues with the new version.
./gradlew test

Length of output: 201

---

Script:

#!/bin/bash
# Search for references to `junit-platform-console` in the codebase
rg "junit-platform-console" -A 5

Length of output: 738

---

52-52: Add new dependency gradlePlugin-mavenSympathy.

The new dependency gradlePlugin-mavenSympathy has been added with version 0.3.0. Ensure that this new dependency is correctly integrated and does not introduce any issues.

Run the following script to verify the integration of the new gradlePlugin-mavenSympathy dependency:

---

38-38: Add new dependency converter-moshi.

The new dependency converter-moshi has been added with a reference to the retrofit version. Ensure that this new dependency is correctly integrated and does not introduce any issues.

Run the following script to verify the integration of the new converter-moshi dependency:

---

55-55: Upgrade guava-jre version.

The guava-jre version has been updated from 33.2.0-jre to 33.3.0-jre. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new guava-jre version:

---

67-67: Upgrade junit-vintage-engine version.

The junit-vintage-engine version has been updated from 5.10.2 to 5.10.3. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new junit-vintage-engine version:

---

51-51: Upgrade gradlePlugin-mavenPublish version.

The gradlePlugin-mavenPublish version has been updated from 0.28.0 to 0.29.0. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new gradlePlugin-mavenPublish version:

---

28-28: Upgrade assertk version.

The assertk version has been updated from 0.28.0 to 0.28.1. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new assertk version:

---

62-62: Upgrade junit-ktx version.

The junit-ktx version has been updated from 1.1.5 to 1.2.1. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new junit-ktx version:

---

57-57: Upgrade httpClient5 version.

The httpClient5 version has been updated from 5.3 to 5.3.1. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new httpClient5 version:

---

88-88: Add new dependency retrofit.

The new dependency retrofit has been added with a reference to the retrofit version. Ensure that this new dependency is correctly integrated and does not introduce any issues.

Run the following script to verify the integration of the new retrofit dependency:

Verification successful

---

Retrofit dependency integration appears correct. The retrofit dependency is referenced in the samples/tlssurvey/build.gradle.kts file and is actively used in the SslLabsClient.kt and SslLabsApi.kt files, indicating proper integration. No issues were found related to its integration.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the integration of the new `retrofit` dependency.

# Test: Check for any issues with the new dependency.
./gradlew build

Length of output: 202

---

Script:

#!/bin/bash
# Search for references to `retrofit` in the codebase to verify its integration.
rg 'retrofit' --glob '!gradle/libs.versions.toml' -A 5

Length of output: 3630

---

44-44: Upgrade gradlePlugin-binaryCompatibilityValidator version.

The gradlePlugin-binaryCompatibilityValidator version has been updated from 0.14.0 to 0.16.3. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new gradlePlugin-binaryCompatibilityValidator version:

---

87-87: Upgrade playservices-safetynet version.

The playservices-safetynet version has been updated from 18.0.1 to 18.1.0. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new playservices-safetynet version:

---

42-42: Upgrade gradlePlugin-androidJunit5 version.

The gradlePlugin-androidJunit5 version has been updated from 1.10.0.0 to 1.11.0.0. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new gradlePlugin-androidJunit5 version:

---

90-90: Upgrade robolectric version.

The robolectric version has been updated from 4.12.1 to 4.12.2. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new robolectric version:

---

97-97: Upgrade squareup-kotlinPoet version.

The squareup-kotlinPoet version has been updated from 1.16.0 to 1.17.0. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new squareup-kotlinPoet version:

---

60-60: Upgrade jsoup version.

The jsoup version has been updated from 1.17.2 to 1.18.1. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new jsoup version:

---

34-34: Upgrade clikt version.

The clikt version has been updated from 4.3.0 to 4.4.0. Ensure that the new version is compatible with the rest of the project and does not introduce any breaking changes.

Run the following script to verify the compatibility of the new clikt version:

Verification successful

---

No breaking changes found for clikt version 4.4.0.

The changelog for version 4.4.0 does not indicate any breaking changes or deprecations that would affect the components used in your project (CliktCommand, argument, default, flag, multiple, option, int). The update should be compatible with your current usage.

• Ensure to test your application thoroughly to confirm compatibility.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the compatibility of the new `clikt` version.

# Test: Check for any breaking changes or issues with the new version.
./gradlew build

Length of output: 202

---

Script:

#!/bin/bash
# Search for imports of clikt in the codebase to identify usage locations.
ast-grep --lang kotlin --pattern 'import com.github.ajalt.clikt.$$$'

Length of output: 783

---

Script:

#!/bin/bash
# Search for a changelog or release notes file in the repository.
fd -i 'changelog*' --type f

Length of output: 170

---

Script:

#!/bin/bash
# Extract and display relevant sections from the changelog for version 4.x to identify breaking changes.
grep -A 10 -i "4.4.0" docs/changelogs/changelog_4x.md

Length of output: 1343

[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 9ed9dfe and 28075d7.

Files selected for processing (1)

• gradle/libs.versions.toml (2 hunks)

Additional comments not posted (21)

gradle/libs.versions.toml (21)

3-3: LGTM!

The checkStyle version update from 10.15.0 to 10.18.0 ensures the project uses the latest features and fixes.

---

6-6: LGTM!

The de-mannodermaus-junit5 version update from 1.4.0 to 1.5.0 ensures the project uses the latest features and fixes.

---

9-9: LGTM!

The addition of ksp with version 1.9.24-1.0.20 provides support for Kotlin Symbol Processing, enhancing build performance and developer productivity.

---

13-13: LGTM!

The org-jetbrains-coroutines version update from 1.8.0 to 1.8.1 ensures the project uses the latest features and fixes.

---

14-14: LGTM!

The org-jetbrains-kotlin version update from 1.9.23 to 1.9.25 ensures the project uses the latest features and fixes.

---

15-15: LGTM!

The org-junit-jupiter version update from 5.10.2 to 5.11.0 ensures the project uses the latest features and fixes.

---

16-16: LGTM!

The addition of retrofit with version 2.11.0 enhances the project's networking capabilities with a type-safe HTTP client for Android and Java.

---

20-20: LGTM!

The amazonCorretto version update from 2.4.0 to 2.4.1 ensures the project uses the latest features and fixes.

---

26-26: LGTM!

The animalsniffer-annotations version update from 1.23 to 1.24 ensures the project uses the latest features and fixes.

---

28-28: LGTM!

The assertk version update from 0.28.0 to 0.28.1 ensures the project uses the latest features and fixes.

---

34-34: LGTM!

The clikt version update from 4.3.0 to 4.4.0 ensures the project uses the latest features and fixes.

---

38-38: LGTM!

The addition of converter-moshi with version 2.11.0 enhances the project's JSON parsing capabilities using Moshi.

---

44-44: LGTM!

The gradlePlugin-binaryCompatibilityValidator version update from 0.14.0 to 0.16.3 ensures the project uses the latest features and fixes.

---

47-47: LGTM!

The gradlePlugin-errorprone version update from 3.1.0 to 4.0.1 ensures the project uses the latest features and fixes.

---

55-55: LGTM!

The guava-jre version update from 33.2.0-jre to 33.3.0-jre ensures the project uses the latest features and fixes.

---

57-57: LGTM!

The httpClient5 version update from 5.3 to 5.3.1 ensures the project uses the latest features and fixes.

---

60-60: LGTM!

The jsoup version update from 1.17.2 to 1.18.1 ensures the project uses the latest features and fixes.

---

87-87: LGTM!

The playservices-safetynet version update from 18.0.1 to 18.1.0 ensures the project uses the latest features and fixes.

---

88-88: LGTM!

The addition of retrofit with version 2.11.0 enhances the project's networking capabilities with a type-safe HTTP client for Android and Java.

---

90-90: LGTM!

The robolectric version update from 4.12.1 to 4.12.2 ensures the project uses the latest features and fixes.

---

97-97: LGTM!

The squareup-kotlinPoet version update from 1.16.0 to 1.17.0 ensures the project uses the latest features and fixes.