[Internal][Gradle] (deps): Bump com.google.dagger:dagger-compiler from 2.51.1 to 2.55 in /catalog by dependabot[bot] · Pull Request #4569 · material-components/material-components-android
Bumps com.google.dagger:dagger-compiler from 2.51.1 to 2.55.
Release notes
Sourced from com.google.dagger:dagger-compiler's releases.
Dagger 2.55
Notable/breaking changes
- Added support for injecting
jakarta.inject.Provider. This should be usable anywherejavax.inject.Provideris usable. Note that this technically comes with a breaking change to disallow providingjakarta.inject.Providertypes in the same way it is disallowed forjavax.inject.Provider. (caa7e178b)- Fixed a number of binding graph related issues. These fixes can be enabled with,
-Adagger.useBindingGraphFix=ENABLED, but due to this sometimes being a breaking change we’ve set the default behavior to “disabled” for now. We will flip the default to “enabled” in a future release, and eventually remove the flag altogether. Enabling this feature can fix a number of confusing error messages. See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix for more details.Bug fixes
- Fixed #4549: Fixed incremental processing for LazyClassKey proguard files by adding the originating element to the
writeResourcecall. (98a027541)Dagger 2.54
Bug fixes
- Fixed #4303: Upgrade Hilt Gradle Plugin to support KSP2 configuration. (76b581999)
- Fixed #4544: Removes private from InstanceHolder field to avoid unnecessary accessor method. (07d8f883f)
- Fixed #4533: Fixes path separator for Windows when creating LazyClassKey proguard file. (efa421a3f)
Notable changes
- In preparation for jakarta support, Dagger’s generated factories now include a
create()method that usesdagger.internal.Providerrather thanjavax.inject.Provider. For now, thejavax.inject.Providercreate()method is also kept for compatibility, but it will be removed in a future release. When that happens, libraries built with the newer version of Dagger may break downstream users of@Componentthat are built with an older version of Dagger. (d60729d20)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:
@Bindsmethods now requires explicit nullabilityNew:
@Bindsmethods must explicitly declare nullability (previously we tried to infer it from the parameter). This change aligns the nullability behavior of@Bindswith 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
@Bindsmethod/parameter. For example:@Module interface MyModule { - @Binds fun bindToNullableImpl(impl: FooImpl): Foo + @Binds fun bindToNullableImpl(impl: FooImpl?): Foo? }
... (truncated)
Commits
14ad5602.55 release7ca9977Add binary compatibility validator to the Gradle projects4cd83cbAdd documentation fordagger.useBindingGraphFixcompiler option.8b4f9b6Add maven publish plugin to Gradle projects.9daa0aeWire resource configuration while keeping the Bazel project structure.3418609Move JDK toolchain, Kotlin language and JVM target configuration to conventio...0927b9aAdd flag to control LegacyBindingGraphFactory usage.1620e92Add Github CI step and action for building with Gradlec43783aInitial setup of Gradle as a build system for Dagger98a0275Fix LazyClassKey proguard file issues.- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.