build: upgrade dependencies

[Gowreesh-A-M]

• Update kotlinVersion from 2.0.21 to 2.2.0
• Upgrade TPStreamsAndroidPlayer from 1.0.1 to 1.0.2

Summary by CodeRabbit

• Chores
  • Updated the TPStreamsAndroidPlayer library to version 1.0.2.
  • Upgraded Kotlin version to 2.2.0 for improved compatibility and performance.
  • Ensured the Kotlin Gradle plugin version matches the updated Kotlin version in the build configuration.

[codetortoiseai]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Walkthrough

The updates focus on dependency and version management for the Android project. The TPStreamsAndroidPlayer library version is incremented, and the Kotlin version is updated across relevant configuration files. The Kotlin Gradle plugin dependency is also modified to reference the centralized Kotlin version variable for consistency.

Changes

File(s)	Change Summary
android/build.gradle	Updated TPStreamsAndroidPlayer dependency from 1.0.1 to 1.0.2.
android/gradle.properties	Updated Kotlin version from 2.0.21 to 2.2.0.
example/android/build.gradle	Updated Kotlin version to 2.2.0 and modified plugin dependency to use the kotlinVersion variable.

Poem

Hopping through the code with glee,
Dependencies fresh as spring can be!
Kotlin now shines at version two point two,
And streams play smoother, all shiny and new.
With tidy configs and carrots in hand,
This bunny’s proud of the code so grand!
🥕✨

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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

🧹 Nitpick comments (2)

android/build.gradle (2)

80-86: Consider externalising TPStreamsAndroidPlayer version

Hard-coding 1.0.2 makes the next bump manual in multiple places. Placing it alongside the other version constants in gradle.properties (e.g. Tpstreams_tpPlayerVersion) keeps version management single-sourced and avoids accidental drift between example & library modules.

-implementation 'com.github.testpress:TPStreamsAndroidPlayer:1.0.2'
+def tpPlayerVersion = getExtOrDefault("tpPlayerVersion")
+implementation "com.github.testpress:TPStreamsAndroidPlayer:$tpPlayerVersion"

Remember to add Tpstreams_tpPlayerVersion=1.0.2 to gradle.properties.

---

14-16: Now that plugin & stdlib share the same property, drop the “DifferentKotlinGradleVersion” suppression

The lint warning was relevant when the Gradle plugin version was pinned differently. With ${getExtOrDefault('kotlinVersion')} driving both, the suppression can be removed to keep the build file tidy.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3b3ba9e and e8bec21.

📒 Files selected for processing (3)

• android/build.gradle (1 hunks)
• android/gradle.properties (1 hunks)
• example/android/build.gradle (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build-android
• GitHub Check: build-ios

🔇 Additional comments (2)

android/gradle.properties (1)

1-1: Verify Kotlin 2.2.0–AGP 8.7.2 compatibility before merging

Jumping two minor releases is generally safe, but Kotlin 2.2.0 is still very fresh and AGP 8.7.2 is likewise on the bleeding edge. Please run a full CI build (including unit tests and ProGuard/R8 if applicable) to surface any compiler / byte-code incompatibilities or IDE lint regressions before tagging a release.

#!/bin/bash
# Quick sanity-check: look for compile / lint errors related to Kotlin 2.2.0.
# We only scan Gradle output logs produced by CI (assuming they live under build/).
fd -e log 'gradle' build | xargs grep -i -e 'Unsupported Kotlin version' -e 'deprecated' -e 'error'

example/android/build.gradle (1)

8-18: 👍 Kotlin version hook-up looks good

The example module now re-uses the kotlinVersion property, ensuring the Gradle plugin and stdlib stay in lock-step with the library module. No further action required here.