Excavator: Upgrades Baseline to the latest version #5965
Closed
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.
excavator is a bot for automating changes across repositories.
Changes produced by the roomba/latest-baseline-oss check.
Release Notes
4.54.0
void write(int)
, theyshould also override
void write(byte[], int, int)
, otherwise theperformance of the stream is likely to be slow.
See https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/io/FilterOutputStream.html#write(byte%5B%5D,int,int)
> Subclasses of FilterOutputStream should provide a more efficient implementation of this method.
Similar in concept to https://errorprone.info/bugpattern/InputStreamSlowMultibyteRead
4.55.0
inefficient FilterOuputStream implementations.
Subclasses of FilterOutputStream should provide a more efficient
implementation of
write(byte[], int, int)
to avoid slow writes.4.56.0
Concrete BugChecker implementations should be annotated
@AutoService(BugChecker.class)
for auto registration with error-prone.4.57.0
Avoid warning FilterOutputStreamSlowMultibyteWrite when intermediate
type overrides both single and multibyte write methods.
4.58.0
DangerousIdentityKey
now allowsClass
to be used as a map or set key.4.59.0
No documented user facing changes
4.60.0
Automated release, no documented user facing changes
4.61.0
Automated release, no documented user facing changes
4.62.0
Automated release, no documented user facing changes
4.63.0
4.64.0
compileRefaster
task for improved performance when it is not needed.4.65.0
4.66.0
com.palantir.baseline-error-prone.disable=false
Gradle property.4.67.0
Automated release, no documented user facing changes
4.68.0
StrictUnusedVariable
no longer flags parameters of default methods.4.69.0
4.70.0
Automated release, no documented user facing changes
4.71.0
Automated release, no documented user facing changes
4.72.0
Automated release, no documented user facing changes
4.73.0
4.74.0
No documented user facing changes
4.75.0
4.76.0
4.77.0
4.78.0
IllegalSafeLoggingArgument
check4.79.0
4.80.0
4.81.0
4.82.0
Automated release, no documented user facing changes
4.83.0
4.84.0
4.85.0
4.86.0
4.87.0
4.88.0
4.89.0
4.90.0
4.91.0
SerializationUtils
matcher4.92.0
4.93.0
4.94.0
4.95.0
4.96.0
4.97.0
4.98.0
4.99.0
4.100.0
4.101.0
Collection<@Safe String>
4.102.0
com.palantir.baseline-circleci
plugin so that compilation failures are once again parsed as XML and can be surfaced at the top of CircleCI builds.4.103.0
4.104.0
4.105.0
4.106.0
4.107.0
Use non-deprecated isSuppressed methods
4.108.0
4.109.0
ImmutablesReferenceEquality
check that checks for comparison of Immutables values using reference equality.4.110.0
4.111.0
4.112.0
SafeLoggingPropagation
error-prone check propages log-safety annotations from getters and superclasses/superinterfaces to the type level4.113.0
4.114.0
4.115.0
4.116.0
Automated release, no documented user facing changes
4.117.0
SafeLoggingPropagation
check and automated fixes:1. Method return statements are analyzed to determine safety of unmarked methods
2. Types are annotated based on the safety of their
toString
method, which is a reasonable heuristic for value types that may be logged.4.118.0
4.119.0
4.120.0
4.121.0
4.122.0
NarrowCalculation
4.123.0
4.124.0
4.125.0
To enable or disable this check, please contact the maintainers of Excavator.