⬆️ Bump auto-value from 1.6.5 to 1.7.4

[dependabot-preview]

Bumps auto-value from 1.6.5 to 1.7.4.

Release notes

Sourced from auto-value's releases.

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)
• The @Memoized annotation now has class-level retention, rather than source-level. (107694b)

Bug fixes

• We fixed an issue with type checking of setter parameters in the presence of inheritance and generics. (e97d1f0)
• We now generate a better toString() for arrays in AutoOneOf (0a7c049)

Miscellaneous

• We added CompileWithEclipseTest, which checks that AutoValue works with ecj, the Eclipse compiler. (05e983c)

AutoValue 1.7

This is the same as 1.7rc1, with one small addition:

• Add a way for extensions to retrieve the name of the final AutoValue_Foo class. (4543619)

Thanks to @bryanstern for checking that the API changes for builder introspection do indeed work in a real extension.

AutoValue 1.7rc1

• Add an API to allow AutoValue extensions to find out about builders. (86f4563)
• The generated AutoValue builder class is no longer final if there are extensions generating code. This means that extensions can subclass Builder to modify or extend its functionality. (49fbf55)
• Property builders now work correctly when their actual return type is different from the corresponding property type because of type variable substitution. (7646889)
• Allow @AutoValue getters to define properties that are not valid Java identifiers, for example get1st(). (6dfa04e)
• Add a propertyTypes() method to AutoValueExtension.Context, to allow extensions to see the true type of every property. In preference to properties().get(p).getReturnType(), extensions should use propertyTypes().get(p). (99ae134)

Commits

• c59110e Set version number for auto-value-parent to 1.7.4.
• b484417 Stop the LazyInit annotation from getting shaded by Maven, so that AutoValue ...
• d9d66ad Fix handling of @Nullable Optional\<T> foo() properties being set by `setFoo...
• da84ef1 Tests related to e62e0abd2fbdfd2512c292ef95d4d152a5ca0691
• df5641b [ #HiltMigration ] Updating BasicAnnotationProcessor to support a String-base...
• e62e0ab Fix a problem with references to Factory classes in other packages.
• 08f930a Make the nested @AutoValue class static otherwise you get the following error:
• 32fdb09 Change links from google.github.io/guava to guava.dev, including making sure ...
• 2f437b5 Change error reporting methods to use format strings.
• b22f969 Copy annotations from @AutoValue.Builder to the generated Builder subclass.
• 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)