Insulator
Insulator copied to clipboard
chore: Bump dagger_version from 2.41 to 2.44
Bumps dagger_version from 2.41 to 2.44.
Updates dagger from 2.41 to 2.44
Release notes
Sourced from dagger's releases.
Dagger 2.44
What’s new In Dagger
Potentially breaking changes
- Fixes #3531: Removed formatting from dagger.android generated source could be a breaking change for anyone relying on golden files for Dagger’s generated code. (d123efdf0)
Bug Fixes
- Fixes #3522: Avoids pre-validating the nearest enclosing type in the InjectProcessingStep. (1d74d1fd3)
What’s new in Hilt
Potentially breaking changes
- Added
ViewModelLifecycle. This can be injected in the ViewModelComponent and used to register listeners for whenViewModel#onCleared()is called. This change also includes a breaking change for anyone who implemented theActivityRetainedLifecycleinterface themselves. This should be rare though as this interface was not meant to be implemented by users. (55aa4c60a)Bug Fixes
- Fixes #3478: Fixes an issue in Hilt's Gradle Plugin not configuring the aggregating task correctly on a
com.android.testGradle module. (ea39850c7)Dagger 2.43.2
What’s New In Dagger
Bug Fixes
- Fixes #3495: Updates the XProcessing jars, which should again be compatible with java 8. (62b7f4592)
- Adds support reading metadata from Kotlin 1.8 by updating kotlin-metadata-jvm to 5.0. (353a50b1e)
- Fixes an issue where the Hilt Gradle Plugin artifact was being bloated with additional classes causing its size to be way bigger than its suppose to be. (8235bebe9)
Dagger 2.43.1
What’s New In Dagger
Bug Fixes
- Fixes #3480. Replace dependency on
javax.annotation:jsr250-api:1.0withjavax.annotation:javax.annotation-api:1.3.2. (e9dc377d1)- Fixes #3483: Add onPluginEnd to BindingGraphPlugin, which will be called after all BindingGraphPlugins have been visited (34452751e)
- Fixes #3476: Fix issue with Dagger generating mismatching parameter names in component inject functions. (90300d992)
Dagger 2.43
What’s New In Dagger
Potentially Breaking Changes
- Note: Dagger 2.43/2.43.1 require java 11 due to a change in Dagger's XProcessing dependency. However, this requirement has been recently reverted in XProcessing and Dagger 2.43.2 should support java 8 again (see [issue #3495](google/dagger#3495)).
Bug Fixes
- Fixes #3401 where Dagger generated mismatched parameter names in subcomponent factory method implementations when the original factory method is in a separate build unit from the component that implements it.
What’s New In Hilt
... (truncated)
Commits
4e9c5702.44 releasefdf1c46Migrate more tests to XProcessing testing APIs.2decc41Migrate more tests to XProcessing testing APIs.55aa4c6Add a ViewModelLifecycle binding to ViewModelComponentbc94a5aMigrate more tests to XProcessing testing APIs.1099dd4Rename SOURCE_7_TARGET_7 to JAVA_RELEASE_MIN85af407Migrate more tests to XProcessing testing APIs.e11fa81Migrate more tests to XProcessing testing APIs.a15f8dfMigrate more tests to XProcessing testing APIs.96e2b8aMigrate more tests to XProcessing testing APIs.- Additional commits viewable in compare view
Updates dagger-compiler from 2.41 to 2.44
Release notes
Sourced from dagger-compiler's releases.
Dagger 2.44
What’s new In Dagger
Potentially breaking changes
- Fixes #3531: Removed formatting from dagger.android generated source could be a breaking change for anyone relying on golden files for Dagger’s generated code. (d123efdf0)
Bug Fixes
- Fixes #3522: Avoids pre-validating the nearest enclosing type in the InjectProcessingStep. (1d74d1fd3)
What’s new in Hilt
Potentially breaking changes
- Added
ViewModelLifecycle. This can be injected in the ViewModelComponent and used to register listeners for whenViewModel#onCleared()is called. This change also includes a breaking change for anyone who implemented theActivityRetainedLifecycleinterface themselves. This should be rare though as this interface was not meant to be implemented by users. (55aa4c60a)Bug Fixes
- Fixes #3478: Fixes an issue in Hilt's Gradle Plugin not configuring the aggregating task correctly on a
com.android.testGradle module. (ea39850c7)Dagger 2.43.2
What’s New In Dagger
Bug Fixes
- Fixes #3495: Updates the XProcessing jars, which should again be compatible with java 8. (62b7f4592)
- Adds support reading metadata from Kotlin 1.8 by updating kotlin-metadata-jvm to 5.0. (353a50b1e)
- Fixes an issue where the Hilt Gradle Plugin artifact was being bloated with additional classes causing its size to be way bigger than its suppose to be. (8235bebe9)
Dagger 2.43.1
What’s New In Dagger
Bug Fixes
- Fixes #3480. Replace dependency on
javax.annotation:jsr250-api:1.0withjavax.annotation:javax.annotation-api:1.3.2. (e9dc377d1)- Fixes #3483: Add onPluginEnd to BindingGraphPlugin, which will be called after all BindingGraphPlugins have been visited (34452751e)
- Fixes #3476: Fix issue with Dagger generating mismatching parameter names in component inject functions. (90300d992)
Dagger 2.43
What’s New In Dagger
Potentially Breaking Changes
- Note: Dagger 2.43/2.43.1 require java 11 due to a change in Dagger's XProcessing dependency. However, this requirement has been recently reverted in XProcessing and Dagger 2.43.2 should support java 8 again (see [issue #3495](google/dagger#3495)).
Bug Fixes
- Fixes #3401 where Dagger generated mismatched parameter names in subcomponent factory method implementations when the original factory method is in a separate build unit from the component that implements it.
What’s New In Hilt
... (truncated)
Commits
4e9c5702.44 releasefdf1c46Migrate more tests to XProcessing testing APIs.2decc41Migrate more tests to XProcessing testing APIs.55aa4c6Add a ViewModelLifecycle binding to ViewModelComponentbc94a5aMigrate more tests to XProcessing testing APIs.1099dd4Rename SOURCE_7_TARGET_7 to JAVA_RELEASE_MIN85af407Migrate more tests to XProcessing testing APIs.e11fa81Migrate more tests to XProcessing testing APIs.a15f8dfMigrate more tests to XProcessing testing APIs.96e2b8aMigrate more tests to XProcessing testing APIs.- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)