Bump com.google.dagger:dagger-compiler from 2.48.1 to 2.52

dependabot[bot] commented 2 months ago

Bumps com.google.dagger:dagger-compiler from 2.48.1 to 2.52.

Release notes

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

Dagger 2.52

Notes: Dagger KSP now requires at least KSP 1.9.24-1.0.20.

Bug fixes

Fixed #4302: Suppress deprecation warnings in generated code. (f41033cc4)

Fixed #4323: Added rules to stop LazyClassKey referenced classes being merged with R8 (81512af9e).

Fixed #4345: Fixes intersection type bounds order in generated factories when using KSP (aosp/3164197).

Fixed #4352: Fixes an issue where the parameter name "instance" could conflict with fields of the same name in the component. (952c2504a)

Merged pull request #4305: Skip view injection when in edit mode for previews. (65b74f832)

Fixed an issue where base classes with a package private constructor would cause the generated code to fail (db25237df)

Add a jakarta.inject.Provider runtime dependency in preparation for supporting Jakarta Providers (a8581e0a6)

Dagger 2.51.1

New Dagger Features

Added BindingGraphPlugin#onProcessingRoundBegin for pre-processing initialization. (2a6a0b461)

Dagger bug fixes

Fixed #4181: Associate Dagger Android output with the generated Component, so that incremental builds with Ksp won’t fail. Fixed #4254: Support using scoped @LazyClassKey map bindings. Fixed #4262: Support referencing an array of annotations in a map key annotation.

Dagger 2.51

New Dagger Features

Added a @LazyClassKey annotation that supports using class names as a map key. Unlike the existing @ClassKey, the map generated by @LazyClassKey won’t eagerly load all of the classes for the keys. This can be useful in situations or environments where classloading can be expensive, such as on Android. For more information, see https://dagger.dev/dev-guide/multibindings

Potential breaking changes

Protected fields using @Inject are now banned in Kotlin classes. This is because Kotlin protected fields are not accessible by code in the same package, unlike Java. This has been working up to this point because Dagger generates Java code, but that is unintentional and would break if Dagger switched to generate Kotlin code.(408431a3b)

New Hilt Features

Fixed #3197: Used the new @LazyClassKey Dagger feature to remove the keep rule for @HiltViewModel class names. This allows obfuscation of @HiltViewModel annotated ViewModel class names with R8. (0786d0af5)

Added @SkipTestInjection which can be used for skipping test injection in Hilt Android tests, which may be useful if building separate custom test infrastructure to inject the test class from another Hilt component. (c40811e71)

Dagger bug fixes

Improve Dagger MissingBinding error messages to give more information and be more consistent. (c8722386a)

Fixed #4201: Suppress warning for casting in Dagger generated code. (813ffced8)

Fixed #4203: Removes @Deprecated annotation causing warnings (3cbc94ad3)

Fixed #4199: Support member injections from type aliased superclass (662d82359)

Complete Ksp support for Dagger Android: Added a Ksp Processor for Dagger Android ProguardProcessor that was previously missed. The ProguardProcessor is a Dagger Android implementation detail that makes sure the AndroidInjector works correctly when shrinking tools obfuscate @ContributesAndroidInjector annotated injector class names. (e71de27a1)

Dagger 2.50

Dagger

Potential breaking changes

... (truncated)

Commits

0544328 2.52 release
3e0d349 Add more information to error message when @AggregatedDeps annotation is miss...
da92d19 Drop latest XProcessing jars into Dagger.
4dcf006 Add jarjar test libraries to the Allstar exemption file for binary artifacts.
31eec2a Update Bazel to use JDK 18.
5293ff5 Automated Code Change
d55d61c No public description
952c250 Fix an issue where the parameter name "instance" could conflict with fields o...
917c005 Internal changes
140e201 Completely remove dependency on https://github.com/google/bazel-common.
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 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)