[compot-dev]

Closes #40. @keyldev: this replaces the text post of #38 before it ever runs here (0.3.2 would have been the first).

• The OpenIPC Telegram dev channel is for build files (archive, test downloads), not text announcements — the same sendMessage post with a CHANGELOG.md excerpt went out from OpenIPC/vectis for 1.9.0 and was not wanted. The release job's Telegram step now sends the four cerberus-<arch> binaries as files in one sendMediaGroup post, with a short caption on the last one: Cerberus <version> for Linux, commit, time, releases/latest.
• Still only for a new version (announce, not a re-publication of the same 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".

Tested in compot/cross with curl stubbed (nothing sent): one sendMediaGroup call with the four binaries attached and a valid media JSON, the caption on the last document. Workflow and docs only: no version bump.

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

PR Summary by Qodo

Post new-release binaries to Telegram instead of text announcements

✨ Enhancement 📝 Documentation 🕐 10-20 Minutes

AI Description

• Send four release binaries in one Telegram post instead of a changelog announcement.
• Post only for new versions; missing secrets or upload failures do not fail the release.
• Clarify the binary-posting policy in the English, Russian, and Chinese READMEs.

Diagram

graph TD
  V{"New version?"} -->|yes| A["Release binaries"] --> S{"Secrets present?"} -->|yes| M["Media group"] --> T["Telegram API"] --> C["Dev channel"]
  V -->|no| X["Skip posting"]
  S -->|no| W["Warning only"]
  T -->|upload fails| W

Loading

High-Level Assessment

A single sendMediaGroup request fits the channel's file-sharing purpose and keeps the four binaries together. Separate sendDocument posts would fragment each release, while retaining the text announcement would not meet the channel's needs.

Files changed (4) +22 / -20

Enhancement (1) +19 / -17

ci.ymlReplace Telegram text announcements with binary uploads +19/-17

Replace Telegram text announcements with binary uploads

• For new versions, the release step sends the dist/cerberus-* binaries as documents in one sendMediaGroup request, with version, commit, time, and release link in the last document's caption. It removes the changelog excerpt and retains warning-only behavior for missing secrets or upload failure.

.github/workflows/ci.yml

Documentation (3) +3 / -3

README.mdDescribe Telegram binary posts in English +1/-1

Describe Telegram binary posts in English

• Clarifies that binaries of each new version are posted to the OpenIPC Telegram channel for archival and test downloads, rather than announced as text.

README.md

README.ru.mdDescribe Telegram binary posts in Russian +1/-1

Describe Telegram binary posts in Russian

• Updates the Russian release guidance to describe binary uploads for archival and test downloads.

README.ru.md

README.zh-CN.mdDescribe Telegram binary posts in Chinese +1/-1

Describe Telegram binary posts in Chinese

• Updates the Chinese release guidance to describe binary uploads for archival 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 ↗