-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix formatting of baseline-class-uniqueness.lock files #1838
Conversation
When there was more than one configuration, a newline was missing between the previous configuration and the comment naming the next one.
Generate changelog in
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might require write-locks on upgrade, but we already do that.
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the roomba/latest-baseline-oss check. # Release Notes ## 4.2.0 | Type | Description | Link | | ---- | ----------- | ---- | | Improvement | Support the new SafeLogger API | palantir/gradle-baseline#1834 | | Improvement | Fix the formatting of `baseline-class-uniqueness.lock` files when more than one configuration is listed. A newline was missing. This may require running `./gradlew checkClassUniqueness --write-locks` to update the files. | palantir/gradle-baseline#1838 | ## 4.3.0 | Type | Description | Link | | ---- | ----------- | ---- | | Fix | Allow `PreferSafeLogger` to migrate logger uses which include level-checks | palantir/gradle-baseline#1842 | To enable or disable this check, please contact the maintainers of Excavator.
Fixes #1289
Before this PR
When the baseline class uniqueness check found issues in more than one configuration, a newline was missing between the previous configuration and the comment naming the next one. See: #1289
After this PR
==COMMIT_MSG==
Fix the formatting of
baseline-class-uniqueness.lock
files when more than one configuration is listed. A newline was missing. This may require running./gradlew checkClassUniqueness --write-locks
to update the files.==COMMIT_MSG==
Possible downsides?
Requires running the command to write the locks in repos that are affected. (By default only one configuration is set up for the uniqueness check, so the number of affected repos may be small.) I'm not sure if this would be considered a break.