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

Bump checker-qual from 2.5.7 to 3.32.0 #26

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Mar 25, 2023

Bumps checker-qual from 2.5.7 to 3.32.0.

Release notes

Sourced from checker-qual's releases.

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:

Moved TreeUtils.isAutoGeneratedRecordMember(Element) to ElementUtils.

Renamed TreeUtils.instanceOfGetPattern() to TreeUtils.instanceOfTreeGetPattern().

Deprecated AnnotatedTypes#isExplicitlySuperBounded and AnnotatedTypes#isExplicitlyExtendsBounded because they are duplicates of #hasExplicitSuperBound and #hasExplicitExtendsBound.

Checker Framework 3.31.0

Version 3.31.0 (February 17, 2023)

User-visible changes:

Command-line argument -AshowPrefixInWarningMessages puts the checker name on the first line of each warning and error message.

Signedness Checker changes:

  • Cast expressions are not subject to type refinement. When a programmer writes a cast such as (@Signed int) 2, it is not refined to @SignednessGlb and cannot be used in an unsigned context.
  • When incompatible arguments are passed to @PolySigned formal parameters, the error is expressed in terms of @SignednessBottom rather than the greatest lower bound of the argument types.

Implementation details:

Moved AnnotationMirrorSet and AnnotationMirrorMap from org.checkerframework.framework.util to org.checkerframework.javacutil. Changed uses of Set<AnnotationMirror> to AnnotationMirrorSet including in APIs. Removed methods from AnnotationUtils that are no longer useful: createAnnotationMap, createAnnotationSet, createUnmodifiableAnnotationSet.

Closed issues: #5597.

Checker Framework 3.30.0

Version 3.30.0 (February 2, 2023)

Implementation details:

getQualifierKind() throws an exception rather than returning null.

Renamed gradle task copyJarsToDist to assembleForJavac.

... (truncated)

Changelog

Sourced from checker-qual's changelog.

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:

Moved TreeUtils.isAutoGeneratedRecordMember(Element) to ElementUtils.

Renamed TreeUtils.instanceOfGetPattern() to TreeUtils.instanceOfTreeGetPattern().

Deprecated AnnotatedTypes#isExplicitlySuperBounded and AnnotatedTypes#isExplicitlyExtendsBounded because they are duplicates of #hasExplicitSuperBound and #hasExplicitExtendsBound.

Version 3.31.0 (February 17, 2023)

User-visible changes:

Command-line argument -AshowPrefixInWarningMessages puts the checker name on the first line of each warning and error message.

Signedness Checker changes:

  • Cast expressions are not subject to type refinement. When a programmer writes a cast such as (@Signed int) 2, it is not refined to @SignednessGlb and cannot be used in an unsigned context.
  • When incompatible arguments are passed to @PolySigned formal parameters, the error is expressed in terms of @SignednessBottom rather than the greatest lower bound of the argument types.

Implementation details:

Moved AnnotationMirrorSet and AnnotationMirrorMap from org.checkerframework.framework.util to org.checkerframework.javacutil. Changed uses of Set<AnnotationMirror> to AnnotationMirrorSet including in APIs. Removed methods from AnnotationUtils that are no longer useful: createAnnotationMap, createAnnotationSet, createUnmodifiableAnnotationSet.

Closed issues:

... (truncated)

Commits
  • d5d0d28 new release 3.32.0
  • 8bee065 Declare explicit task dependencies.
  • 85f483a Prep for release.
  • 9eacbbc Don't run plume_lib_jdk8 because plume-lib doesn't build with JDK 8
  • c725eeb Add quotation marks
  • 42a4abf No-op change in hopes of re-enabling dependabot
  • a509138 Punctuation changes (#5689)
  • 9a0d70b add ability to exclude annotations from RemoveAnnotationsForInference on a pe...
  • 37f0261 Move TreeUtils.isAutoGeneratedRecordMember(Element) to ElementUtils (#5679)
  • e84e29e WPI: decision on whether to infer a type for a type variable should be made b...
  • 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 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 [checker-qual](https://github.com/typetools/checker-framework) from 2.5.7 to 3.32.0.
- [Release notes](https://github.com/typetools/checker-framework/releases)
- [Changelog](https://github.com/typetools/checker-framework/blob/master/docs/CHANGELOG.md)
- [Commits](typetools/checker-framework@checker-framework-2.5.7...checker-framework-3.32.0)

---
updated-dependencies:
- dependency-name: org.checkerframework:checker-qual
  dependency-type: direct:production
  update-type: version-update:semver-major
...

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

dependabot bot commented on behalf of github Apr 4, 2023

Superseded by #27.

@dependabot dependabot bot closed this Apr 4, 2023
@dependabot dependabot bot deleted the dependabot/maven/org.checkerframework-checker-qual-3.32.0 branch April 4, 2023 15:21
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