From dc1f1f3589845d0975a389bff82e6ad97aaf48c3 Mon Sep 17 00:00:00 2001 From: AminDhouib Date: Tue, 15 Sep 2026 20:24:47 -0400 Subject: [PATCH] ci: add per-job timeout-minutes to the release notification workflow Both notification jobs could previously run until the GitHub 6 h ceiling. A webhook POST that never returns therefore held a runner slot for hours. Each job now carries an explicit timeout-minutes. Rule: the budget is 3 x the job's observed p90 duration, rounded up to the nearest 5 minutes. Where 72 h of run history contains no completed sample for a job, the class default for that job's class is used instead. Both jobs below fall in the second case. .github/workflows/notify.yml discord_notify 15 class default (deploy/notify), unobserved slack_release_notify 15 class default (deploy/notify), unobserved No concurrency change: notify.yml is triggered by release:published, so each run corresponds to a distinct release and no run supersedes another. The other workflows in this repository already declare their own concurrency groups. Job names, job count and workflow triggers are unchanged. --- .github/workflows/notify.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/notify.yml b/.github/workflows/notify.yml index edeed01ede..d7ecda3b38 100644 --- a/.github/workflows/notify.yml +++ b/.github/workflows/notify.yml @@ -9,6 +9,7 @@ jobs: name: Send release to Discord if: github.event_name == 'release' runs-on: ubuntu-latest + timeout-minutes: 15 permissions: contents: read steps: @@ -25,6 +26,7 @@ jobs: name: Send release to Slack if: github.event_name == 'release' runs-on: ubuntu-latest + timeout-minutes: 15 permissions: {} steps: - name: Send Slack release notification