Bump dependency com.uber.nullaway:nullaway to v0.14.2 - #1995
Conversation
☀️ Quality MonitorTests Coverage for New Code 〰️ Line Coverage: 100.00% — perfect 🎉 Coverage for Whole Project 〰️ Line Coverage: 92.03% Style Bugs API Problems 🚫 Revapi: No warnings Vulnerabilities 🛡️ OWASP Dependency Check: No vulnerabilities Software Metrics 🌀 Cyclomatic Complexity: 397 (total) 📌 Reference ResultsDelta reports computed against the reference results of 7c7d7bc in workflow run 35969796548. 🚦 Quality GatesOverall Status: ✅ SUCCESS✅ Passed Gates
Created by Quality Monitor v4.15.0 (#82d77af). More details are shown in the GitHub Checks Result. |
This PR contains the following updates:
0.14.1→0.14.2Release Notes
uber/NullAway (com.uber.nullaway:nullaway)
v0.14.2Compare Source
This release adds
JSpecifyUnrecognizedAnnotationLocation, an opt-in check that reportsnullness annotations in locations JSpecify does not recognize. See further documentation
on the wiki: https://github.com/uber/NullAway/wiki/JSpecify-Support#jspecifyunrecognizedannotationlocation-checker
Not packaged in the release, but we have also added a script to remove unnecessary NullAway
suppressions to the repo: https://github.com/uber/NullAway/tree/master/scripts/nullaway-suppression-remover
We expect this to be a useful script to run after NullAway updates, to check if
NullAway improvements make some suppressions unnecessary.
Also of note, NullAway now more precisely detects whether the JDK used for the build properly
supports reading type use annotations from bytecode, particularly important for JSpecify
mode. This may lead NullAway to crash on certain build configurations that were
unsupported before but we were not detecting precisely.
Beyond the above, this release includes further fixes for JSpecify mode and
JSpecifyExperimental, especially for wildcard bounds and multi-dimensional arrays,
along with other bug fixes.
Finally, we have re-enabled pushing snapshot builds to the Sonatype snapshots repository,
which should ease testing NullAway versions between releases.
JSpecifyUnrecognizedAnnotationLocation, an opt-in check that reports nullness annotations in locations JSpecify does not recognize by @vlsi (#1787)RequireExplicitNullMarkingdiagnostics repeating the check name, so a report no longer begins with[RequireExplicitNullMarking] [RequireExplicitNullMarking]by @vlsi (#1815)nullin comparisons by @Beluomini (#1750)Assisted-by:commit trailer for AI-assisted work by @vlsi (#1811)Assisted-by:text to the PR template and CONTRIBUTING.md (#1838)getRawTypeAttributesinGenericsChecks(#1844)addSourceFilecalls in AndroidTest by @jabrailkhalil (#1839)Configuration
📅 Schedule: (UTC)
🚦 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.