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

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

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)

... (truncated)

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

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

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

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)

... (truncated)

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

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

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

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)

... (truncated)

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view