Telegram MarkdownV2 fenced-code regex over-matches inline backticks
Cluster 85381 · gateway. Data as of
Nothing open on GitHub. Fix merged in #131969 on 3 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #131969. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131969. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the Telegram MarkdownV2 parser's fenced-code regex incorrectly matches inline triple backticks, corrupting content and dropping formatting. The associated items propose anchoring the regex to prevent this over-matching while preserving mid-line and indented code fences.
Open issues0
Open PRs0
Fixes on record
-
#131969 fix(telegram): keep mid-line and indented code fences while anchoring inline backticks [risk 0.20]
files:
plugins/platforms/telegram/adapter.py,tests/conformance/vectors/telegram.json,tests/gateway/test_telegram_format.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#85398 fix(telegram): anchor fenced-code regex so inline triple backticks aren't mangled · merged via another change →
5f7b1e2,1897add,3480de0
Closed issues · 1
- Closed#85381[Bug]: Telegram MarkdownV2 fenced-code regex over-matches inline triple backticks, corrupts content and drops rich formatting
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #131969
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 3 Oct 2026