build: update TPStreamsAndroidPlayer dependency to version 1.0.5

[Gowreesh-A-M]

Summary by CodeRabbit

• Chores
  • Updated the TPStreamsAndroidPlayer dependency to version 1.0.5.

[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 dependency version for com.github.testpress:TPStreamsAndroidPlayer in the Android build configuration was updated from 1.0.4 to 1.0.5. No other modifications were made to the build file or project configuration.

Changes

File(s)	Change Summary
android/build.gradle	Updated TPStreamsAndroidPlayer dependency from 1.0.4 to 1.0.5

Possibly related PRs

• build: update TPStreamsAndroidPlayer dependency to version 1.0.4 #8: Updated the same dependency in android/build.gradle from version 1.0.1 to 1.0.4, preceding this version increment.

Poem

A hop and a skip, a version anew,
TPStreamsAndroidPlayer, now 1.0.5 for you!
With builds that are fresh and dependencies tight,
The code hops forward, all through the night.
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3268523 and 6efe374.

📒 Files selected for processing (1)

• android/build.gradle (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

android/build.gradle (1)

Learnt from: syed-tp
PR: testpress/react-native-tpstreams#2
File: android/src/main/java/com/tpstreams/TPStreamsDownloadModule.kt:32-40
Timestamp: 2025-06-17T15:45:22.435Z
Learning: In the react-native-tpstreams project, there's a naming convention where the same identifier is called "assetId" in the Android SDK but "videoId" in the React/JavaScript layer. The React Native bridge intentionally maps item.assetId to the "videoId" key to maintain consistency with React naming conventions.

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

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

🔇 Additional comments (1)

android/build.gradle (1)

83-86: Dependency bump looks fine, but please confirm the artifact is resolvable from JitPack

1.0.5 should correspond to a published tag / release on GitHub.
Before merging, make sure the artifact actually exists (JitPack occasionally fails to build new tags) and that no additional transitive‐dependency upgrades break your compile / min SDK matrix.

#!/bin/bash
# Quick sanity-check: verify that the POM for 1.0.5 is downloadable.
curl -s -o /dev/null -w '%{http_code}\n' \
  https://jitpack.io/com/github/testpress/TPStreamsAndroidPlayer/1.0.5/TPStreamsAndroidPlayer-1.0.5.pom
# Expect: 200

---

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