Repository navigation
Drop release notes repeated from earlier module releases in the changelog - #588
Merged
Merged
Conversation
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.
Before moderneinc/codegenomeproject#698, the CGP release job let GitHub pick where each release's notes started, and it often went back several releases. As a result, 441 module releases repeated pull requests already listed under earlier versions, and the changelog showed them twice.
Those release notes are now regenerated on GitHub from the previous release by version, and this reruns
./gradlew updateChangelogagainst them. It also picks up today's rewrite-recipe-bom 3.61.0, which the nightly job would have added.A few hand-made patch releases from before the CGP move still repeat about 20 pull requests; those are left as they are.