[compot-dev]

Closes #240.

After #242 basic posts nothing to Telegram; v2 posts decoder-v2.apk when its version changes (sendDocument, the caption links releases/latest), as before. The docs said both branches post:

• README (en, ru, zh-CN): every new v2 version goes to the channel as its APK.
• CHANGELOG.md header: the same; it also still said SHA256SUMS covers the release files, which is gone since Release: no SHA256SUMS, no checksum step in the docs #236.
• docs/testing.md: the table of what a run publishes (basic: decoder.apk only, nothing to Telegram) and the release section.

Docs only: no version bump.

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can move or hide resolved findings to focus on what still needs action

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Document v2-only Telegram APK posts and current release assets

📝 Documentation 🕐 10-20 Minutes

AI Description

• Clarify that only new v2 versions send an APK to Telegram; basic sends nothing.
• Correct the CI publication table and remove obsolete release checksum and basic mapping claims.
• Keep English, Russian, and Chinese download guidance consistent without changing builds or
 versions.

Diagram

graph TD
  Run["Build run"] --> V2["v2 branch"] --> Latest[("latest release")]
  Run --> Basic["basic branch"] --> Latest
  V2 --> New["New v2 version"] -->|APK| Telegram["Telegram channel"]

Loading

High-Level Assessment

Correcting the existing download, release, and testing documentation is appropriate: the publication workflow already implements the described behavior, so changing CI or introducing another documentation source would add unnecessary scope.

Files changed (5) +11 / -12

Documentation (5) +11 / -12

CHANGELOG.mdCorrect the release-history introduction +2/-3

Correct the release-history introduction

• Clarifies that Telegram receives the APK for each new 'v2' version, not builds from both branches or every build. Removes the obsolete claim that 'SHA256SUMS' covers release files.

CHANGELOG.md

README.mdClarify English Telegram download guidance +1/-1

Clarify English Telegram download guidance

• States that each new 'v2' version, rather than versions from both branches, is posted to Telegram as an APK with its commit.

README.md

README.ru.mdAlign Russian Telegram download guidance +1/-1

Align Russian Telegram download guidance

• Updates the Russian download section to describe APK posts for new 'v2' versions only.

README.ru.md

README.zh-CN.mdAlign Chinese Telegram download guidance +1/-1

Align Chinese Telegram download guidance

• Updates the Simplified Chinese download section to describe APK posts for new 'v2' versions only.

README.zh-CN.md

testing.mdCorrect the CI publication table and release guidance +6/-6

Correct the CI publication table and release guidance

• Specifies that 'v2' posts its APK to Telegram only for new versions, while 'basic' publishes 'decoder.apk' to 'latest' and posts nothing to Telegram. Removes the 'basic' release-mapping claim and aligns the release guidance with the table.

docs/testing.md