Bump com.google.auto.value:auto-value from 1.9 to 1.11.0

[dependabot]

Bumps com.google.auto.value:auto-value from 1.9 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)

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)
• Fixed an issue when Serializable and Memoized extensions are used together. (e01968d16)
• @AutoAnnotation now has CLASS rather than SOURCE retention, making for better operation with Gradle incremental compilation. (34c3be569)
• @AutoAnnotation methods no longer need to be static. This makes it easier to use AutoAnnotation with Kotlin. (cf55dc644)
• AutoValue and AutoBuilder builders now use bitmasks to track unset primitive properties, which will typically lead to smaller builder objects and faster build times. (b5d398977)

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