-
Notifications
You must be signed in to change notification settings - Fork 36
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
Excavator: Upgrades Baseline to the latest version #593
Merged
Conversation
This file contains 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
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
4 times, most recently
from
November 30, 2021 17:49
a1e8f2a
to
97a70c2
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
3 times, most recently
from
December 11, 2021 20:33
85ecbd4
to
82625c9
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
December 18, 2021 21:50
82625c9
to
7c2e067
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
December 25, 2021 23:11
7c2e067
to
d287065
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
4 times, most recently
from
January 8, 2022 01:28
ff5d7b7
to
02eab8f
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
4 times, most recently
from
January 17, 2022 15:51
4c8e98d
to
03899c3
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
3 times, most recently
from
January 25, 2022 16:48
f672b59
to
fbc9e7a
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
2 times, most recently
from
February 1, 2022 08:38
97b37c1
to
71253a6
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
February 7, 2022 21:46
71253a6
to
2ca14b4
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
February 15, 2022 03:26
2ca14b4
to
228de46
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
4 times, most recently
from
February 24, 2022 01:07
8edcb30
to
2ca1e44
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
3 times, most recently
from
May 16, 2022 22:08
644cb1a
to
ec48392
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
May 23, 2022 22:25
ec48392
to
737db30
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
2 times, most recently
from
June 6, 2022 21:40
5c9b092
to
4aaae77
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
3 times, most recently
from
June 8, 2022 20:33
8f99f03
to
161b585
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
2 times, most recently
from
June 15, 2022 18:29
99f4177
to
7c2128b
Compare
svc-excavator-bot
changed the title
Excavator: Upgrades Baseline to the latest version
Excavator: Upgrades Baseline to the latest version
Jun 22, 2022
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
June 22, 2022 19:12
7c2128b
to
4392957
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
3 times, most recently
from
July 6, 2022 00:17
86d07cc
to
0f7da31
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
July 13, 2022 05:26
0f7da31
to
f479132
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
2 times, most recently
from
July 26, 2022 11:48
230f361
to
4f0c84c
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
3 times, most recently
from
August 3, 2022 01:18
aabd728
to
bb195af
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
August 8, 2022 14:03
bb195af
to
93ac836
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
September 30, 2022 10:11
93ac836
to
7f3109c
Compare
svc-excavator-bot
force-pushed
the
roomba/latest-baseline-oss
branch
from
September 30, 2022 13:53
7f3109c
to
e555cc5
Compare
schlosna
approved these changes
Oct 3, 2022
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.
excavator is a bot for automating changes across repositories.
Changes produced by the roomba/latest-baseline-oss check.
Release Notes
4.43.0
4.44.0
4.45.0
Automated release, no documented user facing changes
4.46.0
Automated release, no documented user facing changes
4.47.0
4.48.0
4.49.0
4.50.0
4.51.0
4.52.0
4.53.0
No documented user facing changes
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
4.126.0
4.127.0
4.128.0
4.129.0
Automated release, no documented user facing changes
4.130.0
StackOverflowError
s do not occur4.131.0
4.132.0
4.133.0
4.134.0
4.135.0
4.136.0
LazilyConfiguredMapping
that was extracted out to gradle-utils.4.137.0
4.138.0
4.139.0
4.140.0
AvoidNewHashMapInt
to warn on uses ofnew HashSet(int)
.4.141.0
4.142.0
4.143.0
4.144.0
4.145.0
4.146.0
Automated release, no documented user facing changes
4.147.0
Automated release, no documented user facing changes
4.148.0
4.149.0
com.palantir.baseline-java-versions
plugin can now setjavaVersions { distributionTarget = '17_PREVIEW' }
to opt-in to Java's--enable-preview
flag at compile time.4.150.0
BaselineModuleJvmArgs
plugin to once again work as intended in multi-project builds4.151.0
--enable-preview
is used4.152.0
Related to google/error-prone issues 632
Adds a
DefaultLocale
check that replaces uses ofString.toLowerCase()
andString.toUpperCase()
with the overloads that take aLocale
, usingLocale.ROOT
.4.153.0
4.154.0
4.155.0
Automated release, no documented user facing changes
4.156.0
4.157.0
junit-reports
plugin.4.158.0
checkUnusedDependencies
tasks added bybaseline-exact-dependencies
compatible with Gradle's configure-on-demand feature.4.159.0
There is a certain class of very problematic cases whereby if you have
a method such as the following:
<br>myJerseyResource.register(/* this is of type Object */ object);<br>
Then if you supply a resource which includes any
javax.ws.rs
annotations on it, then those will not be registered if your Jersey
version is 3.x or later (and you'll only find this out at runtime).
The opposite is also true if you try to supply resources annotated
with
jakarta.ws.rs
to Jersey 2.x.To address this, this commit attempts to add an errorprone check
which lets implementors add an annotation
@ForbidJavax
to methodswhich have been knowingly migrated to Jakarta EE9 and cannot
accept legacy javax types.
4.160.0
4.161.0
4.162.0
+ support setting preview on a project-by-project basis.
+ Fixes #2340
+ fails more elegantly if javaVersions is set on not-the-root.
4.163.0
4.164.0
CyclomaticComplexity
check is now configured withswitchBlockAsSingleDecisionPoint
.4.165.0
com.palantir.baseline-null-away
which registers theNullAway
check atWARNING
. Projects which fail on warnings will require this to pass pre-merge.4.166.0
Automated release, no documented user facing changes
4.167.0
Automated release, no documented user facing changes
4.168.0
4.169.0
4.170.0
4.171.0
com.palantir.baseline-null-away
no longer enables theCheckOptionalEmptiness
checker by default.4.172.0
Automated release, no documented user facing changes
4.173.0
4.174.0
4.175.0
4.176.0
4.177.0
4.178.0
4.179.0
build()
with the more descriptivebuildOrThrow()
, howeverbuildKeepingLast()
may be the original intent in some cases.To enable or disable this check, please contact the maintainers of Excavator.