Bump the migrator group across 1 directory with 5 updates

[dependabot]

Bumps the migrator group with 5 updates in the /migrator directory:

Package	From	To
com.google.truth:truth	1.0.1	1.4.4
info.picocli:picocli	4.7.4	4.7.6
com.google.truth.extensions:truth-java8-extension	1.0.1	1.4.4
com.google.auto.value:auto-value	1.10.2	1.11.0
com.google.auto.value:auto-value-annotations	1.10.2	1.11.0

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

Release notes

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

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 will become ambiguous in Truth 1.4.2, breaking your build.

1.4.0

In this release, our assertions on Java 8 types continue to move from the Truth8 class to the main Truth class. This change should not break compatibility for any supported JDK or Android version, even users who test under old versions of Android without API desugaring. Additionally, we will never break binary compatibility, though some users will have to make changes to their source code in order for it to compile against newer versions.

This release is likely to lead to more build failures than 1.3.0 did. However, those failures should be straightforward to fix.

Example build failure

Foo.java:152: error: reference to assertThat is ambiguous
    assertThat(repo.findFileWithName("foo")).isNull();
</tr></table> 

... (truncated)

Commits

• See full diff in compare view

Updates info.picocli:picocli from 4.7.4 to 4.7.6

Release notes

Sourced from info.picocli:picocli's releases.

Picocli 4.7.6

Picocli 4.7.6

The picocli community is pleased to announce picocli 4.7.6.

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-fifth 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

PropertiesDefaultProvider now tries to load properties from the classpath if the file cannot be found in the user.home directory.

Fixed issues

• #2102#2107 Enhancement: PropertiesDefaultProvider should try to load properties from classpath (last). Thanks to Lumír Návrat for the pull request.
• #2202 Enhancement: Change log level from WARN to INFO when bean not found in ApplicationContext. Thanks to Desmond Kirrane for raising this.
• #2248 Enhancement: Don't show hidden commands in JLine3 command description. Thanks to Reinhard Handler for the pull request.
• #2170 Enhancement: Use ... vararg instead of array parameter to match overridden method signature. Thanks to Michael Vorburger for the pull request.
• #2058 Bugfix: defaultValue should not be applied in addition to user-specified value for options with a custom IParameterConsumer. Thanks to Staffan Arvidsson McShane for raising this.
• #2148 Bugfix: Fix NPE in jline3 Example.jar as ConfigurationPath cannot be null anymore. Thanks to llzen44 for the pull request.
• #2232 Bugfix: fix bug for Optional<T> arguments with initial value. Thanks to hq6 for raising this.
• #2149 Bugfix: @Option-annotated setter method not invoked with default value when used in mixin for both command and subcommand. Thanks to Zhonghao Wang for raising this.
• #2270 Bugfix: Custom type converter for primitive boolean options should not be ignored. Thanks to Sven Kammerer for raising this.
• #2234 BUILD: fix errorprone TruthSelfEquals warnings
• #2172 BUILD: Fix broken build. Thanks to Michael Vorburger for the pull request.
• #2174 BUILD: Fix .gitattributes related CR/LF problems. Thanks to Michael Vorburger for the pull request.
• #2054#2176 BUILD: Add Error Prone. Thanks to Michael Vorburger for the pull request.
• #2053 #2175 CLEAN: Remove unused extra format arguments. Thanks to Michael Vorburger for the pull request.
• #2171 DOC: Fix a few typos in CommandLine's JavaDoc. Thanks to Michael Vorburger for the pull request.
• #2217 DOC: Clarify documentation for negatable options. Thanks to dbear496 for raising this.
• #2228 DOC: Clarify that ParseResult passed to IExecutionExceptionHandler is the top-level parse result, not the parse result of the subcommand that failed. Thanks to Abel Salgado Romero for raising this.
• #2047 DEP: Bump andymckay/append-gist-action from 1fbfbbce708a39bd45846f0955ed5521f2099c6d to 6e8d64427fe47cbacf4ab6b890411f1d67c07f3e
• #2091 DEP: Bump actions/checkout from 3.5.2 to 3.6.0
• #2108 DEP: Bump actions/checkout from 3.6.0 to 4.0.0
• #2120 DEP: Bump actions/checkout from 4.0.0 to 4.1.0
• #2225 DEP: Bump actions/checkout from 4.1.0 to 4.1.2
• #2272 DEP: Bump actions/checkout from 4.1.2 to 4.1.4
• #2098 DEP: Bump actions/setup-java from 3.11.0 to 3.12.0
• #2158 DEP: Bump actions/setup-java from 3.12.0 to 4.0.0

... (truncated)

Changelog

Sourced from info.picocli:picocli's changelog.

Picocli 4.7.6

The picocli community is pleased to announce picocli 4.7.6.

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-fifth 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

PropertiesDefaultProvider now tries to load properties from the classpath if the file cannot be found in the user.home directory.

Fixed issues

• #2102#2107 Enhancement: PropertiesDefaultProvider should try to load properties from classpath (last). Thanks to Lumír Návrat for the pull request.
• #2202 Enhancement: Change log level from WARN to INFO when bean not found in ApplicationContext. Thanks to Desmond Kirrane for raising this.
• #2248 Enhancement: Don't show hidden commands in JLine3 command description. Thanks to Reinhard Handler for the pull request.
• #2170 Enhancement: Use ... vararg instead of array parameter to match overridden method signature. Thanks to Michael Vorburger for the pull request.
• #2058 Bugfix: defaultValue should not be applied in addition to user-specified value for options with a custom IParameterConsumer. Thanks to Staffan Arvidsson McShane for raising this.
• #2148 Bugfix: Fix NPE in jline3 Example.jar as ConfigurationPath cannot be null anymore. Thanks to llzen44 for the pull request.
• #2232 Bugfix: fix bug for Optional<T> arguments with initial value. Thanks to hq6 for raising this.
• #2149 Bugfix: @Option-annotated setter method not invoked with default value when used in mixin for both command and subcommand. Thanks to Zhonghao Wang for raising this.
• #2270 Bugfix: Custom type converter for primitive boolean options should not be ignored. Thanks to Sven Kammerer for raising this.
• #2234 BUILD: fix errorprone TruthSelfEquals warnings
• #2172 BUILD: Fix broken build. Thanks to Michael Vorburger for the pull request.
• #2174 BUILD: Fix .gitattributes related CR/LF problems. Thanks to Michael Vorburger for the pull request.
• #2054#2176 BUILD: Add Error Prone. Thanks to Michael Vorburger for the pull request.
• #2053 #2175 CLEAN: Remove unused extra format arguments. Thanks to Michael Vorburger for the pull request.
• #2171 DOC: Fix a few typos in CommandLine's JavaDoc. Thanks to Michael Vorburger for the pull request.
• #2217 DOC: Clarify documentation for negatable options. Thanks to dbear496 for raising this.
• #2228 DOC: Clarify that ParseResult passed to IExecutionExceptionHandler is the top-level parse result, not the parse result of the subcommand that failed. Thanks to Abel Salgado Romero for raising this.
• #2047 DEP: Bump andymckay/append-gist-action from 1fbfbbce708a39bd45846f0955ed5521f2099c6d to 6e8d64427fe47cbacf4ab6b890411f1d67c07f3e
• #2091 DEP: Bump actions/checkout from 3.5.2 to 3.6.0
• #2108 DEP: Bump actions/checkout from 3.6.0 to 4.0.0
• #2120 DEP: Bump actions/checkout from 4.0.0 to 4.1.0
• #2225 DEP: Bump actions/checkout from 4.1.0 to 4.1.2
• #2272 DEP: Bump actions/checkout from 4.1.2 to 4.1.4
• #2098 DEP: Bump actions/setup-java from 3.11.0 to 3.12.0
• #2158 DEP: Bump actions/setup-java from 3.12.0 to 4.0.0
• #2236 DEP: Bump actions/setup-java from 4.0.0 to 4.2.1.

... (truncated)

Commits

• 368d97e Release picocli version 4.7.6
• ca9fbb6 #2145 fix output dir
• 7737d84 #2145 add test
• 6430401 [BUILD] fix broken CI tests
• aa46a77 Bump actions/upload-artifact from 4.3.1 to 4.3.3
• 4843676 Bump actions/checkout from 4.1.2 to 4.1.4
• c825d20 #2270 Custom type converter for primitive boolean options should not be i...
• fa33be1 #2149 bugfix: ArgSpecs are not equal if their enclosing command is different
• 92be33a DOC update release notes for dependency updates
• 9791bd9 #2228 DOC: Clarify that ParseResult passed to `IExecutionExceptionHandler...
• Additional commits viewable in compare view

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

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

Release notes

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

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

• 5e02d64 Set version number for auto-value-parent to 1.11.0.
• 80b0ada Support all kinds of resource URLs when loading template resources.
• 260b61e Use reflection to avoid referencing the Kotlin metadata API directly.
• 76be89a Bump org.apache.maven.plugins:maven-invoker-plugin from 3.6.1 to 3.7.0 in /fa...
• c11484e Bump org.apache.maven.plugins:maven-invoker-plugin from 3.6.1 to 3.7.0 in /value
• b21d69d Bump kotlin.version from 1.9.24 to 2.0.0 in /value
• e55e60a Update AutoValue to reflect recent Kotlin Metadata API changes.
• 29f739b Bump actions/checkout from 4.1.5 to 4.1.6
• 199a727 Bump kotlin.version from 1.9.23 to 1.9.24 in /value
• f2b22e3 Bump actions/checkout from 4.1.4 to 4.1.5
• Additional commits viewable in compare view

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

Release notes

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

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

• 5e02d64 Set version number for auto-value-parent to 1.11.0.
• 80b0ada Support all kinds of resource URLs when loading template resources.
• 260b61e Use reflection to avoid referencing the Kotlin metadata API directly.
• 76be89a Bump org.apache.maven.plugins:maven-invoker-plugin from 3.6.1 to 3.7.0 in /fa...
• c11484e Bump org.apache.maven.plugins:maven-invoker-plugin from 3.6.1 to 3.7.0 in /value
• b21d69d Bump kotlin.version from 1.9.24 to 2.0.0 in /value
• e55e60a Update AutoValue to reflect recent Kotlin Metadata API changes.
• 29f739b Bump actions/checkout from 4.1.5 to 4.1.6
• 199a727 Bump kotlin.version from 1.9.23 to 1.9.24 in /value
• f2b22e3 Bump actions/checkout from 4.1.4 to 4.1.5
• 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 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