build(deps): Bump google-dagger from 2.52 to 2.53

[dependabot]

Bumps google-dagger from 2.52 to 2.53.
Updates com.google.dagger:dagger from 2.52 to 2.53

Release notes

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

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 for multibound map requests. At the moment, KSP doesn't provide a way to determine the Kotlin type is actually assignable to Map<K, V> without @JvmSuppressWildcards at compile time, and without this check users could hit runtime failures when Dagger tries to cast the type to the users type.

class MyClass
</tr></table> 

... (truncated)

Commits

• 649eed5 2.53 release
• 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...
• 9fe4824 Internal changes
• fdbc63e [Refactor]: Move ProvisionMethods#create()/InjectionSiteMethods#create() ...
• 2b84e57 Kotlin compiler update to 2.0.21, prework.
• fe811e1 Kotlin compiler update to 2.0.21, prework.
• 6b183f8 Support requesting Jakarta Provider types.
• Additional commits viewable in compare view

Updates com.google.dagger:dagger-android-processor from 2.52 to 2.53

Release notes

Sourced from com.google.dagger:dagger-android-processor's releases.

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 for multibound map requests. At the moment, KSP doesn't provide a way to determine the Kotlin type is actually assignable to Map<K, V> without @JvmSuppressWildcards at compile time, and without this check users could hit runtime failures when Dagger tries to cast the type to the users type.

class MyClass
</tr></table> 

... (truncated)

Commits

• 649eed5 2.53 release
• 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...
• 9fe4824 Internal changes
• fdbc63e [Refactor]: Move ProvisionMethods#create()/InjectionSiteMethods#create() ...
• 2b84e57 Kotlin compiler update to 2.0.21, prework.
• fe811e1 Kotlin compiler update to 2.0.21, prework.
• 6b183f8 Support requesting Jakarta Provider types.
• Additional commits viewable in compare view

Updates com.google.dagger:dagger-android-support from 2.52 to 2.53

Release notes

Sourced from com.google.dagger:dagger-android-support's releases.

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 for multibound map requests. At the moment, KSP doesn't provide a way to determine the Kotlin type is actually assignable to Map<K, V> without @JvmSuppressWildcards at compile time, and without this check users could hit runtime failures when Dagger tries to cast the type to the users type.

class MyClass
</tr></table> 

... (truncated)

Commits

• 649eed5 2.53 release
• 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...
• 9fe4824 Internal changes
• fdbc63e [Refactor]: Move ProvisionMethods#create()/InjectionSiteMethods#create() ...
• 2b84e57 Kotlin compiler update to 2.0.21, prework.
• fe811e1 Kotlin compiler update to 2.0.21, prework.
• 6b183f8 Support requesting Jakarta Provider types.
• Additional commits viewable in compare view

Updates com.google.dagger:dagger-compiler from 2.52 to 2.53

Release notes

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

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 for multibound map requests. At the moment, KSP doesn't provide a way to determine the Kotlin type is actually assignable to Map<K, V> without @JvmSuppressWildcards at compile time, and without this check users could hit runtime failures when Dagger tries to cast the type to the users type.

class MyClass
</tr></table> 

... (truncated)

Commits

• 649eed5 2.53 release
• 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...
• 9fe4824 Internal changes
• fdbc63e [Refactor]: Move ProvisionMethods#create()/InjectionSiteMethods#create() ...
• 2b84e57 Kotlin compiler update to 2.0.21, prework.
• fe811e1 Kotlin compiler update to 2.0.21, prework.
• 6b183f8 Support requesting Jakarta Provider types.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-android-compiler from 2.52 to 2.53

Release notes

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

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 for multibound map requests. At the moment, KSP doesn't provide a way to determine the Kotlin type is actually assignable to Map<K, V> without @JvmSuppressWildcards at compile time, and without this check users could hit runtime failures when Dagger tries to cast the type to the users type.

class MyClass
</tr></table> 

... (truncated)

Commits

• 649eed5 2.53 release
• 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...
• 9fe4824 Internal changes
• fdbc63e [Refactor]: Move ProvisionMethods#create()/InjectionSiteMethods#create() ...
• 2b84e57 Kotlin compiler update to 2.0.21, prework.
• fe811e1 Kotlin compiler update to 2.0.21, prework.
• 6b183f8 Support requesting Jakarta Provider types.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-android from 2.52 to 2.53

Release notes

Sourced from com.google.dagger:hilt-android's releases.

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 for multibound map requests. At the moment, KSP doesn't provide a way to determine the Kotlin type is actually assignable to Map<K, V> without @JvmSuppressWildcards at compile time, and without this check users could hit runtime failures when Dagger tries to cast the type to the users type.

class MyClass
</tr></table> 

... (truncated)

Commits

• 649eed5 2.53 release
• 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...
• 9fe4824 Internal changes
• fdbc63e [Refactor]: Move ProvisionMethods#create()/InjectionSiteMethods#create() ...
• 2b84e57 Kotlin compiler update to 2.0.21, prework.
• fe811e1 Kotlin compiler update to 2.0.21, prework.
• 6b183f8 Support requesting Jakarta Provider types.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-android-testing from 2.52 to 2.53

Release notes

Sourced from com.google.dagger:hilt-android-testing's releases.

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 for multibound map requests. At the moment, KSP doesn't provide a way to determine the Kotlin type is actually assignable to Map<K, V> without @JvmSuppressWildcards at compile time, and without this check users could hit runtime failures when Dagger tries to cast the type to the users type.

class MyClass
</tr></table> 

... (truncated)

Commits

• 649eed5 2.53 release
• 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...
• 9fe4824 Internal changes
• fdbc63e [Refactor]: Move ProvisionMethods#create()/InjectionSiteMethods#create() ...
• 2b84e57 Kotlin compiler update to 2.0.21, prework.
• fe811e1 Kotlin compiler update to 2.0.21, prework.
• 6b183f8 Support requesting Jakarta Provider types.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-compiler from 2.52 to 2.53

Release notes

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

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 for multibound map requests. At the moment, KSP doesn't provide a way to determine the Kotlin type is actually assignable to Map<K, V> without @JvmSuppressWildcards at compile time, and without this check users could hit runtime failures when Dagger tries to cast the type to the users type.

class MyClass
</tr></table> 

... (truncated)

Commits

• 649eed5 2.53 release
• 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...
• 9fe4824 Internal changes
• fdbc63e [Refactor]: Move ProvisionMethods#create()/InjectionSiteMethods#create() ...
• 2b84e57 Kotlin compiler update to 2.0.21, prework.
• fe811e1 Kotlin compiler update to 2.0.21, prework.
• 6b183f8 Support requesting Jakarta Provider types.
• Additional commits viewable in compare view

Updates com.google.dagger.hilt.android from 2.52 to 2.53

Release notes

Sourced from com.google.dagger.hilt.android's releases.

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 for multibound map requests. At the moment, KSP doesn't provide a way to determine the Kotlin type is actually assignable to Map<K, V> without @JvmSuppressWildcards at compile time, and without this check users could hit runtime failures when Dagger tries to cast the type to the users type.

class MyClass
</tr></table> 

... (truncated)

Commits

• 649eed5 2.53 release
• 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...
• 9fe4824 Internal changes
• fdbc63e [Refactor]: Move ProvisionMethods#create()/InjectionSiteMethods#create() ...
• 2b84e57 Kotlin compiler update to 2.0.21, prework.
• fe811e1 Kotlin compiler update to 2.0.21, prework.
• 6b183f8 Support requesting Jakarta Provider types.
• 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)

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wpmobilebot]

Project dependencies changes

The following changes in project dependencies were detected (configuration wordpressVanillaReleaseRuntimeClasspath):

list

New Dependencies
org.jspecify:jspecify:1.0.0

Upgraded Dependencies
com.google.dagger:dagger:2.53, (changed from 2.52)
com.google.dagger:dagger-android:2.53, (changed from 2.52)
com.google.dagger:dagger-android-support:2.53, (changed from 2.52)
com.google.dagger:dagger-lint-aar:2.53, (changed from 2.52)
com.google.dagger:hilt-android:2.53, (changed from 2.52)
com.google.dagger:hilt-core:2.53, (changed from 2.52)

tree

 +--- project :libs:fluxc
-|    \--- com.google.dagger:dagger:2.52
-|         +--- jakarta.inject:jakarta.inject-api:2.0.1
-|         \--- javax.inject:javax.inject:1
+|    \--- com.google.dagger:dagger:2.53
+|         +--- jakarta.inject:jakarta.inject-api:2.0.1
+|         +--- javax.inject:javax.inject:1
+|         \--- org.jspecify:jspecify:1.0.0
 +--- project :libs:login
-|    +--- com.google.dagger:dagger:2.52 (*)
+|    +--- com.google.dagger:dagger:2.53 (*)
-|    \--- com.google.dagger:dagger-android-support:2.52
-|         +--- com.google.dagger:dagger:2.52 (*)
-|         +--- com.google.dagger:dagger-android:2.52
-|         |    +--- com.google.dagger:dagger:2.52 (*)
-|         |    +--- com.google.dagger:dagger-lint-aar:2.52
-|         |    +--- androidx.annotation:annotation:1.3.0 -> 1.9.1 (*)
-|         |    \--- javax.inject:javax.inject:1
-|         +--- com.google.dagger:dagger-lint-aar:2.52
-|         +--- androidx.activity:activity:1.5.1 -> 1.9.3 (*)
-|         +--- androidx.annotation:annotation:1.3.0 -> 1.9.1 (*)
-|         +--- androidx.appcompat:appcompat:1.3.1 -> 1.7.0 (*)
-|         +--- androidx.fragment:fragment:1.5.1 -> 1.8.5 (*)
-|         +--- androidx.lifecycle:lifecycle-common:2.5.1 -> 2.8.7 (*)
-|         +--- androidx.lifecycle:lifecycle-viewmodel:2.5.1 -> 2.8.7 (*)
-|         +--- androidx.lifecycle:lifecycle-viewmodel-savedstate:2.5.1 -> 2.8.7 (*)
-|         \--- javax.inject:javax.inject:1
+|    \--- com.google.dagger:dagger-android-support:2.53
+|         +--- com.google.dagger:dagger:2.53 (*)
+|         +--- com.google.dagger:dagger-android:2.53
+|         |    +--- com.google.dagger:dagger:2.53 (*)
+|         |    +--- com.google.dagger:dagger-lint-aar:2.53
+|         |    +--- androidx.annotation:annotation:1.3.0 -> 1.9.1 (*)
+|         |    \--- javax.inject:javax.inject:1
+|         +--- com.google.dagger:dagger-lint-aar:2.53
+|         +--- androidx.activity:activity:1.5.1 -> 1.9.3 (*)
+|         +--- androidx.annotation:annotation:1.3.0 -> 1.9.1 (*)
+|         +--- androidx.appcompat:appcompat:1.3.1 -> 1.7.0 (*)
+|         +--- androidx.fragment:fragment:1.5.1 -> 1.8.5 (*)
+|         +--- androidx.lifecycle:lifecycle-common:2.5.1 -> 2.8.7 (*)
+|         +--- androidx.lifecycle:lifecycle-viewmodel:2.5.1 -> 2.8.7 (*)
+|         +--- androidx.lifecycle:lifecycle-viewmodel-savedstate:2.5.1 -> 2.8.7 (*)
+|         \--- javax.inject:javax.inject:1
 +--- com.zendesk:support:5.1.2
 |    +--- com.zendesk:support-providers:5.1.2
 |    |    +--- com.zendesk:core:4.0.9
-|    |    |    \--- com.google.dagger:dagger:2.42 -> 2.52 (*)
+|    |    |    \--- com.google.dagger:dagger:2.42 -> 2.53 (*)
 |    |    +--- com.zendesk:guide-providers:1.1.1
-|    |    |    \--- com.google.dagger:dagger:2.42 -> 2.52 (*)
+|    |    |    \--- com.google.dagger:dagger:2.42 -> 2.53 (*)
-|    |    \--- com.google.dagger:dagger:2.42 -> 2.52 (*)
+|    |    \--- com.google.dagger:dagger:2.42 -> 2.53 (*)
 |    +--- com.zendesk:guide:1.1.1
 |    |    +--- com.zendesk:messaging:5.3.0
-|    |    |    \--- com.google.dagger:dagger:2.42 -> 2.52 (*)
+|    |    |    \--- com.google.dagger:dagger:2.42 -> 2.53 (*)
-|    |    \--- com.google.dagger:dagger-android:2.42 -> 2.52 (*)
+|    |    \--- com.google.dagger:dagger-android:2.42 -> 2.53 (*)
-|    \--- com.google.dagger:dagger-android:2.42 -> 2.52 (*)
+|    \--- com.google.dagger:dagger-android:2.42 -> 2.53 (*)
-+--- com.google.dagger:dagger-android-support:2.52 (*)
++--- com.google.dagger:dagger-android-support:2.53 (*)
-\--- com.google.dagger:hilt-android:2.52
-     +--- com.google.dagger:dagger:2.52 (*)
-     +--- com.google.dagger:dagger-lint-aar:2.52
-     +--- com.google.dagger:hilt-core:2.52
-     |    +--- com.google.dagger:dagger:2.52 (*)
-     |    +--- com.google.code.findbugs:jsr305:3.0.2
-     |    \--- javax.inject:javax.inject:1
-     +--- com.google.code.findbugs:jsr305:3.0.2
-     +--- androidx.activity:activity:1.5.1 -> 1.9.3 (*)
-     +--- androidx.annotation:annotation:1.3.0 -> 1.9.1 (*)
-     +--- androidx.annotation:annotation-experimental:1.3.1 -> 1.4.1 (*)
-     +--- androidx.fragment:fragment:1.5.1 -> 1.8.5 (*)
-     +--- androidx.lifecycle:lifecycle-common:2.5.1 -> 2.8.7 (*)
-     +--- androidx.lifecycle:lifecycle-viewmodel:2.5.1 -> 2.8.7 (*)
-     +--- androidx.lifecycle:lifecycle-viewmodel-savedstate:2.5.1 -> 2.8.7 (*)
-     +--- androidx.savedstate:savedstate:1.2.0 -> 1.2.1 (*)
-     +--- javax.inject:javax.inject:1
-     \--- org.jetbrains.kotlin:kotlin-stdlib:1.9.24 -> 2.0.21 (*)
+\--- com.google.dagger:hilt-android:2.53
+     +--- com.google.dagger:dagger:2.53 (*)
+     +--- com.google.dagger:dagger-lint-aar:2.53
+     +--- com.google.dagger:hilt-core:2.53
+     |    +--- com.google.dagger:dagger:2.53 (*)
+     |    +--- com.google.code.findbugs:jsr305:3.0.2
+     |    \--- javax.inject:javax.inject:1
+     +--- com.google.code.findbugs:jsr305:3.0.2
+     +--- androidx.activity:activity:1.5.1 -> 1.9.3 (*)
+     +--- androidx.annotation:annotation:1.3.0 -> 1.9.1 (*)
+     +--- androidx.annotation:annotation-experimental:1.3.1 -> 1.4.1 (*)
+     +--- androidx.fragment:fragment:1.5.1 -> 1.8.5 (*)
+     +--- androidx.lifecycle:lifecycle-common:2.5.1 -> 2.8.7 (*)
+     +--- androidx.lifecycle:lifecycle-viewmodel:2.5.1 -> 2.8.7 (*)
+     +--- androidx.lifecycle:lifecycle-viewmodel-savedstate:2.5.1 -> 2.8.7 (*)
+     +--- androidx.savedstate:savedstate:1.2.0 -> 1.2.1 (*)
+     +--- javax.inject:javax.inject:1
+     \--- org.jetbrains.kotlin:kotlin-stdlib:2.0.0-Beta5 -> 2.0.21 (*)

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr21501-46b2f07
	Commit	46b2f07
	Direct Download	wordpress-prototype-build-pr21501-46b2f07.apk

Note: Google Login is not supported on these builds.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr21501-46b2f07
	Commit	46b2f07
	Direct Download	jetpack-prototype-build-pr21501-46b2f07.apk

Note: Google Login is not supported on these builds.

[nbradbury]