mirror of
https://github.com/Comfy-Org/Comfy-PR.git
synced 2026-11-04 23:37:33 +00:00
[PR #213] [MERGED] fix: post overflow changelog PR entries as thread replies instead of truncating #211
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/Comfy-PR#211
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Comfy-Org/Comfy-PR/pull/213
Author: @claude[bot]
Created: 9/12/2026
Status: ✅ Merged
Merged: 9/13/2026
Merged by: @christian-byrne
Base:
main← Head:fix/frontend-changelog-overflow-thread-replies📝 Commits (1)
710b67dfix: post overflow changelog PR entries as thread replies instead of truncating📊 Changes
6 files changed (+598 additions, -43 deletions)
View changed files
📝
app/tasks/gh-frontend-release-notification/index.spec.ts(+312 -26)📝
app/tasks/gh-frontend-release-notification/index.ts(+32 -17)➕
app/tasks/gh-frontend-release-notification/upsertChunkedSlackMessage.spec.ts(+99 -0)➕
app/tasks/gh-frontend-release-notification/upsertChunkedSlackMessage.ts(+76 -0)➕
lib/utils.spec.ts(+47 -0)📝
lib/utils.ts(+32 -0)📄 Description
Requested via Slack thread
Before: the
#frontendrelease-notification message (and the prerelease drafting message) middle-truncates the PR list once the release notes get long, dropping PR entries and inserting a literal...TRUNCATED...line — this just happened on the v1.55.5 stable release announcement.After: the message is split on whole-line boundaries (a PR entry is never split mid-line); the first chunk posts as the main message and any remaining chunks post as thread replies under it, so every PR entry is still visible, just spread across the thread instead of dropped.
Chunk size is 3500 characters — chosen for readability of a single Slack message, well under Slack's real 40,000-character message-text limit.
Also handles the message getting shorter on a later save (e.g. a release note edit) by deleting now-unused trailing thread replies.
Generated by Claude Code
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.