Cairn

Slack ordered list numbering broken by blank lines

NousResearch/hermes-agent · cluster 57076 · gateway

Data as of

Nothing open on GitHub. Fix merged in #57351. Check it covers your case.

The short answer

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

These issues and pull requests address a bug where blank lines between ordered list items cause Slack's rich_text_list rendering to reset numbering to '1.' for each item. Multiple fix attempts approach the problem of keeping blank-line-separated items within a single list block.

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.

  • #57351 fix(slack): keep blank-line-separated ordered lists in one rich_text_list (#57076)

    merged to main

    files: plugins/platforms/slack/block_kit.py, tests/gateway/test_slack_block_kit.py

4 PRs closed without merging

From the close comments: duplicate 3 · merged via another change 1

  • #57107 fix(slack): keep blank-line-separated ordered items in one rich_text_list · merged via another change → #57076, #57351
  • #57138 fix(slack): handle blank lines between ordered list items to preserve numbering (#57076) · duplicate → #57107, #57076
  • #57144 fix(slack): preserve blank-separated ordered lists · duplicate → #57107, #57076, #57138
  • #57204 fix(slack): blank lines no longer break ordered list numbering · duplicate → #57107, #57076, #57138, #57144
Closed issues · 1
  • Closed#57076Slack rich_blocks: blank-line-separated ordered lists render every item as "1."
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.33: 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

Subsystem
gateway
Merged PRs
#57351
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
2 Jul 2026

For your agent

The same facts, typed.

cluster/57076.json
cluster/57076.md