smkrv b9446712e9 fix(telegram): add missing webhook section to capabilities.json (#381) ...

The Telegram channel capabilities file was missing the `webhook`
block inside `capabilities.channel`, causing the router to fall back
to the default `X-Webhook-Secret` header instead of the Telegram-
specific `X-Telegram-Bot-Api-Secret-Token`.

When a webhook secret is configured (via `telegram_webhook_secret`),
incoming updates are rejected with 401 because Telegram sends the
token in `X-Telegram-Bot-Api-Secret-Token` but the router looks for
`X-Webhook-Secret`.

The existing test in `schema.rs` already expects the correct header
name, confirming this is an oversight in the shipped capabilities
file.

Co-authored-by: SMKRV <SMKRV@users.noreply.github.com>
Co-authored-by: firat.sertgoz <f@nuff.tech>

2026-03-04 14:40:28 +00:00

..

discord

fix: add missing build.sh for Discord and WhatsApp channels (#429)

2026-03-01 08:41:20 +00:00

slack

feat: add pairing/permission system to all WASM channels and fix extension registry (#286)

2026-02-20 23:21:32 -08:00

telegram

fix(telegram): add missing webhook section to capabilities.json (#381)

2026-03-04 14:40:28 +00:00

whatsapp

fix: add missing build.sh for Discord and WhatsApp channels (#429)

2026-03-01 08:41:20 +00:00