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

deps: bump com.google.errorprone:error_prone_core from 2.24.1 to 2.27.0 #2800

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 29, 2024

Bumps com.google.errorprone:error_prone_core from 2.24.1 to 2.27.0.

Release notes

Sourced from com.google.errorprone:error_prone_core's releases.

Error Prone 2.27.0

New checks:

  • ClassInitializationDeadlock detects class initializers that reference subtypes of the current class, which can result in deadlocks.
  • MockitoDoSetup suggests using when/thenReturn over doReturn/when for additional type safety.
  • VoidUsed suggests using a literal null instead of referring to a Void-typed variable.

Modified checks:

Closed issues: #4291. #4308, #4343, #4320

Full Changelog: google/error-prone@v2.26.1...v2.27.0

Error Prone 2.26.1

This release contains all of the changes in 2.26.0, plus a bug fix to the module name of the annotations artifact com.google.errorprone.annotations (google/error-prone@9d99ee7)

Starting in 2.26.x, the 'annotations' artifact now includes a module-info.java for Java Platform Module System support, thanks to @​sgammon in #4311.


Compatibility note:

Now that the annotations artifact explicit declares a module instead of relying on Automatic-Module-Name, JDK 17 and newer perform stricter module encapsulation checks. Modularized libraries depending on Error Prone annotations 2.26.x and newer may see errors like:

error: package com.google.errorprone.annotations is not visible
import com.google.errorprone.annotations.CheckReturnValue;
                            ^
  (package com.google.errorprone.annotations is declared in module com.google.errorprone.annotations, but module ... does not read it)

The fix is to add requires static to the module declaration of modularized libraries that depend on Error Prone annotations:

 module your.module {
...
+  requires static com.google.errorprone.annotations;
 }

Full Changelog: google/error-prone@v2.26.0...v2.26.1

Error Prone 2.26.0

Warning: This release contains a bug, please use 2.26.1 or newer instead.

... (truncated)

Commits
  • ebe0a01 Release Error Prone 2.27.0
  • fd9b826 Remove a very literal change-detector test, and move the comment to the produ...
  • f289d9e VoidUsed: flag Void variables being used, where they can simply be repl...
  • 3ee6f41 Fix for a crash in RedundantSetterCall.
  • 92c106d Encourage when/thenReturn over doReturn/when.
  • 07c1a7c Stop mentioning @Var in[]
  • 9d66272 Correction to UseCorrectAssertInTests.
  • a6ab21a Fix a crash in JUnitIncompatibleType
  • 5a7b8d9 NearbyCallers: scan the body of expression lambdas.
  • 53d787c Don't suggest ImmutableSet if ImmutableList is unused.
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@lqiu96 lqiu96 added the automerge Summon MOG for automerging label Apr 30, 2024
@lqiu96
Copy link
Contributor

lqiu96 commented Apr 30, 2024

@dependabot recreate

Bumps [com.google.errorprone:error_prone_core](https://github.com/google/error-prone) from 2.24.1 to 2.27.0.
- [Release notes](https://github.com/google/error-prone/releases)
- [Commits](google/error-prone@v2.24.1...v2.27.0)

---
updated-dependencies:
- dependency-name: com.google.errorprone:error_prone_core
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/maven/3.x/com.google.errorprone-error_prone_core-2.27.0 branch from 0713815 to b2e0486 Compare April 30, 2024 15:39
Copy link

sonarcloud bot commented Apr 30, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link

Merge-on-green is not authorized to push to this branch. Visit https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions to give gcf-merge-on-green permission to push to this branch.

@lqiu96 lqiu96 merged commit 6651a73 into 3.x Apr 30, 2024
10 checks passed
@lqiu96 lqiu96 deleted the dependabot/maven/3.x/com.google.errorprone-error_prone_core-2.27.0 branch April 30, 2024 16:14
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Summon MOG for automerging label Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant