Skip to content

Bump error_prone_annotations from 2.7.1 to 2.13.1 #170

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 18, 2022

Bumps error_prone_annotations from 2.7.1 to 2.13.1.

Release notes

Sourced from error_prone_annotations's releases.

Error Prone 2.13.1

What's Changed

Full Changelog: google/error-prone@v2.13.0...v2.13.1

Error Prone 2.13.0

  • Handle all annotations with the simple name Generated in -XepDisableWarningsInGeneratedCode (#3094)
  • Reconcile BugChecker#isSuppressed with suppression handling in ErrorProneScanner (#3094)
  • Fix a bug in enclosingPackage (8fa64d48f3a1d8df852ed2546ba02b0e2b7585af)
  • Improve performance of fix application (186334bcc45d9c275037cdcce3eb509ae8b7ff50)
  • Implicitly treat @AutoBuilder setter methods as @CanIgnoreReturnValue.
  • Remove some obsolete checks (PublicConstructorForAbstractClass, HashCodeToString)

Release Diff: v2.12.1...v2.13.0.

Error Prone 2.12.1

Error Prone 2.12.0

New checks

Fixed issues: #58, #65, #1327, #1654, #2858, #2867, #2916, #2951, #2954, #3006, #3008

Full Changelog: google/error-prone@v2.11.0...v2.12.0

Error Prone 2.11.0

Error Prone now requires JDK 11 or newer (google/error-prone#2730).

New checks

... (truncated)

Commits

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 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)

Bumps [error_prone_annotations](https://github.com/google/error-prone) from 2.7.1 to 2.13.1.
- [Release notes](https://github.com/google/error-prone/releases)
- [Commits](google/error-prone@v2.7.1...v2.13.1)

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

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 18, 2022
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github May 30, 2022

Superseded by #176.

@dependabot dependabot bot closed this May 30, 2022
@dependabot dependabot bot deleted the dependabot/maven/com.google.errorprone-error_prone_annotations-2.13.1 branch May 30, 2022 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants