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

Update errorproneVersion to v2.36.0 - autoclosed #52

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 12, 2024

This PR contains the following updates:

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

Release Notes

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

v2.36.0: Error Prone 2.36.0

Changes:

  • Add new matcher interfaces to ErrorProneScanner for AST nodes introduced after Java 11 (e5fd194)
  • Fix compatibility with latest JDK 24 EA builds (google/error-prone@d67bc15)
  • Check that --should-stop=ifError=FLOW is set when using the -Xplugin integration (e71db1f)

New checks:

Closed issues: #​4633, #​4646

v2.35.1: Error Prone 2.35.1

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

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

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

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

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


Configuration

📅 Schedule: Branch creation - "* 0-4,22-23 * * 1-5,* * * * 0,6" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 enabled auto-merge (rebase) September 12, 2024 11:03
@renovate renovate bot force-pushed the renovate/errorproneversion branch 3 times, most recently from fec72f9 to c8b8f30 Compare September 30, 2024 22:43
@renovate renovate bot changed the title Update errorproneVersion to v2.32.0 Update errorproneVersion to v2.33.0 Sep 30, 2024
@renovate renovate bot force-pushed the renovate/errorproneversion branch 2 times, most recently from 7c27816 to 66a72c1 Compare October 5, 2024 10:11
@renovate renovate bot changed the title Update errorproneVersion to v2.33.0 Update errorproneVersion Oct 18, 2024
@renovate renovate bot force-pushed the renovate/errorproneversion branch from 66a72c1 to 1f56aab Compare October 18, 2024 23:41
@renovate renovate bot changed the title Update errorproneVersion Update errorproneVersion to v2.34.0 Oct 19, 2024
@renovate renovate bot force-pushed the renovate/errorproneversion branch 3 times, most recently from 0058de6 to b4562e5 Compare October 25, 2024 16:02
@renovate renovate bot changed the title Update errorproneVersion to v2.34.0 Update errorproneVersion Oct 25, 2024
@renovate renovate bot changed the title Update errorproneVersion Update errorproneVersion to v2.35.1 Oct 25, 2024
@renovate renovate bot force-pushed the renovate/errorproneversion branch from b4562e5 to a88e145 Compare November 12, 2024 11:06
@renovate renovate bot force-pushed the renovate/errorproneversion branch from a88e145 to ed2cd06 Compare November 19, 2024 12:05
@renovate renovate bot changed the title Update errorproneVersion to v2.35.1 Update errorproneVersion Nov 19, 2024
@renovate renovate bot changed the title Update errorproneVersion Update errorproneVersion to v2.36.0 Nov 19, 2024
@renovate renovate bot force-pushed the renovate/errorproneversion branch from ed2cd06 to 851d715 Compare November 21, 2024 11:58
@renovate renovate bot force-pushed the renovate/errorproneversion branch from 851d715 to 03704f1 Compare December 17, 2024 18:27
@renovate renovate bot force-pushed the renovate/errorproneversion branch from 03704f1 to c56fb96 Compare December 21, 2024 10:04
@renovate renovate bot changed the title Update errorproneVersion to v2.36.0 Update errorproneVersion to v2.36.0 - autoclosed Jan 8, 2025
@renovate renovate bot closed this Jan 8, 2025
auto-merge was automatically disabled January 8, 2025 00:18

Pull request was closed

@renovate renovate bot deleted the renovate/errorproneversion branch January 8, 2025 00:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants