Bump versions.autoValue from 1.6.5 to 1.10.1

[dependabot]

Bumps versions.autoValue from 1.6.5 to 1.10.1.
Updates com.google.auto.value:auto-value-annotations from 1.6.5 to 1.10.1

Release notes

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

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)

AutoValue 1.9

• The @AutoBuilder annotation documented here is now fully stable and supported. (1f8d7f26)
  • AutoBuilder now uses annotation defaults when building a call to an @AutoAnnotation method. (fb96c836)
• Making a step-builder for AutoValue is now easier because the inherited setters don't need to be restated in the Builder class so that they return Builder. (0820e2e2)
• We now handle better the case where an annotation being copied references a missing class. (e0740327)
• The order of annotations copied into generated code is now deterministic. (8ad800ed)

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)

... (truncated)

Commits

• c698816 Set version number for auto-value-parent to 1.10.1.
• 6de325b Ensure that org.jetbrains.annotations is shaded in the AutoValue jar.
• 61967ec Fix the variable name in the example of "When parameter names are unavailable".
• a91775b Bump mockito-core from 4.8.1 to 4.9.0 in /value
• d7218d5 Bump kotlin.version from 1.7.20 to 1.7.21 in /value
• eea4094 Bump maven-shade-plugin from 3.4.0 to 3.4.1 in /value
• 3659a0e Fix an issue with builder getters.
• aeffb90 Bump mockito-core from 4.8.0 to 4.8.1 in /value
• b8f2bad Bump styfle/cancel-workflow-action from 0.10.1 to 0.11.0
• 4bb91ca Propagate parameter annotations in generated factory code.
• Additional commits viewable in compare view

Updates com.google.auto.value:auto-value from 1.6.5 to 1.10.1

Release notes

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

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)

AutoValue 1.9

• The @AutoBuilder annotation documented here is now fully stable and supported. (1f8d7f26)
  • AutoBuilder now uses annotation defaults when building a call to an @AutoAnnotation method. (fb96c836)
• Making a step-builder for AutoValue is now easier because the inherited setters don't need to be restated in the Builder class so that they return Builder. (0820e2e2)
• We now handle better the case where an annotation being copied references a missing class. (e0740327)
• The order of annotations copied into generated code is now deterministic. (8ad800ed)

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)

... (truncated)

Commits

• c698816 Set version number for auto-value-parent to 1.10.1.
• 6de325b Ensure that org.jetbrains.annotations is shaded in the AutoValue jar.
• 61967ec Fix the variable name in the example of "When parameter names are unavailable".
• a91775b Bump mockito-core from 4.8.1 to 4.9.0 in /value
• d7218d5 Bump kotlin.version from 1.7.20 to 1.7.21 in /value
• eea4094 Bump maven-shade-plugin from 3.4.0 to 3.4.1 in /value
• 3659a0e Fix an issue with builder getters.
• aeffb90 Bump mockito-core from 4.8.0 to 4.8.1 in /value
• b8f2bad Bump styfle/cancel-workflow-action from 0.10.1 to 0.11.0
• 4bb91ca Propagate parameter annotations in generated factory code.
• 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)