From f5a59fffe075dd00925c98d1d0e812c28f6e820c Mon Sep 17 00:00:00 2001 From: Dmitry Ilyin <6576495+widgetii@users.noreply.github.com> Date: Thu, 18 Jun 2026 16:41:30 +0300 Subject: [PATCH] ci(release): make the Telegram binary notification non-blocking The ipctool-release run on master went red even though every build target compiled and both assets uploaded. The only hard failure was the "Send binary to Telegram" step: its `curl --max-time 15` to api.telegram.org timed out (exit 28), and unlike the surrounding `Build sources` / `Create release` steps it had no `continue-on-error`, so a flaky notification gated the whole release. A notification is advisory; it must not fail a release whose build succeeded and whose assets already uploaded. Add `continue-on-error: true` to that step (matching the existing treatment of the build and create-release steps). Note: the "Create release" step still logs a non-fatal `already_exists / tag_name` annotation because all matrix targets race to create the same `latest` tag; it is already `continue-on-error: true`, so it does not fail the run. Left as-is here. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/release.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 679e294..5166e36 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -155,6 +155,10 @@ jobs: - name: Send binary to Telegram if: steps.build.outcome == 'success' + # A notification timing out (curl exit 28 against api.telegram.org) + # must never fail a release whose build succeeded and whose assets + # already uploaded — keep it advisory. + continue-on-error: true env: TG_TOKEN: ${{ secrets.TELEGRAM_TOKEN_BOT_OPENIPC }} TG_CHANNEL: ${{ secrets.TELEGRAM_CHANNEL_OPENIPC_DEV }}