Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)
Bug fixes
Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)
Dagger 2.49
Dagger
New features:
Fixed #4044: Add support for KSP with dagger.android (832717767).
Potential breaking changes:
Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract@Provides/@Binds methods (ed47d4b88).
Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:
Hilt now provides @ActivityRetainedSavedState SavedStateHandle from ActivityRetainedComponent (1cac33b).
Note: This feature relies on a somewhat experimental implementation in order to provide this binding lazily while also avoiding leaking the activity. The laziness is a requirement to not restrict activity injection and also to avoid bloating the saved state when unused. While we predict this should be safe to rely on, if issues are discovered with this implementation, it is possible that a future release may have to remove this binding.
Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)
Bug fixes
Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)
Dagger 2.49
Dagger
New features:
Fixed #4044: Add support for KSP with dagger.android (832717767).
Potential breaking changes:
Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract@Provides/@Binds methods (ed47d4b88).
Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:
Hilt now provides @ActivityRetainedSavedState SavedStateHandle from ActivityRetainedComponent (1cac33b).
Note: This feature relies on a somewhat experimental implementation in order to provide this binding lazily while also avoiding leaking the activity. The laziness is a requirement to not restrict activity injection and also to avoid bloating the saved state when unused. While we predict this should be safe to rely on, if issues are discovered with this implementation, it is possible that a future release may have to remove this binding.
Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)
Bug fixes
Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)
Dagger 2.49
Dagger
New features:
Fixed #4044: Add support for KSP with dagger.android (832717767).
Potential breaking changes:
Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract@Provides/@Binds methods (ed47d4b88).
Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:
Hilt now provides @ActivityRetainedSavedState SavedStateHandle from ActivityRetainedComponent (1cac33b).
Note: This feature relies on a somewhat experimental implementation in order to provide this binding lazily while also avoiding leaking the activity. The laziness is a requirement to not restrict activity injection and also to avoid bloating the saved state when unused. While we predict this should be safe to rely on, if issues are discovered with this implementation, it is possible that a future release may have to remove this binding.
Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)
Bug fixes
Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)
Dagger 2.49
Dagger
New features:
Fixed #4044: Add support for KSP with dagger.android (832717767).
Potential breaking changes:
Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract@Provides/@Binds methods (ed47d4b88).
Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:
Hilt now provides @ActivityRetainedSavedState SavedStateHandle from ActivityRetainedComponent (1cac33b).
Note: This feature relies on a somewhat experimental implementation in order to provide this binding lazily while also avoiding leaking the activity. The laziness is a requirement to not restrict activity injection and also to avoid bloating the saved state when unused. While we predict this should be safe to rely on, if issues are discovered with this implementation, it is possible that a future release may have to remove this binding.
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 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)
Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
Bumps
hilt
from 2.48.1 to 2.50. Updatescom.google.dagger:hilt-android
from 2.48.1 to 2.50Release notes
Sourced from com.google.dagger:hilt-android's releases.
... (truncated)
Commits
137995b
2.50 release8d01223
Fix error message for an@Binds @IntoSet
implementation with duplicate bind...be77d24
Dagger build performance optimizations.8372c63
Flip the default for explicitBindingConflictsWithInject to enabled.13d64c6
Internal changes5f8b76c
OptimizeInjectionSiteFactory#getInjectionSites()
.45af1ed
Increase timeout for emulator tests from 25min to 35min in CI.45d3b87
MakeminSdk
andtargetSdk
versions consistent across Gradle tests.f4b4519
Internal changeseb9a034
Configure Bazel and Gradle to avoid spurious flakes.Updates
com.google.dagger:hilt-android-compiler
from 2.48.1 to 2.50Release notes
Sourced from com.google.dagger:hilt-android-compiler's releases.
... (truncated)
Commits
137995b
2.50 release8d01223
Fix error message for an@Binds @IntoSet
implementation with duplicate bind...be77d24
Dagger build performance optimizations.8372c63
Flip the default for explicitBindingConflictsWithInject to enabled.13d64c6
Internal changes5f8b76c
OptimizeInjectionSiteFactory#getInjectionSites()
.45af1ed
Increase timeout for emulator tests from 25min to 35min in CI.45d3b87
MakeminSdk
andtargetSdk
versions consistent across Gradle tests.f4b4519
Internal changeseb9a034
Configure Bazel and Gradle to avoid spurious flakes.Updates
com.google.dagger:hilt-android-testing
from 2.48.1 to 2.50Release notes
Sourced from com.google.dagger:hilt-android-testing's releases.
... (truncated)
Commits
137995b
2.50 release8d01223
Fix error message for an@Binds @IntoSet
implementation with duplicate bind...be77d24
Dagger build performance optimizations.8372c63
Flip the default for explicitBindingConflictsWithInject to enabled.13d64c6
Internal changes5f8b76c
OptimizeInjectionSiteFactory#getInjectionSites()
.45af1ed
Increase timeout for emulator tests from 25min to 35min in CI.45d3b87
MakeminSdk
andtargetSdk
versions consistent across Gradle tests.f4b4519
Internal changeseb9a034
Configure Bazel and Gradle to avoid spurious flakes.Updates
com.google.dagger.hilt.android
from 2.48.1 to 2.50Release notes
Sourced from com.google.dagger.hilt.android's releases.
... (truncated)
Commits
137995b
2.50 release8d01223
Fix error message for an@Binds @IntoSet
implementation with duplicate bind...be77d24
Dagger build performance optimizations.8372c63
Flip the default for explicitBindingConflictsWithInject to enabled.13d64c6
Internal changes5f8b76c
OptimizeInjectionSiteFactory#getInjectionSites()
.45af1ed
Increase timeout for emulator tests from 25min to 35min in CI.45d3b87
MakeminSdk
andtargetSdk
versions consistent across Gradle tests.f4b4519
Internal changeseb9a034
Configure Bazel and Gradle to avoid spurious flakes.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