Bump the java-production-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the java-production-dependencies group with 3 updates in the / directory: com.google.dagger:dagger, com.google.dagger:dagger-compiler and com.google.guava:guava.

Updates com.google.dagger:dagger from 2.51.1 to 2.53.1

Release notes

Sourced from com.google.dagger:dagger's releases.

Dagger 2.53.1

Bug fixes

• Fixes #4525: Update kotlin-jvm-metadata to 2.0.21 to remove dependency on Beta version. (84d3aa5f1)
• Fixes #4526: Add the originating element in LazyMapKeyProxyGenerator. (5fd8ec1a3)

Dagger 2.53

Potentially breaking changes:

@Binds methods now requires explicit nullability

New: @Binds methods must explicitly declare nullability (previously we tried to infer it from the parameter). This change aligns the nullability behavior of @Binds with how nullability is treated elsewhere in Dagger by requiring it to be explict at the request and declaration sites. (4941926c5)

Suggested fix: If you get a failure due to this change, add the proper nullability to your @Binds method/parameter. For example:

@Module
interface MyModule {
-    @Binds fun bindToNullableImpl(impl: FooImpl): Foo
+    @Binds fun bindToNullableImpl(impl: FooImpl?): Foo?
}

Scopes are now banned on @Binds that delegate to production implementations.

New: Scoping an @Binds method that delegates to an @Produces implementation is not allowed. The scope was ignored anyway because production bindings are implicitly scoped. (03b237ff2)

Suggested fix: Remove the scope annotation (since the scope was ignored, this should not be a functional change).

@Module
interface MyModule {
-    @ProductionScoped
     @Binds fun bindToProductionImpl(impl: FooImpl): Foo
}

@JvmSuppressWildcards now required on multibound map requests in KSP.

New: When requesting a multibound map, users must include @JvmSuppressWildcards on the map's value, e.g. Map<K, @JvmSuppressWildcards V>. Note that this has always been the behavior in KAPT, but due to a bug in the KSP implementation we accidentally matched the request without @JvmSuppressWildcards.

Suggested fix: Unfortunately, this means users may need to add back @JvmSuppressWildcards

... (truncated)

Commits

• d33c3e7 2.53.1 release
• dde28e5 Make Hilt copy type-use nullness annotations, too.
• 84d3aa5 Update kotlin (and related dependencies) to 2.0.21.
• 09a4246 Nit
• 5fd8ec1 Add the originating element in LazyMapKeyProxyGenerator.
• 384ad08 Update Dagger yml and README with new latest version number.
• 369bbc6 [Refactor]: Move members injection optimization into its RequestRepresentation.
• 841d765 Internal changes
• 2d75be9 Internal changes
• 4046f2c [Refactor]: Change FrameworkField#create() to better align with the XPoet m...
• Additional commits viewable in compare view

Updates com.google.dagger:dagger-compiler from 2.51.1 to 2.53.1

Release notes

Sourced from com.google.dagger:dagger-compiler's releases.

Dagger 2.53.1

Bug fixes

• Fixes #4525: Update kotlin-jvm-metadata to 2.0.21 to remove dependency on Beta version. (84d3aa5f1)
• Fixes #4526: Add the originating element in LazyMapKeyProxyGenerator. (5fd8ec1a3)

Dagger 2.53

Potentially breaking changes:

@Binds methods now requires explicit nullability

New: @Binds methods must explicitly declare nullability (previously we tried to infer it from the parameter). This change aligns the nullability behavior of @Binds with how nullability is treated elsewhere in Dagger by requiring it to be explict at the request and declaration sites. (4941926c5)

Suggested fix: If you get a failure due to this change, add the proper nullability to your @Binds method/parameter. For example:

@Module
interface MyModule {
-    @Binds fun bindToNullableImpl(impl: FooImpl): Foo
+    @Binds fun bindToNullableImpl(impl: FooImpl?): Foo?
}

Scopes are now banned on @Binds that delegate to production implementations.

New: Scoping an @Binds method that delegates to an @Produces implementation is not allowed. The scope was ignored anyway because production bindings are implicitly scoped. (03b237ff2)

Suggested fix: Remove the scope annotation (since the scope was ignored, this should not be a functional change).

@Module
interface MyModule {
-    @ProductionScoped
     @Binds fun bindToProductionImpl(impl: FooImpl): Foo
}

@JvmSuppressWildcards now required on multibound map requests in KSP.

New: When requesting a multibound map, users must include @JvmSuppressWildcards on the map's value, e.g. Map<K, @JvmSuppressWildcards V>. Note that this has always been the behavior in KAPT, but due to a bug in the KSP implementation we accidentally matched the request without @JvmSuppressWildcards.

Suggested fix: Unfortunately, this means users may need to add back @JvmSuppressWildcards

... (truncated)

Commits

• d33c3e7 2.53.1 release
• dde28e5 Make Hilt copy type-use nullness annotations, too.
• 84d3aa5 Update kotlin (and related dependencies) to 2.0.21.
• 09a4246 Nit
• 5fd8ec1 Add the originating element in LazyMapKeyProxyGenerator.
• 384ad08 Update Dagger yml and README with new latest version number.
• 369bbc6 [Refactor]: Move members injection optimization into its RequestRepresentation.
• 841d765 Internal changes
• 2d75be9 Internal changes
• 4046f2c [Refactor]: Change FrameworkField#create() to better align with the XPoet m...
• Additional commits viewable in compare view

Updates com.google.guava:guava from 33.2.1-jre to 33.3.1-jre

Release notes

Sourced from com.google.guava:guava's releases.

33.3.1

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.3.1-jre</version>
  <!-- or, for Android: -->
  <version>33.3.1-android</version>
</dependency>

Jar files

• 33.3.1-jre.jar
• 33.3.1-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.1.jar

Javadoc

• 33.3.1-jre
• 33.3.1-android

JDiff

• 33.3.1-jre vs. 33.3.0-jre
• 33.3.1-android vs. 33.3.0-android
• 33.3.1-android vs. 33.3.1-jre

Changelog

• Added j2objc-annotations to the Gradle runtime classpath to stop producing an Android Gradle Plugin error. (a3b51888c2)

33.3.0

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.3.0-jre</version>
  <!-- or, for Android: -->
  <version>33.3.0-android</version>
</dependency>

... (truncated)

Commits

• See full diff in compare view

Updates com.google.dagger:dagger-compiler from 2.51.1 to 2.53.1

Release notes

Sourced from com.google.dagger:dagger-compiler's releases.

Dagger 2.53.1

Bug fixes

• Fixes #4525: Update kotlin-jvm-metadata to 2.0.21 to remove dependency on Beta version. (84d3aa5f1)
• Fixes #4526: Add the originating element in LazyMapKeyProxyGenerator. (5fd8ec1a3)

Dagger 2.53

Potentially breaking changes:

@Binds methods now requires explicit nullability

New: @Binds methods must explicitly declare nullability (previously we tried to infer it from the parameter). This change aligns the nullability behavior of @Binds with how nullability is treated elsewhere in Dagger by requiring it to be explict at the request and declaration sites. (4941926c5)

Suggested fix: If you get a failure due to this change, add the proper nullability to your @Binds method/parameter. For example:

@Module
interface MyModule {
-    @Binds fun bindToNullableImpl(impl: FooImpl): Foo
+    @Binds fun bindToNullableImpl(impl: FooImpl?): Foo?
}

Scopes are now banned on @Binds that delegate to production implementations.

New: Scoping an @Binds method that delegates to an @Produces implementation is not allowed. The scope was ignored anyway because production bindings are implicitly scoped. (03b237ff2)

Suggested fix: Remove the scope annotation (since the scope was ignored, this should not be a functional change).

@Module
interface MyModule {
-    @ProductionScoped
     @Binds fun bindToProductionImpl(impl: FooImpl): Foo
}

@JvmSuppressWildcards now required on multibound map requests in KSP.

New: When requesting a multibound map, users must include @JvmSuppressWildcards on the map's value, e.g. Map<K, @JvmSuppressWildcards V>. Note that this has always been the behavior in KAPT, but due to a bug in the KSP implementation we accidentally matched the request without @JvmSuppressWildcards.

Suggested fix: Unfortunately, this means users may need to add back @JvmSuppressWildcards

... (truncated)

Commits

• d33c3e7 2.53.1 release
• dde28e5 Make Hilt copy type-use nullness annotations, too.
• 84d3aa5 Update kotlin (and related dependencies) to 2.0.21.
• 09a4246 Nit
• 5fd8ec1 Add the originating element in LazyMapKeyProxyGenerator.
• 384ad08 Update Dagger yml and README with new latest version number.
• 369bbc6 [Refactor]: Move members injection optimization into its RequestRepresentation.
• 841d765 Internal changes
• 2d75be9 Internal changes
• 4046f2c [Refactor]: Change FrameworkField#create() to better align with the XPoet m...
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Superseded by #266.