build(deps): bump autovalue from 1.8.1 to 1.11.1

[dependabot]

Bumps autovalue from 1.8.1 to 1.11.1.
Updates com.google.auto.value:auto-value-annotations from 1.8.1 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)

AutoValue 1.10.2

• The constructor parameter names in the class generated by @Memoized no longer add a $. This may require changes to code that was depending on the old names, for example using Error Prone's /* param= */ comments. (4f8dbea8a)
• An AutoValue or AutoBuilder property is now allowed to be null if its type is a type variable with a @Nullable bound, like <T extends @Nullable Object>. (1b58cff5e)
• Better error message when AutoValue, AutoBuilder, etc give up because of missing types. We now say what the first missing type was. (2e734f605)
• AutoBuilder copy-constructors no longer require an exact match between a property and the corresponding constructor parameter. (1440a25e4)
• A property of type List<T> can be built by a property builder whose build() method returns List<? extends T>. (8ba4531b8)
• Made it easier to support @CopyAnnotations in AutoValue extensions, via new methods classAnnotationsToCopy and methodAnnotationsToCopy. (a3f218d2b)
• Generated builders now include a @Nullable type annotation on appropriate builder fields if one is available. (91d5f32c6)
• Updated @AutoAnnotation documentation to say that it isn't needed in Kotlin. (600b4b6d0)
• Maven dependencies have been updated, fixing #1532.

AutoValue 1.10.1

• Two annotations from org.jetbrains.annotations were accidentally included unshaded in the AutoValue jar. That has been fixed. (6de325b0c)
• Fixed an issue when a builder has a property foo with both a getter foo() and a builder fooBuilder(). (3659a0e64)

AutoValue 1.10

• AutoBuilder is now stable and supported. (2e44a5327)
  • AutoBuilder now allows you to omit a Kotlin default parameter when building a Kotlin class. (d2f91bf32)
  • An @AutoBuilder class can now have @AutoValue.CopyAnnotations so annotations are copied from the class to its generated subclass. (3a15c8834)
  • The generated AutoBuilder class now has a "copy constructor" if values for the builder properties can be obtained from the built type. (b3b53a344)
  • AutoBuilder can now be used to build annotation implementations directly. (196c8100d)

... (truncated)

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 from 1.6.5 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)

AutoValue 1.10.2

• The constructor parameter names in the class generated by @Memoized no longer add a $. This may require changes to code that was depending on the old names, for example using Error Prone's /* param= */ comments. (4f8dbea8a)
• An AutoValue or AutoBuilder property is now allowed to be null if its type is a type variable with a @Nullable bound, like <T extends @Nullable Object>. (1b58cff5e)
• Better error message when AutoValue, AutoBuilder, etc give up because of missing types. We now say what the first missing type was. (2e734f605)
• AutoBuilder copy-constructors no longer require an exact match between a property and the corresponding constructor parameter. (1440a25e4)
• A property of type List<T> can be built by a property builder whose build() method returns List<? extends T>. (8ba4531b8)
• Made it easier to support @CopyAnnotations in AutoValue extensions, via new methods classAnnotationsToCopy and methodAnnotationsToCopy. (a3f218d2b)
• Generated builders now include a @Nullable type annotation on appropriate builder fields if one is available. (91d5f32c6)
• Updated @AutoAnnotation documentation to say that it isn't needed in Kotlin. (600b4b6d0)
• Maven dependencies have been updated, fixing #1532.

AutoValue 1.10.1

• Two annotations from org.jetbrains.annotations were accidentally included unshaded in the AutoValue jar. That has been fixed. (6de325b0c)
• Fixed an issue when a builder has a property foo with both a getter foo() and a builder fooBuilder(). (3659a0e64)

AutoValue 1.10

• AutoBuilder is now stable and supported. (2e44a5327)
  • AutoBuilder now allows you to omit a Kotlin default parameter when building a Kotlin class. (d2f91bf32)
  • An @AutoBuilder class can now have @AutoValue.CopyAnnotations so annotations are copied from the class to its generated subclass. (3a15c8834)
  • The generated AutoBuilder class now has a "copy constructor" if values for the builder properties can be obtained from the built type. (b3b53a344)
  • AutoBuilder can now be used to build annotation implementations directly. (196c8100d)

... (truncated)

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

[github-actions]

📝 PRs merging into main branch

Our main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released.

[github-actions]

plugins test results

67 tests   67 ✅  1m 57s ⏱️
12 suites   0 💤
12 files     0 ❌

Results for commit c1b44f4.

♻️ This comment has been updated with latest results.