Repository navigation
Conversation
chat.update rejects longer text with msg_too_long, so a long release changelog left the release head message stale. Cut at a line break, keep a short closing paragraph (the DB-migration flag) and log the Slack error.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| .catch(() => { | ||
| console.error('Failed to send Slack message.'); | ||
| .catch((error) => { | ||
| console.error(`Failed to send Slack message: ${error.message}`); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
chat.updaterejectstextover 4,000 characters withmsg_too_long. Release head updates (start, refresh, complete) send the full changelog, so a long release leaves the head message stale. The app-backend v0.41.0 refresh sent 5.7K characters and failed. Nobody saw it because the step iscontinue-on-errorand the script dropped the Slack error.truncateTextcuts the mrkdwn text at the last line break that fits, marks the cut and keeps a short closing paragraph, where release flags such as the DB-migration warning live. Messages under the limit go out unchanged.Checked on the v0.41.0 message: 5725 → 3992 characters, migration flag kept.
🤖 Generated with Claude Code