Bump the migrator group in /migrator with 5 updates

[dependabot]

Bumps the migrator group in /migrator with 5 updates:

Package	From	To
com.google.truth:truth	1.0.1	1.4.5
info.picocli:picocli	4.7.4	4.7.7
com.google.truth.extensions:truth-java8-extension	1.0.1	1.4.5
com.google.auto.value:auto-value	1.10.2	1.11.1
com.google.auto.value:auto-value-annotations	1.10.2	1.11.1

Updates com.google.truth:truth from 1.0.1 to 1.4.5

Release notes

Sourced from com.google.truth:truth's releases.

1.4.5

• Changed assertions like assertThat(nullMap).isEmpty() to fail with a useful failure message instead of throwing NullPointerException (and similarly for other "bogus" values, such as negative sizes). (da5d6e96f)
• Made Kotlin's isInstanceOf(Int::class.java) (and Java's isInstanceOf(int.class)) a valid way to check for Int/Integer instances. (974ef195b)
• Improved isWithin to pretty-print numbers in its failure messages. (de785536d, 07318c23e)
• Improved some assertions that print class names to print simpler names (e.g., Integer instead of java.lang.Integer). (0ba72d60fdb384aa97da03e2403a6757f63bf129)
• Changed ExpectFailure to never generate "value of" lines based on bytecode. This slightly simplifies writing new tests with ExpectFailure and prevents future behavior changes in some ExpectFailure tests that already exist. However, it may also require changes to other existing ExpectFailure tests to remove or change any assertions about the "value of" line. (3caa0e845)
• Our Android minSdkVersion is now 23 (Marshmallow). This follows the minimum of Google's foundational Android libraries, and we expect it to have no practical impact on users. (c85c75cf4)
• Changed our GWT/J2CL artifact to omit usages of @NullMarked. This was making all our types non-null in those environments, since we don't yet use @Nullable in the GWT/J2CL artifact. (6392d37e7)

v1.4.4

• Annotated the rest of the main package for nullness, and moved the @NullMarked annotation from individual classes up to the package to avoid a warning under --release 8. (e107aeadc)
• Improved the failure message for matches to conditionally suggest using containsMatch. (7e9fc7aec)

1.4.3

Known Issue for at least some builds targeting Java 8, fixed in 1.4.4: "unknown enum constant ElementType.MODULE": google/truth#1320. As far as we know, this is only a warning, so it should cause practical problems only if you use -Werror or you perform reflection on @NullMarked under a Java 8 runtime.

• Added more nullness information to our APIs (in the form of JSpecify annotations). This could lead to additional warnings (or even errors) for users of Kotlin and other nullness checkers. Please report any problems. (ee680cbaf)
• Deprecated Subject.Factory methods for Java 8 types. We won't remove them, but you can simplify your code by migrating off them: Just replace assertAbout(foos()).that(foo) with assertThat(foo) (or about(foos()).that(foo) with that(foo)). (59e7a5065)

1.4.2

This release is the final step of copying all our methods from Truth8 to Truth. If you have not already migrated your usages from Truth8 to Truth, you may see build errors:

OptionalSubjectTest.java:39: error: reference to assertThat is ambiguous
    assertThat(Optional.of("foo")).isPresent();
    ^
  both method assertThat(@org.checkerframework.checker.nullness.qual.Nullable Optional<?>) in Truth8 and method assertThat(@org.checkerframework.checker.nullness.qual.Nullable Optional<?>) in Truth match

In most cases, you can migrate your whole project mechanically: git grep -l Truth8 | xargs perl -pi -e 's/\bTruth8\b/Truth/g;'. (You can make that change before upgrading to Truth 1.4.2 or as part of the same commit.)

If you instead need to migrate your project incrementally (for example, because it is very large), you may want to upgrade your version of Truth incrementally, too, following our instructions for 1.3.0 and 1.4.0.

For help

Please feel welcome to open an issue to report problems or request help.

Changelog

• Removed temporary type parameters from Truth.assertThat(Stream) and Truth.assertThat(Optional). This can create build errors, which you can fix by replacing all your references to Truth8 with references to Truth. (45782bd0e)

1.4.1

This release deprecates Truth8.

All its methods have become available on the main Truth class. In most cases, you can migrate your whole project mechanically: git grep -l Truth8 | xargs perl -pi -e 's/\bTruth8\b/Truth/g;'

While we do not plan to delete Truth8, we recommend migrating off it, at least if you static import assertThat: If you do not migrate, such static imports become ambiguous in Truth 1.4.2, breaking your build.

1.4.0

... (truncated)

Commits

• See full diff in compare view

Updates info.picocli:picocli from 4.7.4 to 4.7.7

Release notes

Sourced from info.picocli:picocli's releases.

Picocli 4.7.7

Picocli 4.7.7

The picocli community is pleased to announce picocli 4.7.7.

This release includes bugfixes and enhancements.

Many thanks to the picocli community for raising these issues and providing the pull requests to address them!

This is the eighty-sixth public release. Picocli follows semantic versioning. Artifacts in this release are signed by Remko Popma (6601 E5C0 8DCC BB96).

Table of Contents

• New and noteworthy
• Fixed issues
• Deprecations
• Potential breaking changes

New and Noteworthy

This release fixes a problem that was introduced in the previous release (4.7.6), where using an ArgGroup in a Mixin would result in options being added twice, or DuplicateOptionAnnotationsException.

The built-in picocli.CommandLine.HelpCommand subcommand now implements Callable<Integer> and returns the exit code of the subcommand's exitCodeOnUsageHelp value for the subcommand whose help was requested.

From this release, if a command implements both Callable and Runnable, then the default execution strategy will invoke the call method instead of the run method.

Fixed issues

• #2353 Enhancement: picocli.shell.jline3.PicocliCommands::invoke now returns ParseResult instead of null. Thanks to Paul for raising this.
• #2336 Enhancement: Avoid syntax error in auto-completion script for invalid option names and paramLabel values starting with a digit. Thanks to Ruud Senden and Tobias Knerr for raising this.
• #2281 Enhancement: Variable interpolation should work for ArgGroup.heading attribute. Thanks to Marc Philipp for raising this.
• #2355 Bugfix: The built-in help subcommand should return the exit code of the subcommand's exitCodeOnUsageHelp value for the subcommand whose help was requested. Thanks to marco-brandizi for raising this.
• #2335 Bugfix: Module info missing in all jars except the main picocli jar file. Thanks to Oliver B. Fischer for raising this.
• #2331 Bugfix: AutoComplete with jline3 was showing hidden commands. Thanks to clebertsuconic for raising this.
• #2291 Bugfix: NullPointerException when using PropertiesDefaultProvider. Thanks to JessHolle for raising this.
• #2344 Bugfix: negatable=true option in an ArgGroup should not add negated option twice. Thanks to Robin Fritz for raising this.
• #2309 Bugfix: Duplicate help output for ArgGroup from a Mixin. Thanks to s-falke for raising this. Thanks to Simon Gamma for providing a pull request for this.
• #2341 Bugfix: Options get doubled in non validating ArgGroup when used in Mixin. Thanks to Selene Feigl for raising this.
• #2349 Bugfix: Incorrect results when using ArgGroup + defaultValue + split + List/Set. Thanks to Mithun Josalyn Gonsalvez for raising this.
• #2292 Bugfix: DuplicateOptionAnnotationsException on using negatable option in ArgGroup. Thanks to Bhavik Patel for raising this.
• #2380 Bugfix: boolean with arity=0 and defaultValue=false behaved unexpectedly. Thanks to Leonard Brünings for raising this.
• #2290 DOC: User guide, CDI 2.0 (JSR 365) section: fix example and add warning about dynamic proxies. Thanks to Mert Zeybekler for the pull request.
• #2347 DOC: Fix line-endings in generated asciidoc HTML. Thanks to Fridrich Štrba for the pull request.
• #2367 DOC: Fix broken link. Thanks to yeoleobun for the pull request.
• #2370 DOC: Add at least a link to how to use the CodeGen APT under Bazel. Thanks to Michael Vorburger for the pull request.
• #2302 DEP: Bump actions/checkout from 4.1.4 to 4.1.7
• #2391 DEP: Bump actions/checkout from 4.1.7 to 4.2.2
• #2388 DEP: Bump actions/setup-java from 4.2.1 to 4.7.1

... (truncated)

Changelog

Sourced from info.picocli:picocli's changelog.

Picocli 4.7.7

The picocli community is pleased to announce picocli 4.7.7.

This release includes bugfixes and enhancements.

Many thanks to the picocli community for raising these issues and providing the pull requests to address them!

This is the eighty-sixth public release. Picocli follows semantic versioning. Artifacts in this release are signed by Remko Popma (6601 E5C0 8DCC BB96).

Table of Contents

• New and noteworthy
• Fixed issues
• Deprecations
• Potential breaking changes

New and Noteworthy

This release fixes a problem that was introduced in the previous release (4.7.6), where using an ArgGroup in a Mixin would result in options being added twice, or DuplicateOptionAnnotationsException.

The built-in picocli.CommandLine.HelpCommand subcommand now implements Callable<Integer> and returns the exit code of the subcommand's exitCodeOnUsageHelp value for the subcommand whose help was requested.

From this release, if a command implements both Callable and Runnable, then the default execution strategy will invoke the call method instead of the run method.

Fixed issues

• #2353 Enhancement: picocli.shell.jline3.PicocliCommands::invoke now returns ParseResult instead of null. Thanks to Paul for raising this.
• #2336 Enhancement: Avoid syntax error in auto-completion script for invalid option names and paramLabel values starting with a digit. Thanks to Ruud Senden and Tobias Knerr for raising this.
• #2281 Enhancement: Variable interpolation should work for ArgGroup.heading attribute. Thanks to Marc Philipp for raising this.
• #2355 Bugfix: The built-in help subcommand should return the exit code of the subcommand's exitCodeOnUsageHelp value for the subcommand whose help was requested. Thanks to marco-brandizi for raising this.
• #2335 Bugfix: Module info missing in all jars except the main picocli jar file. Thanks to Oliver B. Fischer for raising this.
• #2331 Bugfix: AutoComplete with jline3 was showing hidden commands. Thanks to clebertsuconic for raising this.
• #2291 Bugfix: NullPointerException when using PropertiesDefaultProvider. Thanks to JessHolle for raising this.
• #2344 Bugfix: negatable=true option in an ArgGroup should not add negated option twice. Thanks to Robin Fritz for raising this.
• #2309 Bugfix: Duplicate help output for ArgGroup from a Mixin. Thanks to s-falke for raising this. Thanks to Simon Gamma for providing a pull request for this.
• #2341 Bugfix: Options get doubled in non validating ArgGroup when used in Mixin. Thanks to Selene Feigl for raising this.
• #2349 Bugfix: Incorrect results when using ArgGroup + defaultValue + split + List/Set. Thanks to Mithun Josalyn Gonsalvez for raising this.
• #2292 Bugfix: DuplicateOptionAnnotationsException on using negatable option in ArgGroup. Thanks to Bhavik Patel for raising this.
• #2380 Bugfix: boolean with arity=0 and defaultValue=false behaved unexpectedly. Thanks to Leonard Brünings for raising this.
• #2290 DOC: User guide, CDI 2.0 (JSR 365) section: fix example and add warning about dynamic proxies. Thanks to Mert Zeybekler for the pull request.
• #2347 DOC: Fix line-endings in generated asciidoc HTML. Thanks to Fridrich Štrba for the pull request.
• #2367 DOC: Fix broken link. Thanks to yeoleobun for the pull request.
• #2370 DOC: Add at least a link to how to use the CodeGen APT under Bazel. Thanks to Michael Vorburger for the pull request.
• #2302 DEP: Bump actions/checkout from 4.1.4 to 4.1.7
• #2391 DEP: Bump actions/checkout from 4.1.7 to 4.2.2
• #2388 DEP: Bump actions/setup-java from 4.2.1 to 4.7.1
• #2390 DEP: Bump actions/upload-artifact from 4.3.3 to 4.6.2

... (truncated)

Commits

• 5fcd441 BUILD: use JReleaser for publishing to Maven Central
• 7f14deb Release picocli version 4.7.7
• feae94e Bump net.ltgt.gradle:gradle-errorprone-plugin from 4.1.0 to 4.2.0
• cacb0e7 Bump org.jetbrains.kotlin:kotlin-script-runtime from 2.0.0 to 2.1.20
• 44de141 Bump org.jetbrains.kotlin:kotlin-gradle-plugin from 2.0.0 to 2.1.20
• 8440061 Bump jakarta.validation:jakarta.validation-api from 3.1.0 to 3.1.1
• f5b9590 Bump org.jline:jline from 3.26.1 to 3.29.0
• 9d94fa6 DOC update RELEASE-NOTES for dependency updates
• 5bfb673 Revert "Bump org.hamcrest:hamcrest-core from 2.2 to 3.0"
• 1afa344 Bump org.hibernate.validator:hibernate-validator
• Additional commits viewable in compare view

Updates com.google.truth.extensions:truth-java8-extension from 1.0.1 to 1.4.5

Updates com.google.auto.value:auto-value from 1.10.2 to 1.11.1

Release notes

Sourced from com.google.auto.value:auto-value's releases.

AutoValue 1.11.1

• Fixed a crash with @AutoValue.CopyAnnotations(exclude=Missing.class), where Missing is a class that does not exist.
• Type-use annotations such as @Nullable are now better preserved in generated builder setter method parameters. Previously they could be lost in some circumstances, for example with @Nullable T.
• An issue with @Nullable type-use annotations in AutoBuilder has been fixed.
• Report a diagnostic for setters with boxed primitive types for primitive properties.
• A bug with AutoBuilder and Kotlin data classes has been fixed. If there was a mix of required and optional parameters in a data class with a large number of properties, sometimes the generated code would not compile.

AutoValue 1.11.0

What's Changed

• AutoValue (including AutoBuilder) no longer bundles the Kotlin metadata API. This may require adding an explicit dependency on org.jetbrains.kotlinx:kotlinx-metadata-jvm:0.9.0 or org.jetbrains.kotlin:kotlin-metadata-jvm:2.0.0 to client code that uses AutoBuilder to build Kotlin classes. The metadata API has changed from kotlinx.metadata to kotlin.metadata, but AutoBuilder uses reflection to function with either. (260b61ec7)
• Support for generating Java 7 code has been removed from AutoValue, AutoAnnotation, and AutoBuilder. You must be on at least Java 8, or an Android version with desugaring that allows it to pass for Java 8. 1.10.4 is the last AutoValue version with support for Java 7. (b9142b7cd)
• AutoBuilder now reports an error if it encounters a @Nullable primitive parameter. Primitive types cannot be null, and should not be annotated for nullness. (7cbdeb43b)
• Annotations on type parameters, like abstract @Nullable T foo(), are now better propagated to fields and constructor parameters. (92d881ed9)
• The generated toBuilder() method now says new AutoValue_Foo.Builder(this) rather than just new Builder(this), to do the right thing if an extension generates its own subclass of Builder. (324470ba2)
• The "copy constructor" in a generated Builder is no longer private. (6730615c9)
• Added support for extending AutoValue.Builder with abstract methods. (7d4b020dd)
• The annotation processors now support all kinds of resource URLs when loading template resources. This change only affects the case where the AutoValue (etc) processors are being invoked in an unusual environment, for example from a GraalVM app. It does not affect code that is merely being compiled for such an environment. (80b0ada75)

Full Changelog: google/auto@auto-value-1.10.4...auto-value-1.11.0

AutoValue 1.10.4

• A workaround for a JDK bug with reading jar resources has been extended so it always applies, rather than just as a fallback. See #1572. (3f69cd255)
• If an AutoValue property method is @Nullable, the corresponding field in the generated class will be too. This was already the case for TYPE_USE @Nullable or if the method had @CopyAnnotations, but now @Nullable will be copied in other cases too. (4506804f1)

AutoValue 1.10.3

• An "incompatible version" issue with Kotlin compilation has been fixed. See #1574. (b21c7f4fb)
• A warning is now produced if a setX method in a Builder or its return type is marked @Nullable. Those methods always return the Builder instance, which is never null. (e5b4b5484)

Commits

• 4a03588 Set version number for auto-value-parent to 1.11.1.
• c5c1ae5 Update do-not-publish configuration.
• 6d41b70 [maven-release-plugin] prepare for next development iteration
• 74d3d07 [maven-release-plugin] prepare release auto-value-parent-1.11.1
• 82eb4f8 Bump the dependencies group in /value with 2 updates
• d09c2d3 Bump the dependencies group in /value with 4 updates
• 893034b Delete the WeakHashMap recommendation.
• 4bcb6b9 Bump net.ltgt.gwt.maven:gwt-maven-plugin from 1.1.0 to 1.2.0 in /value in the...
• 66a26da Slightly reword @​AutoOneOf docs
• 7e5e3c8 Bump the dependencies group in /value with 2 updates
• Additional commits viewable in compare view

Updates com.google.auto.value:auto-value-annotations from 1.10.2 to 1.11.1

Release notes

Sourced from com.google.auto.value:auto-value-annotations's releases.

AutoValue 1.11.1

• Fixed a crash with @AutoValue.CopyAnnotations(exclude=Missing.class), where Missing is a class that does not exist.
• Type-use annotations such as @Nullable are now better preserved in generated builder setter method parameters. Previously they could be lost in some circumstances, for example with @Nullable T.
• An issue with @Nullable type-use annotations in AutoBuilder has been fixed.
• Report a diagnostic for setters with boxed primitive types for primitive properties.
• A bug with AutoBuilder and Kotlin data classes has been fixed. If there was a mix of required and optional parameters in a data class with a large number of properties, sometimes the generated code would not compile.

AutoValue 1.11.0

What's Changed

• AutoValue (including AutoBuilder) no longer bundles the Kotlin metadata API. This may require adding an explicit dependency on org.jetbrains.kotlinx:kotlinx-metadata-jvm:0.9.0 or org.jetbrains.kotlin:kotlin-metadata-jvm:2.0.0 to client code that uses AutoBuilder to build Kotlin classes. The metadata API has changed from kotlinx.metadata to kotlin.metadata, but AutoBuilder uses reflection to function with either. (260b61ec7)
• Support for generating Java 7 code has been removed from AutoValue, AutoAnnotation, and AutoBuilder. You must be on at least Java 8, or an Android version with desugaring that allows it to pass for Java 8. 1.10.4 is the last AutoValue version with support for Java 7. (b9142b7cd)
• AutoBuilder now reports an error if it encounters a @Nullable primitive parameter. Primitive types cannot be null, and should not be annotated for nullness. (7cbdeb43b)
• Annotations on type parameters, like abstract @Nullable T foo(), are now better propagated to fields and constructor parameters. (92d881ed9)
• The generated toBuilder() method now says new AutoValue_Foo.Builder(this) rather than just new Builder(this), to do the right thing if an extension generates its own subclass of Builder. (324470ba2)
• The "copy constructor" in a generated Builder is no longer private. (6730615c9)
• Added support for extending AutoValue.Builder with abstract methods. (7d4b020dd)
• The annotation processors now support all kinds of resource URLs when loading template resources. This change only affects the case where the AutoValue (etc) processors are being invoked in an unusual environment, for example from a GraalVM app. It does not affect code that is merely being compiled for such an environment. (80b0ada75)

Full Changelog: google/auto@auto-value-1.10.4...auto-value-1.11.0

AutoValue 1.10.4

• A workaround for a JDK bug with reading jar resources has been extended so it always applies, rather than just as a fallback. See #1572. (3f69cd255)
• If an AutoValue property method is @Nullable, the corresponding field in the generated class will be too. This was already the case for TYPE_USE @Nullable or if the method had @CopyAnnotations, but now @Nullable will be copied in other cases too. (4506804f1)

AutoValue 1.10.3

• An "incompatible version" issue with Kotlin compilation has been fixed. See #1574. (b21c7f4fb)
• A warning is now produced if a setX method in a Builder or its return type is marked @Nullable. Those methods always return the Builder instance, which is never null. (e5b4b5484)

Commits

• 4a03588 Set version number for auto-value-parent to 1.11.1.
• c5c1ae5 Update do-not-publish configuration.
• 6d41b70 [maven-release-plugin] prepare for next development iteration
• 74d3d07 [maven-release-plugin] prepare release auto-value-parent-1.11.1
• 82eb4f8 Bump the dependencies group in /value with 2 updates
• d09c2d3 Bump the dependencies group in /value with 4 updates
• 893034b Delete the WeakHashMap recommendation.
• 4bcb6b9 Bump net.ltgt.gwt.maven:gwt-maven-plugin from 1.1.0 to 1.2.0 in /value in the...
• 66a26da Slightly reword @​AutoOneOf docs
• 7e5e3c8 Bump the dependencies group in /value with 2 updates
• 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 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]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml