docs(release): one changelog entry per tag; derive the customer summary - #1224
Merged
Merged
Conversation
…ry from the entries since the last Latest
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.
GitHub release notes list only what changed since the previous tag, pre-release or not, so the release list reads top to bottom without repeats. The customer-facing summary is derived when a release goes Latest: print every entry since the previous Latest with the
ghone-liner in section 3, then pare it down. Replaces the guidance to fold an unpromoted pre-release's changes into the next entry, which no release has actually followed.