Excavator: Upgrades Baseline to the latest version

[svc-excavator-bot]

excavator is a bot for automating changes across repositories.

Changes produced by the roomba/latest-baseline-oss check.

Release Notes

2.39.0

Type	Description	Link
Improvement	Baseline now depends on mockito-errorprone to get Mockito error-prone checks.	palantir/gradle-baseline#1085

2.40.0

Type	Description	Link
Improvement	Error prone CatchSpecificity and ThrowSpecificity to avoid unnecessarily broad throwables. Prefer more specific catch types than Exception and Throwable. When methods are updated to throw new checked exceptions they expect callers to handle failure types explicitly. Catching broad types defeats the type system. By catching the most specific types possible we leverage existing compiler functionality to detect unreachable code.	palantir/gradle-baseline#1074
Improvement	For repos that opted into palantir-java-format, the arguments of SafeArg.of (when it's a last argument) are no longer unexpectedly split onto the next line.	palantir/gradle-baseline#1075

2.40.1

Type	Description	Link
Fix	The PreferJavaTimeOverload error-prone check is turned off as it produces noisy false positives relating to custom AssertJ utilities.	palantir/gradle-baseline#1094

2.40.2

Type	Description	Link
Fix	Disable ThrowSpecificty and CatchSpecificity fixes by default	palantir/gradle-baseline#1098

2.41.0

No documented user facing changes

2.42.0

Type	Description	Link
Improvement	Improve NonComparableStreamSort to validate that stream types implement comparable, as opposed to validating that casting to comparable does not cause a compiler error. This commit reduces the severity to WARNING because it's possible that the check will flag code that happens to work today, but we strongly recommend against sorting streams of a type that is not directly comparable without a custom comparator because it is likely to break later due to lack of enforcement by the type system.	palantir/gradle-baseline#1070
Improvement	You may apply specific error-prone refactors including those which are not enabled by default by providing a comma delimited list of check names to the -PerrorProneApply option.	palantir/gradle-baseline#1109
Fix	Migrate baseline error-prone checks to use jdk13 compatible qualifiers	palantir/gradle-baseline#1110

2.43.0

Automated release, no documented user facing changes

2.44.0

Type	Description	Link
Improvement	Document ThrowSpecificity and CatchSpecificity edge cases	palantir/gradle-baseline#1118
Improvement	Using TaggedMetricRegistry.gauge is equivalent to map.putIfAbsent, and can result in subtle resource leaks. Prefer replacing existing gauge values using registerWithReplacement. This check doesn't apply unless a new enough version of Tritium is available on the compilation classpath.	palantir/gradle-baseline#1123
Migration	All assertj-related code-rewriting now lives in the https://github.com/palantir/assertj-automation repo.	palantir/gradle-baseline#1125

To enable or disable this check, please contact the maintainers of Excavator.