Split Release Notes in public Discord into chunks#5470
Merged
Conversation
bfops
approved these changes
Jul 1, 2026
bfops
left a comment
bfops
left a comment
Collaborator
There was a problem hiding this comment.
seems reasonabl to me! if this gets much more complicated we might consider putting into rust code, but seems fine for now
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
3 participants
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.
Description of Changes
Splits the Release Notes send to Discord during a release into chunks of 2000 characters
API and ABI breaking changes
None
Expected complexity level and risk
1 - Trivial
Testing