Skip to content

Telegram: which release files to post #240

Closed
#243
Closed
Telegram: which release files to post#240
#243
Labels
uniRelease naming and management, common across the repositories

Description

@compot-dev
compot-dev
opened on Oct 18, 2026

On a new version the Telegram channel gets only the APK from this repository, while OpenIPC/vectis and OpenIPC/cerberus post all the release binaries (one sendMediaGroup post, short caption).

Decision needed: post all the files of the release, or keep only the APK where there is one.

Activity

  1. compot-dev
    added
    uniRelease naming and management, common across the repositories
    on Oct 18, 2026

  2. compot-dev commented on Oct 18, 2026

    @compot-dev
    compot-dev
    on Oct 18, 2026
    CollaboratorAuthor

    Decision: post all the files of the release in one post (sendMediaGroup, caption on the last file; sendDocument for a single file). The caption links releases/latest.

  3. compot-dev commented on Oct 18, 2026

    @compot-dev
    compot-dev
    on Oct 18, 2026
    CollaboratorAuthor

    Decision: Telegram gets only decoder-v2.apk, when the v2 version changes. basic (decoder.apk) and decoder-v2-mapping.txt are not posted. The caption links releases/latest.

  4. compot-dev
    added 2 commits that reference this issue on Oct 18, 2026

    Merge pull request #242 from OpenIPC/basic-no-telegram

    9702df8

    Merge pull request #243 from OpenIPC/docs-telegram-v2-only

    4aefb1e
  5. compot-dev
    closed this as completedin #243on Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    uniRelease naming and management, common across the repositories

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions