Skip to content
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

chore(deps): update error-prone monorepo to v2.35.1 #128

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 31, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.google.errorprone:error_prone_annotations (source) 2.27.1 -> 2.35.1 age adoption passing confidence
com.google.errorprone:error_prone_core (source) 2.27.1 -> 2.35.1 age adoption passing confidence

Release Notes

google/error-prone (com.google.errorprone:error_prone_annotations)

v2.35.1: Error Prone 2.35.1

Compare Source

Error Prone's dependency on protobuf has been downgraded to 3.25.5 for this release.

Version 3.25.5 of protobuf still fixes CVE-2024-7254. This release is provided for users who aren't ready to update to 4.x, see also #​4584 and #​4634. Future versions of Error Prone will upgrade back to protobuf 4.x.

Full changelog: google/error-prone@v2.35.0...v2.35.1

v2.35.0: Error Prone 2.35.0

Compare Source

Changes:

  • Fix handling of \s before the trailing delimiter in MisleadingEscapedSpace
  • TimeUnitMismatch improvements: handle binary trees, consider trees like fooSeconds * 1000 to have units of millis

New checks:

Full changelog: google/error-prone@v2.34.0...v2.35.0

v2.34.0: Error Prone 2.34.0

Compare Source

Changes:

  • Passing the javac flag --should-stop=ifError=FLOW is now required when running Error Prone (#​4595)
  • The MemberName check was renamed to IdentifierName

New checks:

Closed issues: #​4595, #​4598, #​4620

Full changelog: google/error-prone@v2.33.0...v2.34.0

v2.33.0: Error Prone 2.33.0

Compare Source

Similar to release 2.32.0, the minimum supported JDK version to run Error Prone is JDK 17 (#​3803). Using Error Prone to compile code that is deployed to earlier versions is still fully supported, but will require using JDK 17 or newer for compilation and setting --release or -source/-target/-bootclasspath.

Changes:

New checks:

Full changelog: google/error-prone@v2.32.0...v2.33.0

v2.32.0: Error Prone 2.32.0

Compare Source

The minimum support JDK version to run Error Prone is now JDK 17 (#​3803).

Using Error Prone to compile code that is deployed to earlier versions is still fully supported, but will requires using JDK 17 or newer for compilation and setting --release or -source/-target/-bootclasspath.

Full changelog: google/error-prone@v2.31.0...v2.32.0

v2.31.0: Error Prone 2.31.0

Compare Source

This is the last planned minor release of Error Prone that will support running on JDK 11, see #​3803. Using Error Prone to compile code that is deployed to earlier versions will continue to be fully supported, but will require using JDK 17 or newer for compilation and setting --release or -source/-target/-bootclasspath.

Changes:

New checks:

  • AutoValueBoxedValues: AutoValue instances should not usually contain boxed types that are not Nullable. We recommend removing the unnecessary boxing.

Full changelog: google/error-prone@v2.30.0...v2.31.0

v2.30.0: Error Prone 2.30.0

Compare Source

New checks:

Closed issues: #​632, #​4487

Full changelog: google/error-prone@v2.29.2...v2.30.0

v2.29.2: Error Prone 2.29.2

Compare Source

This release contains all of the changes in 2.29.0 and 2.29.1, plus:

Full Changelog: google/error-prone@v2.29.1...v2.29.2

v2.29.1: Error Prone 2.29.1

Compare Source

This release contains all of the changes in 2.29.0, plus:

Full Changelog: google/error-prone@v2.29.0...v2.29.1

v2.29.0: Error Prone 2.29.0

Compare Source

New checks:

Closed issues: #​4318, #​4429, #​4467

Full Changelog: google/error-prone@v2.28.0...v2.29.0

v2.28.0: Error Prone 2.28.0

Compare Source

Error Prone nows supports the latest JDK 23 EA builds (#​4412, #​4415).

Closed issues:

  • Improved errors for invalid check severities (#​4306).
  • Fix a crash with nested instanceof patterns (#​4349).
  • Fix a crash in JUnitIncompatibleType (#​4377).
  • In ObjectEqualsForPrimitives, don't suggest replacing equal with == for floating-point values (#​4392).

New checks:

Full Changelog: google/error-prone@v2.27.1...v2.28.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from joshuasing as a code owner May 31, 2024 20:02
@renovate renovate bot added the type: dependencies This involves updating, adding or removing a dependency label May 31, 2024
@renovate renovate bot requested a review from LooFifteen as a code owner May 31, 2024 20:02
@renovate renovate bot force-pushed the renovate/error-prone-monorepo branch from 823f3c7 to af0037a Compare July 16, 2024 22:53
@renovate renovate bot changed the title chore(deps): update error-prone monorepo to v2.28.0 chore(deps): update error-prone monorepo to v2.29.0 Jul 16, 2024
@renovate renovate bot changed the title chore(deps): update error-prone monorepo to v2.29.0 chore(deps): update error-prone monorepo to v2.29.1 Jul 17, 2024
@renovate renovate bot force-pushed the renovate/error-prone-monorepo branch 2 times, most recently from a9796e8 to 9c4c5fc Compare July 18, 2024 23:28
@renovate renovate bot changed the title chore(deps): update error-prone monorepo to v2.29.1 chore(deps): update error-prone monorepo to v2.29.2 Jul 18, 2024
@renovate renovate bot force-pushed the renovate/error-prone-monorepo branch from 9c4c5fc to a82da28 Compare August 10, 2024 19:55
@renovate renovate bot changed the title chore(deps): update error-prone monorepo to v2.29.2 chore(deps): update error-prone monorepo to v2.30.0 Aug 10, 2024
@renovate renovate bot force-pushed the renovate/error-prone-monorepo branch from a82da28 to 51eb05a Compare August 28, 2024 20:35
@renovate renovate bot changed the title chore(deps): update error-prone monorepo to v2.30.0 chore(deps): update error-prone monorepo to v2.31.0 Aug 28, 2024
@renovate renovate bot changed the title chore(deps): update error-prone monorepo to v2.31.0 chore(deps): update error-prone monorepo to v2.32.0 Sep 11, 2024
@renovate renovate bot force-pushed the renovate/error-prone-monorepo branch from 51eb05a to cd3f5f1 Compare September 11, 2024 18:56
@renovate renovate bot force-pushed the renovate/error-prone-monorepo branch from cd3f5f1 to 45ccc7f Compare October 1, 2024 00:36
@renovate renovate bot changed the title chore(deps): update error-prone monorepo to v2.32.0 chore(deps): update error-prone monorepo to v2.33.0 Oct 1, 2024
@renovate renovate bot changed the title chore(deps): update error-prone monorepo to v2.33.0 chore(deps): update error-prone monorepo Oct 18, 2024
@renovate renovate bot changed the title chore(deps): update error-prone monorepo chore(deps): update error-prone monorepo to v2.34.0 Oct 19, 2024
@renovate renovate bot force-pushed the renovate/error-prone-monorepo branch from 45ccc7f to 39f4665 Compare October 19, 2024 21:23
@renovate renovate bot changed the title chore(deps): update error-prone monorepo to v2.34.0 chore(deps): update error-prone monorepo to v2.35.1 Oct 25, 2024
@renovate renovate bot force-pushed the renovate/error-prone-monorepo branch from 39f4665 to f41f2aa Compare October 25, 2024 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: dependencies This involves updating, adding or removing a dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants