Repository navigation
Conversation
…to its full text Changelog lists written with `*` reached Slack as literal asterisks: only `-` items became bullets. A head message cut at 4,000 characters ended in `… (truncated)`; the new `cut-link` input names where the full text is, and the release flows pass the PR (started, cancelled) or the GitHub release (completed).
Contributor
Author
|
Folded into #20 as a separate commit, one PR to merge. |
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.
Two things seen on the app-backend 0.41.0 release head message. Changelog lists written with `*` (conventional-changelog style) reached Slack as literal asterisks: the converter only turned `-` items into bullets. And once the message was cut to Slack's 4,000 characters (#19) it ended in a bare `… (truncated)`, with nowhere to read the rest.
Changes
🤖 Generated with Claude Code