Bump checker-qual from 3.28.0 to 3.34.0 in /fhir-parent

[dependabot]

Bumps checker-qual from 3.28.0 to 3.34.0.

Release notes

Sourced from checker-qual's releases.

Checker Framework 3.34.0

Version 3.34.0 (May 2, 2023)

User-visible changes:

The Checker Framework runs under JDK 20 -- that is, it runs on a version 20 JVM.

Explicit lambda parameters are defaulted the same as method parameters. For example, in (String s) -> {...} the type of s is @NonNull String.

Implementation details:

Renamings in AnnotatedTypeFactory:

• prepareCompilationUnitForWriting() => wpiPrepareCompilationUnitForWriting()
• prepareClassForWriting() => wpiPrepareClassForWriting()
• prepareMethodForWriting() => wpiPrepareMethodForWriting() and changed its signature by adding two formal parameters

Closed issues: #803, #5739, #5749, #5767, #5781, #5787.

Checker Framework 3.33.0

Version 3.33.0 (April 3, 2023)

User-visible changes:

The new command-line argument -AwarnRedundantAnnotations warns about redundant annotations. With this flag, a warning is issued if an explicitly written annotation on a type is the same as the default annotation. This feature does not warn about all redundant annotations, only some.

The Value Checker is cognizant of signedness annotations. This eliminates some false positive warnings.

Implementation details:

The Checker Framework no longer builds under JDK 8. However, you can still run the Checker Framework under JDK 8.

Closed issues:

#3785, #5436, #5708, #5717, #5720, #5721, #5727, #5732.

Checker Framework 3.32.0

Version 3.32.0 (March 2, 2023)

User-visible changes:

Fixed a bug in the Nullness Checker where a call to a side-effecting method did not make some formal parameters possibly-null. The Nullness Checker is likely to issue more warnings for your code. For ways to eliminate the new warnings, see https://checkerframework.org/manual/#type-refinement-side-effects .

If you supply the -AinvocationPreservesArgumentNullness command-line option, the Nullness Checker unsoundly assumes that arguments passed to non-null parameters in an invocation remain non-null after the invocation. This assumption is unsound in general, but it holds for most code.

Implementation details:

... (truncated)

Changelog

Sourced from checker-qual's changelog.

Version 3.34.0 (May 2, 2023)

User-visible changes:

The Checker Framework runs under JDK 20 -- that is, it runs on a version 20 JVM.

Explicit lambda parameters are defaulted the same as method parameters. For example, in (String s) -> {...} the type of s is @NonNull String.

Implementation details:

Renamings in AnnotatedTypeFactory:

• prepareCompilationUnitForWriting() => wpiPrepareCompilationUnitForWriting()
• prepareClassForWriting() => wpiPrepareClassForWriting()
• prepareMethodForWriting() => wpiPrepareMethodForWriting() and changed its signature by adding two formal parameters

Closed issues: #803, #5739, #5749, #5767, #5781, #5787.

Version 3.33.0 (April 3, 2023)

User-visible changes:

The new command-line argument -AwarnRedundantAnnotations warns about redundant annotations. With this flag, a warning is issued if an explicitly written annotation on a type is the same as the default annotation. This feature does not warn about all redundant annotations, only some.

The Value Checker is cognizant of signedness annotations. This eliminates some false positive warnings.

Implementation details:

The Checker Framework no longer builds under JDK 8. However, you can still run the Checker Framework under JDK 8.

Closed issues:

#3785, #5436, #5708, #5717, #5720, #5721, #5727, #5732.

Version 3.32.0 (March 2, 2023)

User-visible changes:

... (truncated)

Commits

• 57959be new release 3.34.0
• fd5713b Changed release date.
• ea0fca0 Define toStringVerbose() (#5830)
• afdd30a Avoid ConcurrentModificationException (#5828)
• a868d08 Fix link.
• b9d46b9 Revert updating shadown plugin.
• 3d9b765 Prep for release.
• 58cea05 Documentation improvements (#5822)
• 9c9238a Improve efficiency of getPreconditionAnnotations() and `getPostconditionAnn...
• 5218e20 Documentation for checkMemberReferenceReceivers() (#5819)
• Additional commits viewable in compare view

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)