Skip to content

Bump the gradle-deps group across 1 directory with 7 updates#3815

Merged
wadoon merged 2 commits intomainfrom
dependabot/gradle/gradle-deps-9990bcc2d9
May 2, 2026
Merged

Bump the gradle-deps group across 1 directory with 7 updates#3815
wadoon merged 2 commits intomainfrom
dependabot/gradle/gradle-deps-9990bcc2d9

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 2, 2026

Bumps the gradle-deps group with 7 updates in the / directory:

Package From To
io.github.eisop:checker-qual 3.49.3-eisop1 3.49.5-eisop1
io.github.eisop:checker-util 3.49.3-eisop1 3.49.5-eisop1
io.github.eisop:checker 3.49.3-eisop1 3.49.5-eisop1
org.junit:junit-bom 5.14.3 6.0.3
com.fasterxml.jackson.dataformat:jackson-dataformat-yaml 2.21.2 2.21.3
com.fasterxml.jackson.datatype:jackson-datatype-jsr310 2.21.2 2.21.3
org.sonarqube 7.2.3.7755 7.3.0.8198

Updates io.github.eisop:checker-qual from 3.49.3-eisop1 to 3.49.5-eisop1

Release notes

Sourced from io.github.eisop:checker-qual's releases.

Checker Framework 3.49.5-eisop1

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be

... (truncated)

Changelog

Sourced from io.github.eisop:checker-qual's changelog.

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be consistent when printing both bounds.

... (truncated)

Commits

Updates io.github.eisop:checker-util from 3.49.3-eisop1 to 3.49.5-eisop1

Release notes

Sourced from io.github.eisop:checker-util's releases.

Checker Framework 3.49.5-eisop1

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be

... (truncated)

Changelog

Sourced from io.github.eisop:checker-util's changelog.

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be consistent when printing both bounds.

... (truncated)

Commits

Updates io.github.eisop:checker from 3.49.3-eisop1 to 3.49.5-eisop1

Release notes

Sourced from io.github.eisop:checker's releases.

Checker Framework 3.49.5-eisop1

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be

... (truncated)

Changelog

Sourced from io.github.eisop:checker's changelog.

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be consistent when printing both bounds.

... (truncated)

Commits

Updates io.github.eisop:checker-util from 3.49.3-eisop1 to 3.49.5-eisop1

Release notes

Sourced from io.github.eisop:checker-util's releases.

Checker Framework 3.49.5-eisop1

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be

... (truncated)

Changelog

Sourced from io.github.eisop:checker-util's changelog.

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be consistent when printing both bounds.

... (truncated)

Commits

Updates io.github.eisop:checker from 3.49.3-eisop1 to 3.49.5-eisop1

Release notes

Sourced from io.github.eisop:checker's releases.

Checker Framework 3.49.5-eisop1

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be

... (truncated)

Changelog

Sourced from io.github.eisop:checker's changelog.

Version 3.49.5-eisop1 (April 26, 2026)

User-visible changes:

Considerable performance improvements. In a large project (over 4000 .java files) with complex qualifiers, compilation time was reduced from around 30 minutes to below 7 minutes. Running allNullnessTests went from around 3 minutes to 2.5 minutes and checkNullness went from around 5.25 to below 4 minutes.

The EISOP Checker Framework runs under JDK 26 and under JDK 27 b18 early access builds -- that is, it runs on version 26 and 27 JVMs.

The new command-line option -AonlyAnnotatedFor suppresses all type-checking errors and warnings outside the scope of a corresponding @AnnotatedFor annotation. Note that the @AnnotatedFor annotation must include the checker's name to enable warnings from that checker. For example, use @AnnotatedFor("nullness") for the Nullness Checker. This option unsoundly uses source defaults and suppresses the warnings outside the scope of a corresponding @AnnotatedFor annotation. Use -AuseConservativeDefaultsForUncheckedCode=source if you want conservative defaults for source code outside the scope of a corresponding @AnnotatedFor annotation.

The Nullness Checker now has more fine-grained prefix options to suppress warnings:

  • @SuppressWarnings("nullness") is used to suppress warnings from the Nullness, Initialization, and KeyFor Checkers.
  • @SuppressWarnings("nullnesskeyfor") is used to suppress warnings from the Nullness and KeyFor Checkers, warnings from the Initialization Checker are not suppressed. @SuppressWarnings("nullnessnoinit") has the same effect as @SuppressWarnings("nullnesskeyfor").
  • @SuppressWarnings("nullnessinitialization") is used to suppress warnings from the Nullness and Initialization Checkers, warnings from the KeyFor Checker are not suppressed.
  • @SuppressWarnings("nullnessonly") is used to suppress warnings from the Nullness Checker only, warnings from the Initialization and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("initialization") is used to suppress warnings from the Initialization Checker only, warnings from the Nullness and KeyFor Checkers are not suppressed.
  • @SuppressWarnings("keyfor") is used to suppress warnings from the KeyFor Checker only, warnings from the Nullness and Initialization Checkers are not suppressed.

The EISOP Checker Framework now uses NullType instead of Void to denote the bottom type in the Java type hierarchy. It is visible in error messages with type variable's or wildcard's lower bounds. The type of the null literal in the Nullness Checker is now displayed as @Nullable NullType instead of the earlier null (NullType). This change makes the EISOP Checker Framework more consistent with the Java language specification.

The format of error messages for type variables and wildcards has been improved to be consistent when printing both bounds.

... (truncated)

Commits

Updates org.junit:junit-bom from 5.14.3 to 6.0.3

Release notes

Sourced from org.junit:junit-bom's releases.

JUnit 6.0.3 = Platform 6.0.3 + Jupiter 6.0.3 + Vintage 6.0.3

See Release Notes.

Full Changelog: junit-team/junit-framework@r6.0.2...r6.0.3

JUnit 6.0.2 = Platform 6.0.2 + Jupiter 6.0.2 + Vintage 6.0.2

See Release Notes.

Full Changelog: junit-team/junit-framework@r6.0.1...r6.0.2

JUnit 6.0.1 = Platform 6.0.1 + Jupiter 6.0.1 + Vintage 6.0.1

See Release Notes.

Full Changelog: junit-team/junit-framework@r6.0.0...r6.0.1

JUnit 6.0.0 = Platform 6.0.0 + Jupiter 6.0.0 + Vintage 6.0.0

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r5.14.0...r6.0.0

JUnit 6.0.0-RC3 = Platform 6.0.0-RC3 + Jupiter 6.0.0-RC3 + Vintage 6.0.0-RC3

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.0.0-RC2...r6.0.0-RC3

JUnit 6.0.0-RC2 = Platform 6.0.0-RC2 + Jupiter 6.0.0-RC2 + Vintage 6.0.0-RC2

See Release Notes.

Full Changelog: junit-team/junit-framework@r6.0.0-RC1...r6.0.0-RC2

JUnit 6.0.0-RC1 = Platform 6.0.0-RC1 + Jupiter 6.0.0-RC1 + Vintage 6.0.0-RC1

... (truncated)

Commits
  • 36e3253 Release 6.0.3
  • 295561f Finalize 6.0.3 release notes
  • ea18076 Fix deadlock in NamespacedHierarchicalStore.computeIfAbsent() (#5348)
  • 869e232 Add 5.14.3 release notes
  • d4b34c4 Fix links to User Guide
  • 5c8fb0f Reliably support JRE.OTHER with @⁠EnabledOnJre and @⁠DisabledOnJre
  • febb13f Check out entire repo so switching to main branch works in last step
  • 71fba90 Install poppler-utils for pdfinfo
  • 740e9e0 Update API baseline
  • 2ba535f Use release branch of examples repo
  • Additional commits viewable in compare view

Updates com.fasterxml.jackson.dataformat:jackson-dataformat-yaml from 2.21.2 to 2.21.3

Commits
  • ccfcc95 [maven-release-plugin] prepare release jackson-dataformats-text-2.21.3
  • 5e81617 Prep for 2.21.3 release
  • 52ab617 Merge branch '2.20' into 2.21
  • 84f99f7 Merge branch '2.19' into 2.20
  • 4fe54cb Merge branch '2.18' into 2.19
  • f18c578 Post-release dep version bump
  • 8db1032 [maven-release-plugin] prepare for next development iteration
  • 7afb263 [maven-release-plugin] prepare release jackson-dataformats-text-2.18.7
  • ec50f24 Prep for 2.18.7 release
  • a8bedbd Post-release dep version bump
  • Additional commits viewable in compare view

Updates com.fasterxml.jackson.datatype:jackson-datatype-jsr310 from 2.21.2 to 2.21.3

Updates org.sonarqube from 7.2.3.7755 to 7.3.0.8198

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the gradle-deps group across 1 directory with 7 updates
5f7884b 
Bumps the gradle-deps group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [io.github.eisop:checker-qual](https://github.com/eisop/checker-framework) | `3.49.3-eisop1` | `3.49.5-eisop1` |
| [io.github.eisop:checker-util](https://github.com/eisop/checker-framework) | `3.49.3-eisop1` | `3.49.5-eisop1` |
| [io.github.eisop:checker](https://github.com/eisop/checker-framework) | `3.49.3-eisop1` | `3.49.5-eisop1` |
| [org.junit:junit-bom](https://github.com/junit-team/junit-framework) | `5.14.3` | `6.0.3` |
| [com.fasterxml.jackson.dataformat:jackson-dataformat-yaml](https://github.com/FasterXML/jackson-dataformats-text) | `2.21.2` | `2.21.3` |
| com.fasterxml.jackson.datatype:jackson-datatype-jsr310 | `2.21.2` | `2.21.3` |
| org.sonarqube | `7.2.3.7755` | `7.3.0.8198` |



Updates `io.github.eisop:checker-qual` from 3.49.3-eisop1 to 3.49.5-eisop1
- [Release notes](https://github.com/eisop/checker-framework/releases)
- [Changelog](https://github.com/eisop/checker-framework/blob/master/docs/CHANGELOG.md)
- [Commits](eisop/checker-framework@checker-framework-3.49.3-eisop1...checker-framework-3.49.5-eisop1)

Updates `io.github.eisop:checker-util` from 3.49.3-eisop1 to 3.49.5-eisop1
- [Release notes](https://github.com/eisop/checker-framework/releases)
- [Changelog](https://github.com/eisop/checker-framework/blob/master/docs/CHANGELOG.md)
- [Commits](eisop/checker-framework@checker-framework-3.49.3-eisop1...checker-framework-3.49.5-eisop1)

Updates `io.github.eisop:checker` from 3.49.3-eisop1 to 3.49.5-eisop1
- [Release notes](https://github.com/eisop/checker-framework/releases)
- [Changelog](https://github.com/eisop/checker-framework/blob/master/docs/CHANGELOG.md)
- [Commits](eisop/checker-framework@checker-framework-3.49.3-eisop1...checker-framework-3.49.5-eisop1)

Updates `io.github.eisop:checker-util` from 3.49.3-eisop1 to 3.49.5-eisop1
- [Release notes](https://github.com/eisop/checker-framework/releases)
- [Changelog](https://github.com/eisop/checker-framework/blob/master/docs/CHANGELOG.md)
- [Commits](eisop/checker-framework@checker-framework-3.49.3-eisop1...checker-framework-3.49.5-eisop1)

Updates `io.github.eisop:checker` from 3.49.3-eisop1 to 3.49.5-eisop1
- [Release notes](https://github.com/eisop/checker-framework/releases)
- [Changelog](https://github.com/eisop/checker-framework/blob/master/docs/CHANGELOG.md)
- [Commits](eisop/checker-framework@checker-framework-3.49.3-eisop1...checker-framework-3.49.5-eisop1)

Updates `org.junit:junit-bom` from 5.14.3 to 6.0.3
- [Release notes](https://github.com/junit-team/junit-framework/releases)
- [Commits](junit-team/junit-framework@r5.14.3...r6.0.3)

Updates `com.fasterxml.jackson.dataformat:jackson-dataformat-yaml` from 2.21.2 to 2.21.3
- [Commits](FasterXML/jackson-dataformats-text@jackson-dataformats-text-2.21.2...jackson-dataformats-text-2.21.3)

Updates `com.fasterxml.jackson.datatype:jackson-datatype-jsr310` from 2.21.2 to 2.21.3

Updates `org.sonarqube` from 7.2.3.7755 to 7.3.0.8198

---
updated-dependencies:
- dependency-name: io.github.eisop:checker-qual
  dependency-version: 3.49.5-eisop1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-deps
- dependency-name: io.github.eisop:checker-util
  dependency-version: 3.49.5-eisop1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-deps
- dependency-name: io.github.eisop:checker
  dependency-version: 3.49.5-eisop1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-deps
- dependency-name: io.github.eisop:checker-util
  dependency-version: 3.49.5-eisop1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-deps
- dependency-name: io.github.eisop:checker
  dependency-version: 3.49.5-eisop1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-deps
- dependency-name: org.junit:junit-bom
  dependency-version: 6.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: gradle-deps
- dependency-name: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml
  dependency-version: 2.21.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-deps
- dependency-name: com.fasterxml.jackson.datatype:jackson-datatype-jsr310
  dependency-version: 2.21.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-deps
- dependency-name: org.sonarqube
  dependency-version: 7.3.0.8198
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: gradle-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file Java Pull requests that update Java code labels May 2, 2026
@wadoon wadoon self-requested a review May 2, 2026 10:20
@wadoon wadoon added this pull request to the merge queue May 2, 2026
Merged via the queue into main with commit 17e9fe5 May 2, 2026
36 checks passed
@wadoon wadoon deleted the dependabot/gradle/gradle-deps-9990bcc2d9 branch May 2, 2026 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@wadoon wadoon wadoon approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file Java Pull requests that update Java code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@wadoon