Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump the hilt group across 1 directory with 6 updates #1479

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Bump the hilt group across 1 directory with 6 updates #1479

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 13, 2025 •
edited
Loading

Bumps the hilt group with 6 updates in the / directory:

Package From To
com.google.dagger:dagger 2.52 2.55
com.google.dagger:dagger-compiler 2.52 2.55
com.google.dagger:hilt-android 2.52 2.55
com.google.dagger:hilt-android-compiler 2.52 2.55
com.google.dagger:hilt-core 2.52 2.55
com.google.dagger.hilt.android 2.52 2.55

Updates com.google.dagger:dagger from 2.52 to 2.55

Release notes

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

Dagger 2.55

Notable/breaking changes

  • Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.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 writeResource call. (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 uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() 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 @Component that 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:

@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?
}

... (truncated)

Commits
  • 14ad560 2.55 release
  • 7ca9977 Add binary compatibility validator to the Gradle projects
  • 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
  • 8b4f9b6 Add maven publish plugin to Gradle projects.
  • 9daa0ae Wire resource configuration while keeping the Bazel project structure.
  • 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
  • 0927b9a Add flag to control LegacyBindingGraphFactory usage.
  • 1620e92 Add Github CI step and action for building with Gradle
  • c43783a Initial setup of Gradle as a build system for Dagger
  • 98a0275 Fix LazyClassKey proguard file issues.
  • Additional commits viewable in compare view

Updates com.google.dagger:dagger-compiler from 2.52 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 anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.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 writeResource call. (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 uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() 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 @Component that 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:

@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?
}

... (truncated)

Commits
  • 14ad560 2.55 release
  • 7ca9977 Add binary compatibility validator to the Gradle projects
  • 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
  • 8b4f9b6 Add maven publish plugin to Gradle projects.
  • 9daa0ae Wire resource configuration while keeping the Bazel project structure.
  • 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
  • 0927b9a Add flag to control LegacyBindingGraphFactory usage.
  • 1620e92 Add Github CI step and action for building with Gradle
  • c43783a Initial setup of Gradle as a build system for Dagger
  • 98a0275 Fix LazyClassKey proguard file issues.
  • Additional commits viewable in compare view

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

Release notes

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

Dagger 2.55

Notable/breaking changes

  • Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.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 writeResource call. (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 uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() 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 @Component that 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:

@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?
}

... (truncated)

Commits
  • 14ad560 2.55 release
  • 7ca9977 Add binary compatibility validator to the Gradle projects
  • 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
  • 8b4f9b6 Add maven publish plugin to Gradle projects.
  • 9daa0ae Wire resource configuration while keeping the Bazel project structure.
  • 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
  • 0927b9a Add flag to control LegacyBindingGraphFactory usage.
  • 1620e92 Add Github CI step and action for building with Gradle
  • c43783a Initial setup of Gradle as a build system for Dagger
  • 98a0275 Fix LazyClassKey proguard file issues.
  • Additional commits viewable in compare view

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

Release notes

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

Dagger 2.55

Notable/breaking changes

  • Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.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 writeResource call. (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 uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() 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 @Component that 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:

@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?
}

... (truncated)

Commits
  • 14ad560 2.55 release
  • 7ca9977 Add binary compatibility validator to the Gradle projects
  • 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
  • 8b4f9b6 Add maven publish plugin to Gradle projects.
  • 9daa0ae Wire resource configuration while keeping the Bazel project structure.
  • 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
  • 0927b9a Add flag to control LegacyBindingGraphFactory usage.
  • 1620e92 Add Github CI step and action for building with Gradle
  • c43783a Initial setup of Gradle as a build system for Dagger
  • 98a0275 Fix LazyClassKey proguard file issues.
  • Additional commits viewable in compare view

Updates com.google.dagger:hilt-core from 2.52 to 2.55

Release notes

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

Dagger 2.55

Notable/breaking changes

  • Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.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 writeResource call. (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 uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() 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 @Component that 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:

@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?
}

... (truncated)

Commits
  • 14ad560 2.55 release
  • 7ca9977 Add binary compatibility validator to the Gradle projects
  • 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
  • 8b4f9b6 Add maven publish plugin to Gradle projects.
  • 9daa0ae Wire resource configuration while keeping the Bazel project structure.
  • 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
  • 0927b9a Add flag to control LegacyBindingGraphFactory usage.
  • 1620e92 Add Github CI step and action for building with Gradle
  • c43783a Initial setup of Gradle as a build system for Dagger
  • 98a0275 Fix LazyClassKey proguard file issues.
  • Additional commits viewable in compare view

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

Release notes

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

Dagger 2.55

Notable/breaking changes

  • Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.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 writeResource call. (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 uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() 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 @Component that 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:

@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?
}

... (truncated)

Commits
  • 14ad560 2.55 release
  • 7ca9977 Add binary compatibility validator to the Gradle projects
  • 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
  • 8b4f9b6 Add maven publish plugin to Gradle projects.
  • 9daa0ae Wire resource configuration while keeping the Bazel project structure.
  • 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
  • 0927b9a Add flag to control LegacyBindingGraphFactory usage.
  • 1620e92 Add Github CI step and action for building with Gradle
  • c43783a Initial setup of Gradle as a build system for Dagger
  • 98a0275 Fix LazyClassKey proguard file issues.
  • Additional commits viewable in compare view

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

Release notes

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

Dagger 2.55

Notable/breaking changes

  • Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.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 writeResource call. (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 uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() 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 @Component that 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:

@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?
}

... (truncated)

Commits
  • 14ad560 2.55 release
  • 7ca9977 Add binary compatibility validator to the Gradle projects
  • 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
  • 8b4f9b6 Add maven publish plugin to Gradle projects.
  • 9daa0ae Wire resource configuration while keeping the Bazel project structure.
  • 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
  • 0927b9a Add flag to control LegacyBindingGraphFactory usage.
  • 1620e92 Add Github CI step and action for building with Gradle
  • c43783a Initial setup of Gradle as a build system for Dagger
  • 98a0275 Fix LazyClassKey proguard file issues.
  • Additional commits viewable in compare view

Updates com.google.dagger:hilt-core from 2.52 to 2.55

Release notes

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

Dagger 2.55

Notable/breaking changes

  • Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.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 writeResource call. (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 uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() 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 @Component that 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:

@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?
}

... (truncated)

Commits
  • 14ad560 2.55 release
  • 7ca9977 Add binary compatibility validator to the Gradle projects
  • 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
  • 8b4f9b6 Add maven publish plugin to Gradle projects.
  • 9daa0ae Wire resource configuration while keeping the Bazel project structure.
  • 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
  • 0927b9a Add flag to control LegacyBindingGraphFactory usage.
  • 1620e92 Add Github CI step and action for building with Gradle
  • c43783a Initial setup of Gradle as a build system for Dagger
  • 98a0275 Fix LazyClassKey proguard file issues.
  • Additional commits viewable in compare view

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

Release notes

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

Dagger 2.55

Notable/breaking changes

  • Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.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 writeResource call. (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 uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() 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 @Component that 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:

@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?
}

... (truncated)

Commits
  • 14ad560 2.55 release
  • 7ca9977 Add binary compatibility validator to the Gradle projects
  • 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
  • 8b4f9b6 Add maven publish plugin to Gradle projects.
  • 9daa0ae Wire resource configuration while keeping the Bazel project structure.
  • 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
  • 0927b9a Add flag to control LegacyBindingGraphFactory usage.
  • 1620e92 Add Github CI step and action for building with Gradle
  • c43783a Initial setup of Gradle as a build system for Dagger
  • 98a0275 Fix 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 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

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Jan 13, 2025
@dependabot dependabot bot requested a review from jeubank12 January 13, 2025 07:06
@dependabot dependabot bot mentioned this pull request Jan 13, 2025
Closed
@dependabot dependabot bot force-pushed the dependabot/gradle/hilt-e1cbcaa113 branch 2 times, most recently from f3daef4 to 6364267 Compare January 20, 2025 07:43
@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 27, 2025

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

@dependabot dependabot bot force-pushed the dependabot/gradle/hilt-e1cbcaa113 branch from 6364267 to 32100b1 Compare February 3, 2025 07:34
@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 17, 2025

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

@dependabot
Bump the hilt group across 1 directory with 6 updates
ed2457c 
Bumps the hilt group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [com.google.dagger:dagger](https://github.com/google/dagger) | `2.52` | `2.55` |
| [com.google.dagger:dagger-compiler](https://github.com/google/dagger) | `2.52` | `2.55` |
| [com.google.dagger:hilt-android](https://github.com/google/dagger) | `2.52` | `2.55` |
| [com.google.dagger:hilt-android-compiler](https://github.com/google/dagger) | `2.52` | `2.55` |
| [com.google.dagger:hilt-core](https://github.com/google/dagger) | `2.52` | `2.55` |
| [com.google.dagger.hilt.android](https://github.com/google/dagger) | `2.52` | `2.55` |



Updates `com.google.dagger:dagger` from 2.52 to 2.55
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.52...dagger-2.55)

Updates `com.google.dagger:dagger-compiler` from 2.52 to 2.55
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.52...dagger-2.55)

Updates `com.google.dagger:hilt-android` from 2.52 to 2.55
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.52...dagger-2.55)

Updates `com.google.dagger:hilt-android-compiler` from 2.52 to 2.55
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.52...dagger-2.55)

Updates `com.google.dagger:hilt-core` from 2.52 to 2.55
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.52...dagger-2.55)

Updates `com.google.dagger.hilt.android` from 2.52 to 2.55
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.52...dagger-2.55)

Updates `com.google.dagger:hilt-android-compiler` from 2.52 to 2.55
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.52...dagger-2.55)

Updates `com.google.dagger:hilt-core` from 2.52 to 2.55
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.52...dagger-2.55)

Updates `com.google.dagger.hilt.android` from 2.52 to 2.55
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.52...dagger-2.55)

---
updated-dependencies:
- dependency-name: com.google.dagger:dagger
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: hilt
- dependency-name: com.google.dagger:dagger-compiler
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: hilt
- dependency-name: com.google.dagger:hilt-android
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: hilt
- dependency-name: com.google.dagger:hilt-android-compiler
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: hilt
- dependency-name: com.google.dagger:hilt-core
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: hilt
- dependency-name: com.google.dagger.hilt.android
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: hilt
- dependency-name: com.google.dagger:hilt-android-compiler
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: hilt
- dependency-name: com.google.dagger:hilt-core
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: hilt
- dependency-name: com.google.dagger.hilt.android
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: hilt
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/gradle/hilt-e1cbcaa113 branch from 32100b1 to ed2457c Compare February 24, 2025 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jeubank12 jeubank12 Awaiting requested review from jeubank12

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file java Pull requests that update Java code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants