The release workflow had no mechanism to deliver user-facing documentation as PDFs alongside the binary artifacts.

Changes

.github/workflows/release.yml

• New parallel job build-user-manuals (runs after quality-gate, alongside the three platform builds):
  • Installs pandoc + weasyprint (Python-based PDF engine, no LaTeX)
  • Iterates over all *.md files in telegram/telegram-cli/manuals/, converts each to PDF, collects output in user_manuals/
  • Uploads the directory as artifact telegram-cli-manuals
• release job: added build-user-manuals to needs; added release-assets/*.pdf to the release files list — the existing download-artifact step (no name filter, merge-multiple: true) already pulls all artifacts, so PDFs land flat in release-assets/ automatically

build-user-manuals:
  needs: [quality-gate]
  runs-on: ubuntu-latest
  steps:
    - uses: actions/checkout@v5
    - name: Install pandoc and weasyprint
      run: |
        sudo apt-get update -q && sudo apt-get install -y pandoc
        pip install weasyprint
    - name: Convert manuals to PDF
      run: |
        mkdir -p user_manuals
        for f in telegram/telegram-cli/manuals/*.md; do
          base=$(basename "$f" .md)
          pandoc "$f" -o "user_manuals/${base}.pdf" --pdf-engine=weasyprint
        done
    - uses: actions/upload-artifact@v5
      with:
        name: telegram-cli-manuals
        path: user_manuals/

Version bump: telegram/telegram-cli → 1.1.2 (build 55)

Created from VS Code.

⚡ Quickly spin up Copilot coding agent tasks from anywhere on your macOS or Windows machine with Raycast.