search

aritra-tech / Notify

📝 Notify is a simple note application build to demonstrate the use of clean MVVM Architecture with Jetpack Compose and Material-3 guidelines along with some Modern Android development tools.
MIT License
331 stars 65 forks source link

Bump com.google.dagger.hilt.android from 2.48.1 to 2.51 #373

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 8 months ago

Bumps com.google.dagger.hilt.android from 2.48.1 to 2.51.

Release notes

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

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

  • Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
  • Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)

Bug fixes

  • Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)

Dagger 2.49

Dagger

New features:

  • Fixed #4044: Add support for KSP with dagger.android (832717767).

Potential breaking changes:

  • Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract @Provides/@Binds methods (ed47d4b88).

    Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:

    MyComponent component =
    DaggerMyComponent.builder()
-        .moduleWithOnlyStaticOrAbstractMethods(new ModuleWithOnlyStaticOrAbstractMethods())
        .build();

    These setter methods were already no-ops (i.e. Dagger just ignored them), so removing it should not cause any functional changes.

... (truncated)

Commits
  • c6c0b8a 2.51 release
  • 0786d0a Allow obfuscating @​HiltViewModel annotated ViewModel name with r8.
  • c5075df Remove kitkat-specific test.
  • c40811e Add a SkipTestInjection annotation to disable injecting the test class. This ...
  • 02d62d6 Replace processingEnv.requireTypeElement() with `DaggerSuperficialValidatio...
  • c872238 Improve Dagger error messages to give more information and be more consistent.
  • 7ac1dcc Internal changes
  • 09e5ac2 Include proguard rules in dagger core artifact so that LazyClassKeyMap's stri...
  • 348bd75 Rename proguard_specs attribute for gen_maven_artifact to reflect how it will...
  • d7a55be Migrate usages of Truth8.assertThat to equivalent usages of `Truth.assertTh...
  • Additional commits viewable in compare view


Dependabot compatibility score

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)
dependabot[bot] commented 8 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.