Skip to content

chore(gradle): bump dagger from 2.56.2 to 2.59.1#7656

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/gradle/dagger-2.59.1
Closed

chore(gradle): bump dagger from 2.56.2 to 2.59.1#7656
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/gradle/dagger-2.59.1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Feb 9, 2026

Bumps dagger from 2.56.2 to 2.59.1.
Updates com.google.dagger:dagger from 2.56.2 to 2.59.1

Release notes

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

Dagger 2.59.1

Bug fixes:

  • Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
  • Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

  • Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

  • Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
  • The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

  • Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
  • Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
  • Fixes #4982:
    • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
    • Added error for binding elements names that are Java keywords. (38071c5ae)
    • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Dagger 2.57.2

Bug fixes

  • Fixed #4847: Fixed an issue with the Hilt Gradle Plugin registered transforms on projects using Gradle 9.0.0 (ea570e7)
  • Fixes #4898: Fixed an issue with backwards compatibility handling for libraries that export Hilt roots. (85c470ca4)
  • Fixes #4937: Fixed the incorrectly declared version of the Kotlin stdlib dependency in the Hilt Gradle Plugin. (deefd9a2d)
  • Updated ASM dependency to 9.8 (365bc499d)

Dagger 2.57.1

Bug fixes

  • Fixes #4734: Updated Hilt's Gradle Plugin detection of AGP to maximize compatibility and avoid the confusing 'The Hilt Android Gradle plugin can only be applied to an Android project.' error when the plugin is on an Android project. (20adecbf5)
  • Fixes #4848: Set coreLibrariesVersion for the Kotlin compilation of the Hilt Gradle Plugin to further improve backwards compatibility. (00c7fc203)
  • Fixes #4848: Use api / language versions for the Kotlin compilation of the Hilt Gradle Plugin to not force projects to update to Kotlin 2.2.0, the current version used by the plugin. (58e499243)

... (truncated)

Commits
  • 45105f9 2.59.1 release
  • 62b5423 Internal changes
  • 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
  • ed252cd Upgrading protobuf-java version to 4.32.1
  • 9354ef3 Use java_single_jar instead of a java_binary to roll up deps
  • f9deeef Internal changes
  • 141e594 Update minimum required AGP version to 9.0.0.
  • d060e95 Internal Changes
  • e679bd9 Update Bazel module dependencies and remove unnecessary :aar suffixes.
  • 7a370d9 Fix emulator tests.
  • Additional commits viewable in compare view

Updates com.google.dagger:dagger-compiler from 2.56.2 to 2.59.1

Release notes

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

Dagger 2.59.1

Bug fixes:

  • Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
  • Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

  • Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

  • Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
  • The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

  • Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
  • Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
  • Fixes #4982:
    • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
    • Added error for binding elements names that are Java keywords. (38071c5ae)
    • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Dagger 2.57.2

Bug fixes

  • Fixed #4847: Fixed an issue with the Hilt Gradle Plugin registered transforms on projects using Gradle 9.0.0 (ea570e7)
  • Fixes #4898: Fixed an issue with backwards compatibility handling for libraries that export Hilt roots. (85c470ca4)
  • Fixes #4937: Fixed the incorrectly declared version of the Kotlin stdlib dependency in the Hilt Gradle Plugin. (deefd9a2d)
  • Updated ASM dependency to 9.8 (365bc499d)

Dagger 2.57.1

Bug fixes

  • Fixes #4734: Updated Hilt's Gradle Plugin detection of AGP to maximize compatibility and avoid the confusing 'The Hilt Android Gradle plugin can only be applied to an Android project.' error when the plugin is on an Android project. (20adecbf5)
  • Fixes #4848: Set coreLibrariesVersion for the Kotlin compilation of the Hilt Gradle Plugin to further improve backwards compatibility. (00c7fc203)
  • Fixes #4848: Use api / language versions for the Kotlin compilation of the Hilt Gradle Plugin to not force projects to update to Kotlin 2.2.0, the current version used by the plugin. (58e499243)

... (truncated)

Commits
  • 45105f9 2.59.1 release
  • 62b5423 Internal changes
  • 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
  • ed252cd Upgrading protobuf-java version to 4.32.1
  • 9354ef3 Use java_single_jar instead of a java_binary to roll up deps
  • f9deeef Internal changes
  • 141e594 Update minimum required AGP version to 9.0.0.
  • d060e95 Internal Changes
  • e679bd9 Update Bazel module dependencies and remove unnecessary :aar suffixes.
  • 7a370d9 Fix emulator tests.
  • 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 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)

Bumps `dagger` from 2.56.2 to 2.59.1.

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

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

---
updated-dependencies:
- dependency-name: com.google.dagger:dagger
  dependency-version: 2.59.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.google.dagger:dagger-compiler
  dependency-version: 2.59.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 9, 2026

No docs changes detected for 9d2a582

@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Feb 23, 2026

Superseded by #7707.

@dependabot dependabot Bot closed this Feb 23, 2026
@dependabot dependabot Bot deleted the dependabot/gradle/dagger-2.59.1 branch February 23, 2026 02:09
@github-actions github-actions Bot locked and limited conversation to collaborators Feb 23, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants