ci: Telegram gets all the release files in one post (#70)

[compot-dev]

Closes #70.

On a new version the Telegram channel now gets all the release files in one post instead of the APK only: sendMediaGroup with the 8 files (camex-<arch>, camex-android.apk, camex-macos.zip, camex-windows-<arch>.zip), the caption on the last one, the same way OpenIPC/vectis and OpenIPC/cerberus post. A single file would go with sendDocument; more than 10 files (the Telegram limit for one post) are not posted, with a warning. The caption is "Camex ", the commit, the time and the permanent link releases/latest (was releases/tag/latest). Still only when the version changes; a failed upload stays a warning.

The release files themselves do not change, so this carries no-release.

Checked locally in Docker: the step with a stub curl on 8 empty files builds one sendMediaGroup request with attach://f0…f7 and the caption on the last item; on one file it calls sendDocument. shellcheck v0.10.0 clean on the step; the workflow parses as YAML.

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

PR Summary by Qodo

Post all release files in one Telegram message

✨ Enhancement ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Send all eight release assets in one Telegram post instead of posting only the APK.
• Link the caption to the permanent latest-release page and retain version-change gating.
• Warn without failing the release if uploads fail or exceed Telegram’s ten-file limit.

Diagram

graph TD
  R["Release assets"] --> V{"New version?"} -->|Yes| C{"File count?"} -->|"2-10"| G["Media group"] --> T["Telegram API"]
  C -->|"1"| S["Single document"] --> T
  C -->|">10"| W["Skip with warning"]
  V -->|No| N["No post"]

Loading

High-Level Assessment

The direct Telegram API approach fits the existing workflow and the one-post requirement. Splitting larger releases into batches would change that behavior; warning instead is consistent with the stated ten-file limit.

Files changed (1) +26 / -8

Enhancement (1) +26 / -8

build.ymlPost every release asset to Telegram in one message +26/-8

Post every release asset to Telegram in one message

• The Telegram step now sends the collected release files as a media group, with a single-document path for one file and a warning when there are more than ten. Its caption links to releases/latest; the existing new-version condition and non-fatal upload warnings remain. Release asset creation is unchanged.

.github/workflows/build.yml

[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 ↗