fix(release): preserve wrapped release notes#141
Merged
Conversation
Release highlights: - keep public release notes complete when Conventional Commit bullets wrap Release details: - **Release automation:** join indented bullet continuations before generating the curated GitHub release body - **Repository rules:** document the line-length-safe release note convention Verification: - pass pnpm validate after confirming the isolated retention test - prove wrapped detail and verification bullets remain complete in release notes
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
1 participant
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.
Summary: preserve indented Conventional Commit bullet continuations in curated GitHub release notes, document the 100-character wrapping convention, and cover it in the semantic-release smoke test. Verification: pnpm validate and commitlint passed.