scoootscooob 2a381e6d7b fix(telegram): replyToMode 'first' now only applies reply-to to first chunk ...

The `replyToMessageIdForPayload` was computed once outside the chunk
and media loops, so all chunks received the same reply-to ID even when
replyToMode was set to "first". This replaces the static binding with
a lazy `resolveReplyTo()` function that checks `hasReplied` at each
send site, and updates `hasReplied` immediately after the first
successful send.

Fixes #31039

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-02 02:57:10 +00:00

..

delivery.resolve-media-retry.test.ts

fix(telegram): allowlist api.telegram.org in media SSRF policy

2026-02-24 04:20:30 +00:00

delivery.test.ts

fix(telegram): replyToMode 'first' now only applies reply-to to first chunk

2026-03-02 02:57:10 +00:00

delivery.ts

fix(telegram): replyToMode 'first' now only applies reply-to to first chunk

2026-03-02 02:57:10 +00:00

helpers.test.ts

fix(telegram): link forwarded messages with comments (#9720)

2026-02-22 21:23:56 +05:30

helpers.ts

refactor(security): enforce account-scoped pairing APIs

2026-02-26 21:57:52 +01:00

types.ts

fix(telegram): stream replies in-place without duplicate final sends

2026-02-15 20:32:51 +05:30