Skip to content

Bump google-dagger from 2.57.2 to 2.59 #322

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
Closed
dependabot wants to merge 1 commit into from
Closed

Bump google-dagger from 2.57.2 to 2.59 #322

dependabot wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 29, 2026 •
edited
Loading

Bumps google-dagger from 2.57.2 to 2.59.
Updates com.google.dagger:dagger-compiler from 2.57.2 to 2.59

Release notes

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

Dagger 2.59

Breaking changes:

This release adds support for AGP 9, which means 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).

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)
Commits
  • bd412c6 2.59 release
  • 507a226 Fix upload_to_sonatype script.
  • 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
  • 6eb10d1 Bump minimum emulator to API Level 23.
  • beb47ae Update Dagger yml and README with new latest version number.
  • dba58d2 Upgrade Bazel version to 8.5.0
  • a54bac9 Add a test to check on framework requests on delegate chains.
  • be5dbc9 Internal change
  • 925e514 Internal changes
  • ad02c11 Internal Changes
  • Additional commits viewable in compare view

Updates com.google.dagger:hilt-compiler from 2.57.2 to 2.59

Release notes

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

Dagger 2.59

Breaking changes:

This release adds support for AGP 9, which means 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).

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)
Commits
  • bd412c6 2.59 release
  • 507a226 Fix upload_to_sonatype script.
  • 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
  • 6eb10d1 Bump minimum emulator to API Level 23.
  • beb47ae Update Dagger yml and README with new latest version number.
  • dba58d2 Upgrade Bazel version to 8.5.0
  • a54bac9 Add a test to check on framework requests on delegate chains.
  • be5dbc9 Internal change
  • 925e514 Internal changes
  • ad02c11 Internal Changes
  • Additional commits viewable in compare view

Updates com.google.dagger:hilt-android from 2.57.2 to 2.59

Release notes

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

Dagger 2.59

Breaking changes:

This release adds support for AGP 9, which means 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).

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)
Commits
  • bd412c6 2.59 release
  • 507a226 Fix upload_to_sonatype script.
  • 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
  • 6eb10d1 Bump minimum emulator to API Level 23.
  • beb47ae Update Dagger yml and README with new latest version number.
  • dba58d2 Upgrade Bazel version to 8.5.0
  • a54bac9 Add a test to check on framework requests on delegate chains.
  • be5dbc9 Internal change
  • 925e514 Internal changes
  • ad02c11 Internal Changes
  • Additional commits viewable in compare view

Updates com.google.dagger:hilt-android-gradle-plugin from 2.57.2 to 2.59

Release notes

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

Dagger 2.59

Breaking changes:

This release adds support for AGP 9, which means 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).

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)
Commits
  • bd412c6 2.59 release
  • 507a226 Fix upload_to_sonatype script.
  • 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
  • 6eb10d1 Bump minimum emulator to API Level 23.
  • beb47ae Update Dagger yml and README with new latest version number.
  • dba58d2 Upgrade Bazel version to 8.5.0
  • a54bac9 Add a test to check on framework requests on delegate chains.
  • be5dbc9 Internal change
  • 925e514 Internal changes
  • ad02c11 Internal Changes
  • Additional commits viewable in compare view

Updates com.google.dagger.hilt.android from 2.57.2 to 2.59

Release notes

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

Dagger 2.59

Breaking changes:

This release adds support for AGP 9, which means 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).

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)
Commits
  • bd412c6 2.59 release
  • 507a226 Fix upload_to_sonatype script.
  • 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
  • 6eb10d1 Bump minimum emulator to API Level 23.
  • beb47ae Update Dagger yml and README with new latest version number.
  • dba58d2 Upgrade Bazel version to 8.5.0
  • a54bac9 Add a test to check on framework requests on delegate chains.
  • be5dbc9 Internal change
  • 925e514 Internal changes
  • ad02c11 Internal Changes
  • 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 <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)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 29, 2026
@dependabot dependabot bot force-pushed the dependabot/gradle/google-dagger-2.59 branch from 3d3c408 to 00ec412 Compare February 1, 2026 11:47
@dependabot
Bump google-dagger from 2.57.2 to 2.59
b91cbe2 
Bumps `google-dagger` from 2.57.2 to 2.59.

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

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

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

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

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

---
updated-dependencies:
- dependency-name: com.google.dagger:dagger-compiler
  dependency-version: '2.59'
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.google.dagger:hilt-compiler
  dependency-version: '2.59'
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.google.dagger:hilt-android
  dependency-version: '2.59'
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.google.dagger:hilt-android-gradle-plugin
  dependency-version: '2.59'
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.google.dagger.hilt.android
  dependency-version: '2.59'
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/gradle/google-dagger-2.59 branch from 00ec412 to b91cbe2 Compare February 1, 2026 16:14
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 1, 2026

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 2, 2026

Looks like these dependencies are up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Feb 2, 2026
@dependabot dependabot bot deleted the dependabot/gradle/google-dagger-2.59 branch February 2, 2026 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants