Nothing open on GitHub. Fix attempted, not merged.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug where upgrading to 0.21.0 left existing installs without the v2→v3 Telegram topic schema migration, silently breaking auto topic-rename. The accompanying fixes add self-healing migration logic triggered on read paths.
Open issues0
Open PRs0
3 PRs closed without merging
From the close comments: done elsewhere 2 · merged via another change 1
-
#103371 fix(state): self-heal pre-v3 telegram topic tables on read · merged via another change →
8b038f3,775fd44,cc59407 -
#103380 fix(telegram): heal v2->v3 schema gap on read paths before SELECT · done elsewhere →
8b038f3,#103363,#103371 -
#109228 fix(telegram): auto-migrate v2->v3 topic schema on first read (fixes #103363) · done elsewhere →
8b038f3,#103363,#103371
Closed issues · 1
- Closed#103363[Bug]: Telegram auto topic-rename silently broken on existing installs after 0.21.0 upgrade (schema v2→v3 migration never triggered)
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.50: 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
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging