mirror of
https://github.com/zulip/zulip.git
synced 2026-06-03 21:01:43 +08:00
ae4d65ad7f
The pre-deploy zulip_notify hook posts an informational "Starting deploy" message; combined with `set -e`, a failure to deliver it (e.g. the bot lacks posting permission on the target channel, or the server is unreachable) propagated out of the hook, and run_hooks.py treats any pre-deploy hook failure as fatal. A transient chat-notification problem could thus block an urgent deploy. Swallow delivery failures in the shared zulip_send helper after logging them, so neither the pre- nor post-deploy notification can abort a deploy. The post-deploy hooks were already best-effort; this brings the gating pre-deploy notification in line. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| kandra | ||
| zulip | ||
| deps.yaml | ||