4 people 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 <[email protected]>
Co-authored-by: firat.sertgoz <[email protected]>

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

..

src

fix: prevent Telegram 409 Conflict on webhook re-registration (#447)

2026-03-01 16:36:26 -08:00

build.sh

Fixes build, adds missing sse event and correct command (#11)

2026-02-10 00:08:59 +00:00

Cargo.lock

Add Telegram Bot API channel as WASM module

2026-02-04 09:16:03 -08:00

Cargo.toml

fix: improve Telegram status delivery and reliability (#304)

2026-02-22 18:07:57 +00:00

telegram.capabilities.json

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

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