Rollback Telegram library upgrade

[rob93c]

Summary by CodeRabbit

• Chores
  • Updated the Telegram bot library to an earlier, more stable version.
• Refactor
  • Simplified the bot's messaging reply process by switching from a parameter-based method to a direct message identifier approach, streamlining how responses are handled.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request performs two main changes. First, it downgrades the telegram-bot-api library version in the Gradle configuration from 8.3.0 to 8.1.0. Second, within the Stickerify.java file, it removes the use of the ReplyParameters class in favour of directly referencing the message ID using replyToMessageId when replying to Telegram requests. No modifications to public APIs have been made.

Changes

File(s)	Change Summary
gradle/libs.versions.toml	Downgraded telegram-bot-api version from 8.3.0 to 8.1.0.
src/main/java/.../Stickerify.java	Removed the ReplyParameters class and replaced its usage with replyToMessageId for constructing reply messages.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant S as Stickerify Bot
    participant T as Telegram API
    U->>S: Sends message (with messageId)
    S->>T: Processes incoming message
    alt New Flow
        S->>T: Reply using replyToMessageId(messageId)
    else Old Flow
        S->>T: Reply using ReplyParameters(messageId)
    end

Loading

Suggested labels

enhancement

Suggested reviewers

• MartelliEnrico

Poem

Hoppin' through the code, I dance with glee,
A rabbit's trail of change for all to see.
Versions downgraded, replies now refined,
With every leap, new clarity we find.
ASCII hops and rabbit cheers, code smiles so free!
🐰💻

---

📜 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 909c57b and d77ead0.

📒 Files selected for processing (2)

• gradle/libs.versions.toml (1 hunks)
• src/main/java/com/github/stickerifier/stickerify/bot/Stickerify.java (2 hunks)

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

• GitHub Check: Execute unit tests (macos-13)
• GitHub Check: Execute unit tests (windows-latest)
• GitHub Check: Execute unit tests (ubuntu-latest)
• GitHub Check: Build and upload Docker image

🔇 Additional comments (3)

src/main/java/com/github/stickerifier/stickerify/bot/Stickerify.java (2)

130-134: LGTM! The reply parameter change aligns with the library downgrade.

The modification from ReplyParameters to replyToMessageId maintains the same functionality whilst being compatible with the older library version.

---

197-200: LGTM! The reply parameter change aligns with the library downgrade.

The modification from ReplyParameters to replyToMessageId maintains the same functionality whilst being compatible with the older library version.

gradle/libs.versions.toml (1)

23-23:

Details

✅ Verification successful

Verify the security and stability of the downgraded version.

Let's ensure that version 8.1.0 of the telegram-bot-api library is secure and stable.

---

🌐 Web query:

Are there any known security vulnerabilities in java-telegram-bot-api version 8.1.0?

💡 Result:

The java-telegram-bot-api library version 8.1.0 (maintained by com.github.pengrad) does not have any directly reported security vulnerabilities according to available data[4][7]. However, developers should consider:

Key observations:

• Snyk's vulnerability database shows no direct vulnerabilities for this specific package[7]
• The library depends on:
  • OkHttp 4.12.0 (no known CVEs at time of release)
  • Gson 2.10.1 (no known CVEs at time of release)

Related considerations:

1. The Telegram Bot API itself had historical vulnerabilities like CVE-2019-{NUMBER} (2019 TLS/MiTM weakness)[3], but these were protocol-level issues rather than library flaws
2. Connection handling should implement proper error recovery to avoid service disruptions from TCP timeouts[2]
3. Authentication/authorization must be properly implemented when using chat IDs to prevent "chat not found" errors and potential misdelivery[5]

While no specific vulnerabilities exist in version 8.1.0, developers should:

• Monitor dependency updates (particularly OkHttp/Gson)
• Implement message validation to prevent injection attacks
• Use HTTPS exclusively for API communication
• Handle connection resets gracefully as shown in error patterns from other implementations[2][5]

The library appears maintained with recent updates addressing API changes[8][10], suggesting active development and likely prompt patching if vulnerabilities emerge[4][10].

Citations:

• 1: https://www.cisa.gov/news-events/bulletins/sb24-120
• 2: https://community.koyeb.com/t/telegram-bot-loses-connection/194
• 3: https://latesthackingnews.com/2019/01/22/vulnerability-in-telegram-bot-api-encryption-allows-access-to-messages/
• 4: https://central.sonatype.com/artifact/com.github.pengrad/java-telegram-bot-api
• 5: https://community.make.com/t/telegram-bot-chatid-value-must-not-be-empty-and-400-bad-request-chat-not-found/68872
• 6: https://mergebase.com/blog/java-vulnerabilities/
• 7: https://security.snyk.io/package/npm/telegram-bot-api-c/8.1.0
• 8: https://github.com/InsanusMokrassar/ktgbotapi/blob/master/CHANGELOG.md
• 9: https://www.ibm.com/support/pages/security-bulletin-multiple-vulnerabilities-ibm-java-runtime-affecting-tivoli-netcoolomnibus-1
• 10: https://github.com/pengrad/java-telegram-bot-api/releases

---

Security and Stability Verification

The downgraded version 8.1.0 of the telegram-bot-api library has been verified against publicly available data and shows no directly reported security vulnerabilities. The dependency checks (notably OkHttp 4.12.0 and Gson 2.10.1) also indicate these components are free from known CVEs. Nonetheless, please ensure to:

• Keep monitoring dependency updates (especially for OkHttp and Gson).
• Implement robust error handling for connection and timeout issues.
• Maintain proper message validation and use HTTPS to secure API communications.

Overall, the version appears secure and stable based on current information.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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>, 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 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 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.