[compot-dev]

Closes #58.

• The release job's Telegram step no longer sends a text post (sendMessage with a CHANGELOG.md excerpt, as it did for 1.9.0). For a new version it sends the release binaries as files — vectis-linux-x86_64, vectis-linux-mipsel (dist/vectis-linux-*) — in one sendMediaGroup post, with a short caption on the last one: Vectis <version> for Linux, commit, time, releases/latest. The channel is for build files (archive, test downloads), as OpenIPC/vtesse, OpenIPC/decoder and OpenIPC/camex post their APKs.
• Still only for a new version; missing secrets or a failed upload are a warning, the release stays.
• READMEs (all three): "the binaries of every new version are also posted to the OpenIPC Telegram channel" instead of "every new version is announced".

Tested in compot/cross with curl stubbed (nothing sent): without secrets a warning and exit 0; with them one sendMediaGroup call with both binaries attached (f0, f1) and a valid media JSON (checked with jq), the caption on the last document. Workflow and docs only: no version bump, so merging posts nothing.

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

PR Summary by Qodo

Post new-version binaries to Telegram as one media group

✨ Enhancement ⚙️ Configuration changes 📝 Documentation 🕐 10-20 Minutes

AI Description

• Replace Telegram text announcements with one post containing both Linux release binaries.
• Keep posting limited to new versions; missing secrets or upload failures remain warnings.
• Update three READMEs to describe Telegram as a source for archive and test downloads.

Diagram

graph TD
  A["Verified binaries"] --> B["Publish latest"] --> C{"New version?"} -->|Yes| D{"Secrets present?"} -->|Yes| E["Upload media group"] -->|Success| F["Telegram channel"]
  C -->|No| G["No post"]
  D -->|No| H["Warn only"]
  E -->|Failure| H

Loading

High-Level Assessment

Using the existing verified dist binaries and a single sendMediaGroup request fits the channel's file-oriented purpose. Separate sendDocument calls would fragment each release across posts; retaining the text announcement would not provide downloadable binaries.

Files changed (4) +20 / -15

Enhancement (1) +17 / -12

build.ymlUpload new-version binaries to Telegram as documents +17/-12

Upload new-version binaries to Telegram as documents

• Replaces the changelog-based sendMessage step with a sendMediaGroup upload of dist/vectis-linux-* and a short caption on the last document. Preserves the new-version gate and treats missing secrets or upload failures as warnings.

.github/workflows/build.yml

Documentation (3) +3 / -3

README.mdClarify Telegram binary availability in English +1/-1

Clarify Telegram binary availability in English

• States that binaries for each new version are posted to the OpenIPC Telegram channel for archive and test downloads, rather than announced there.

README.md

README.ru.mdClarify Telegram binary availability in Russian +1/-1

Clarify Telegram binary availability in Russian

• Changes the release-channel description from version announcements to binary posts for archive and test downloads.

README.ru.md

README.zh-CN.mdClarify Telegram binary availability in Chinese +1/-1

Clarify Telegram binary availability in Chinese

• Changes the release-channel description from version announcements to binary posts for archive and test downloads.

README.zh-CN.md

[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 see how risky a PR is at a glance with blast radius labels

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗