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

Upgrade NullAway 0.10.2 -> 0.10.3 #324

Merged
merged 1 commit into from
Oct 30, 2022
Merged

Conversation

Picnic-Bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
com.uber.nullaway:nullaway patch 0.10.2 -> 0.10.3
com.uber.nullaway:nullaway compile patch 0.10.2 -> 0.10.3

Release Notes

uber/NullAway

v0.10.3

Compare Source

  • Report an error when casting @​Nullable expression to primitive type (#​663)
  • Fix an NPE in the optional emptiness handler (#​678)
  • Add support for boolean constraints (about nullness) in Contract annotations (#​669)
  • Support for specific libraries/APIs:
    • PreconditionsHandler reflects Guava Preconditions exception types (#​668)
    • Handle Guava Verify functions (#​682)
  • Dependency Updates:
    • checkerframework 3.26.0 (#​671)
  • Build / CI tooling for NullAway itself:
    • Build and test against Error Prone 2.15.0 (#​665)
    • Bump Error Prone and EP plugin to 2.16 (#​675)

  • If you want to rebase/retry this PR, click this checkbox.

@Picnic-Bot
Copy link
Contributor Author

Picnic-Bot commented Oct 30, 2022

Suggested commit message:

Upgrade NullAway 0.10.2 -> 0.10.3 (#324)

See:
- https://github.com/uber/NullAway/blob/master/CHANGELOG.md
- https://github.com/uber/NullAway/compare/v0.10.2...v0.10.3

@Stephan202 Stephan202 added this to the 0.5.0 milestone Oct 30, 2022
@rickie rickie changed the title Upgrade com.uber.nullaway:nullaway 0.10.2 -> 0.10.3 Upgrade NullAway 0.10.2 -> 0.10.3 Oct 30, 2022
@rickie rickie merged commit 16955a9 into master Oct 30, 2022
@rickie rickie deleted the renovate/version.nullaway branch October 30, 2022 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants