Cairn
NousResearch/hermes-agent

Legacy Telegram topic schema handling during profile ops

Cluster 113757. Data as of

Nothing open on GitHub. Fix merged in #114831 on 18 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #114831. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #114831. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests concern failures in profile deletion, renaming, and purging when legacy Telegram topic database tables are present. The work involves detecting and migrating or accommodating those legacy schemas before profile cleanup operations proceed.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #114831 fix(state): profile delete/rename no longer fail on legacy Telegram topic tables (#113757, salvage #113767)

    merged to main

    files: contributors/emails/[redacted:email], hermes_state_gateway.py, tests/hermes_state/test_purge_profile_state.py, tests/hermes_state/test_rekey_profile_state.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #113765 fix(state): migrate legacy topic tables before profile purge and rekey · superseded by another PR → 4838119, #114831, #113757, #113767
  • #113767 fix: support legacy Telegram topic schemas during profile cleanup · merged via another change → 4838119, #114831, #113757, #113767
Closed issues · 1
  • Closed#113757[Bug]: profile purge/delete and rename fail on supported legacy Telegram topic schemas
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.00 means 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 Lab

At a glance

Merged PRs
#114831
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/113757.json
cluster/113757.md