Bump auto-value.version from 1.6.6 to 1.8.2

[dependabot[bot]]

Bumps auto-value.version from 1.6.6 to 1.8.2. Updates auto-value-annotations from 1.6.6 to 1.8.2

Release notes

Sourced from auto-value-annotations's releases.

AutoValue 1.8.2

• Fixed a bug with AutoBuilder and property builder methods. (05ea1356)
• Generated builder code is now slightly friendly to null-analysis. (f00c32a5)
• Fixed a problem where @SerializableAutoValue could generate incorrect code for complex types. (689c8d49)
• Implicitly exclude Kotlin @Metadata annotations from @CopyAnnotations (7d3aa66e)

AutoValue 1.8.1

• Fixed Gradle incremental compilation. (8f17e4c4)

AutoValue 1.8

• The parameter of equals(Object) is annotated with @Nullable if any method signature mentions @Nullable. (4d01ce62)
• If an @AutoOneOf class has a serialVersionUID this is now copied to its generated subclasses. THIS BREAKS SERIAL COMPATIBILITY for @AutoOneOf classes with explicit serialVersionUID declarations, though those were already liable to be broken by arbitrary changes to the generated AutoOneOf code. (71d81210)

AutoValue 1.7.5

• Added @ToPrettyString for generating pretty String versions for AutoValue types. (9e9be9fa)
• AutoValue property builders can now have a single parameter which is passed to the constructor of the new builder. (f19117aa)
• AutoValue now copies annotations from type parameters of an @AutoValue class to the subclass generated by the @Memoized extension. (77de95c3)
• Avoid surprising behaviour when getters are prefixed and setters are not, and a property name begins with two capital letters. (1bfc3b53)
• The methods returned by BuilderContext.buildMethod() and .toBuilderMethods() can be inherited. (f2cb2247)
• Fixed a bug which could lead to the same AutoValue extension being run more than once. (f40317ae)
• AutoAnnotationProcessor and AutoServiceProcessor no longer claim their annotations. (c27b527a)
• @AutoAnnotation instances are now serializable. (7eb2d47a)
• Fully qualify @Override to avoid name conflicts (85af4437)
• AutoValue error messages now have short [tags] so they can be correlated by tools. (c6e35e68)

AutoValue 1.7.4

• Stop the LazyInit annotation from getting shaded by Maven, so that AutoValue can find it on the classpath. (b484417)
• Fixed handling of @Nullable Optional<T> foo() properties being set by setFoo(@Nullable T) setters. Now setFoo(null) results in Optional.empty(), not null. (d9d66ad)

AutoValue 1.7.3

• Optionally copy annotations from the @AutoValue.Builder class to the generated subclass. (b22f969)
• Drop unnecessary parentheses in AutoAnnotation equals and hashCode methods. (b9ba06a)
• Fixed a problem when an @AutoValue class references types that are generated by other annotation processors. (2797d38)

AutoValue 1.7.2

Only one change in this release:

• AutoValue is once again "isolating" for Gradle incremental compilation. (8e7515a)

AutoValue 1.7.1

New features

• SerializableAutoValue extension. This can be used to serialize @AutoValue classes with properties of type java.util.Optional, even though java.util.Optional is not serializable, and it can also be configured to serialize other arbitrary types. Thanks to @​alvinlao for this contribution! (f91d2fe)
• The logic for determining if we can make a BarBuilder out of a Bar has been generalized. For example, if your @AutoValue class Foo has a property IntList ints(), then your builder can have IntListBuilder intsBuilder(). Previously this worked if there was no Foo.toBuilder() method, or if IntList had its own toBuilder() method. Now it also works if it is possible to call IntListBuilder.addAll(IntList). (6aeb44f)
• AutoValue now allows boxed properties to be set from the corresponding primitive type, for example Integer from int. (2bbe506)

Behaviour changes

• AutoValue now gives a warning if the static builder() method is inside the @AutoValue.Builder class instead of directly in the @AutoValue class. (fcccded)
• AutoValue doesn't generate code or invoke extensions if it detects a problem, for example a mismatch between getters and setters. (ecb6032)
• AutoOneOf factory methods for void values now have type parameters if the @AutoOneOf class does. (4ab1b53)
• It is now a compilation error if a setter method in a builder has a parameter marked @Nullable when the corresponding property is not in fact @Nullable. Calling such a method with a null parameter already generated a NullPointerException at runtime. (bd7bed2)

... (truncated)

Commits

• 19a86d6 Set version number for auto-value-parent to 1.8.2.
• 04ebf9c Bump kotlin.version from 1.5.20 to 1.5.21 in /value
• f09743c Annotate com.google.auto.factory for null hygiene.
• 895a4d5 Internal change
• e72fc7b Internal change
• 4f6f782 Internal change
• 3b1f449 Avoid wildcards, which confuse our nullness checker.
• 9d79ce1 Annotate auto-common for nullness.
• 2ee7f62 Rewrite some references to JSpecify @Nullable to prevent their being rewrit...
• c68b2ff Use more fluent streams constructs.
• Additional commits viewable in compare view

Updates auto-value from 1.6.6 to 1.8.2

Release notes

Sourced from auto-value's releases.

AutoValue 1.8.2

• Fixed a bug with AutoBuilder and property builder methods. (05ea1356)
• Generated builder code is now slightly friendly to null-analysis. (f00c32a5)
• Fixed a problem where @SerializableAutoValue could generate incorrect code for complex types. (689c8d49)
• Implicitly exclude Kotlin @Metadata annotations from @CopyAnnotations (7d3aa66e)

AutoValue 1.8.1

• Fixed Gradle incremental compilation. (8f17e4c4)

AutoValue 1.8

• The parameter of equals(Object) is annotated with @Nullable if any method signature mentions @Nullable. (4d01ce62)
• If an @AutoOneOf class has a serialVersionUID this is now copied to its generated subclasses. THIS BREAKS SERIAL COMPATIBILITY for @AutoOneOf classes with explicit serialVersionUID declarations, though those were already liable to be broken by arbitrary changes to the generated AutoOneOf code. (71d81210)

AutoValue 1.7.5

• Added @ToPrettyString for generating pretty String versions for AutoValue types. (9e9be9fa)
• AutoValue property builders can now have a single parameter which is passed to the constructor of the new builder. (f19117aa)
• AutoValue now copies annotations from type parameters of an @AutoValue class to the subclass generated by the @Memoized extension. (77de95c3)
• Avoid surprising behaviour when getters are prefixed and setters are not, and a property name begins with two capital letters. (1bfc3b53)
• The methods returned by BuilderContext.buildMethod() and .toBuilderMethods() can be inherited. (f2cb2247)
• Fixed a bug which could lead to the same AutoValue extension being run more than once. (f40317ae)
• AutoAnnotationProcessor and AutoServiceProcessor no longer claim their annotations. (c27b527a)
• @AutoAnnotation instances are now serializable. (7eb2d47a)
• Fully qualify @Override to avoid name conflicts (85af4437)
• AutoValue error messages now have short [tags] so they can be correlated by tools. (c6e35e68)

AutoValue 1.7.4

• Stop the LazyInit annotation from getting shaded by Maven, so that AutoValue can find it on the classpath. (b484417)
• Fixed handling of @Nullable Optional<T> foo() properties being set by setFoo(@Nullable T) setters. Now setFoo(null) results in Optional.empty(), not null. (d9d66ad)

AutoValue 1.7.3

• Optionally copy annotations from the @AutoValue.Builder class to the generated subclass. (b22f969)
• Drop unnecessary parentheses in AutoAnnotation equals and hashCode methods. (b9ba06a)
• Fixed a problem when an @AutoValue class references types that are generated by other annotation processors. (2797d38)

AutoValue 1.7.2

Only one change in this release:

• AutoValue is once again "isolating" for Gradle incremental compilation. (8e7515a)

AutoValue 1.7.1

New features

• SerializableAutoValue extension. This can be used to serialize @AutoValue classes with properties of type java.util.Optional, even though java.util.Optional is not serializable, and it can also be configured to serialize other arbitrary types. Thanks to @​alvinlao for this contribution! (f91d2fe)
• The logic for determining if we can make a BarBuilder out of a Bar has been generalized. For example, if your @AutoValue class Foo has a property IntList ints(), then your builder can have IntListBuilder intsBuilder(). Previously this worked if there was no Foo.toBuilder() method, or if IntList had its own toBuilder() method. Now it also works if it is possible to call IntListBuilder.addAll(IntList). (6aeb44f)
• AutoValue now allows boxed properties to be set from the corresponding primitive type, for example Integer from int. (2bbe506)

Behaviour changes

• AutoValue now gives a warning if the static builder() method is inside the @AutoValue.Builder class instead of directly in the @AutoValue class. (fcccded)
• AutoValue doesn't generate code or invoke extensions if it detects a problem, for example a mismatch between getters and setters. (ecb6032)
• AutoOneOf factory methods for void values now have type parameters if the @AutoOneOf class does. (4ab1b53)
• It is now a compilation error if a setter method in a builder has a parameter marked @Nullable when the corresponding property is not in fact @Nullable. Calling such a method with a null parameter already generated a NullPointerException at runtime. (bd7bed2)

... (truncated)

Commits

• 19a86d6 Set version number for auto-value-parent to 1.8.2.
• 04ebf9c Bump kotlin.version from 1.5.20 to 1.5.21 in /value
• f09743c Annotate com.google.auto.factory for null hygiene.
• 895a4d5 Internal change
• e72fc7b Internal change
• 4f6f782 Internal change
• 3b1f449 Avoid wildcards, which confuse our nullness checker.
• 9d79ce1 Annotate auto-common for nullness.
• 2ee7f62 Rewrite some references to JSpecify @Nullable to prevent their being rewrit...
• c68b2ff Use more fluent streams constructs.
• 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 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)