Bump libraryVersion.dagger from 2.18 to 2.28.3
Bumps libraryVersion.dagger from 2.18 to 2.28.3.
Updates dagger from 2.18 to 2.28.3
Release notes
Sourced from dagger's releases.
Dagger 2.28.3
Bug fixes
Hilt
- Fix #1987: Fixes a bug in version 2.28.2 that occurs when a transitive dependency installs something into
ApplicationComponentand depends on a version of Hilt less than 2.28.2. (667a8e25)Dagger 2.28.2
What’s new
Hilt
The Hilt class
dagger.hilt.android.components.ApplicationComponentis being renamed todagger.hilt.components.SingletonComponent. This release adds the newSingletonComponentclass in preparation for this change without removing the existingApplicationComponent. This rename is part of a plan to address google/dagger#1908 to allow usage of Hilt in non-Android Gradle modules when installing into theSingletonComponent. Current users can begin switching to the newSingletonComponentname as of this release. A future release will removeApplicationComponent.Bug fixes
Hilt
- Fix #1980: Added missing FIELD target to @ActivityContext qualifier. (29e080f0)
- Fix #1909: Update Dagger's JavaPoet dependency to 1.13.0 containing fixes for Dagger & Hilt related to generating code with overriding methods without annotations. (c5de4ab0)
- Fix #1955: Fixes issue with bytecode transformation in Gradle plugin to allow @AndroidEntryPoint annotations to be used with abstract classes containing abstract methods. (884fee53)
- Fix #1947: Fixes issue with Hilt base classes that extend other Hilt base classes. (61c5c433)
- Fix #1917: Fixes Hilt example app for Gradle users on mac. (5b3a9661)
Dagger 2.28.1
What's New
New Bazel helper macros for using Dagger. See the updated README for instructions. There are also examples using these macros for Dagger and Hilt (9494f40f).
Bug fixes
Hilt
- Throws an error when @AndroidEntryPoint base classes use default params in Kotlin. This is a temporary stopgap while support is investigated (2d433491).
- Fixes #1910: Allow usage of an @AndroidEntryPoint class having an @AndroidEntryPoint base class when using the gradle plugin (3a31bf65).
- Fixes #1864: Add minSdkVersion to Lint AndroidManifest.xml. This fixes problems of incorrect added permissions to the manifest (85f285c2).
Dagger 2.28
What's New
Hilt Alpha Release
Hilt is a new library that layers on top of Dagger and provides a standard way to incorporate Dagger into an Android application. For more information, see https://dagger.dev/hilt.
Lint checks in Dagger for Kotlin (2597f5a6)
Dagger now includes Lint checks for Kotlin users. The checks cover the following cases:
- Using a redundant
field:site target in injected properties- Using a redundant
@JvmStaticin object modules.- Annotating companion objects with
@Module(@Moduleshould just be on the enclosing class)These checks are included by default for users of
dagger-androidandhilt-android. For Kotlin only projects the checks are available in a new artifact,com.google.dagger:dagger-lint:<version>and can be applied via thelintChecksconfiguration in Gradle:
Commits
38acce72.28.3 release667a8e2Add backwards compatibility with ApplicationComponent for libraries using pre...09d60beAdd artifact tests to javatests/artifacts29e080fAdd FIELD annotation target to @ActivityContext qualifier.c8a737fpedantic update to commentf14d319Add SingletonComponent and temporarily map the old ApplicationComponent to that.f3ff00aInternal refactorc5de4abUpdate Dagger's Bazel Common dependency that contains the JavaPoet 1.13.0 upd...62d1e49Internal cleanup884fee5Ignore abstract methods when transforming @AndroidEntryPoint-annotated classes.- Additional commits viewable in compare view
Updates dagger-compiler from 2.18 to 2.28.3
Release notes
Sourced from dagger-compiler's releases.
Dagger 2.28.3
Bug fixes
Hilt
- Fix #1987: Fixes a bug in version 2.28.2 that occurs when a transitive dependency installs something into
ApplicationComponentand depends on a version of Hilt less than 2.28.2. (667a8e25)Dagger 2.28.2
What’s new
Hilt
The Hilt class
dagger.hilt.android.components.ApplicationComponentis being renamed todagger.hilt.components.SingletonComponent. This release adds the newSingletonComponentclass in preparation for this change without removing the existingApplicationComponent. This rename is part of a plan to address google/dagger#1908 to allow usage of Hilt in non-Android Gradle modules when installing into theSingletonComponent. Current users can begin switching to the newSingletonComponentname as of this release. A future release will removeApplicationComponent.Bug fixes
Hilt
- Fix #1980: Added missing FIELD target to @ActivityContext qualifier. (29e080f0)
- Fix #1909: Update Dagger's JavaPoet dependency to 1.13.0 containing fixes for Dagger & Hilt related to generating code with overriding methods without annotations. (c5de4ab0)
- Fix #1955: Fixes issue with bytecode transformation in Gradle plugin to allow @AndroidEntryPoint annotations to be used with abstract classes containing abstract methods. (884fee53)
- Fix #1947: Fixes issue with Hilt base classes that extend other Hilt base classes. (61c5c433)
- Fix #1917: Fixes Hilt example app for Gradle users on mac. (5b3a9661)
Dagger 2.28.1
What's New
New Bazel helper macros for using Dagger. See the updated README for instructions. There are also examples using these macros for Dagger and Hilt (9494f40f).
Bug fixes
Hilt
- Throws an error when @AndroidEntryPoint base classes use default params in Kotlin. This is a temporary stopgap while support is investigated (2d433491).
- Fixes #1910: Allow usage of an @AndroidEntryPoint class having an @AndroidEntryPoint base class when using the gradle plugin (3a31bf65).
- Fixes #1864: Add minSdkVersion to Lint AndroidManifest.xml. This fixes problems of incorrect added permissions to the manifest (85f285c2).
Dagger 2.28
What's New
Hilt Alpha Release
Hilt is a new library that layers on top of Dagger and provides a standard way to incorporate Dagger into an Android application. For more information, see https://dagger.dev/hilt.
Lint checks in Dagger for Kotlin (2597f5a6)
Dagger now includes Lint checks for Kotlin users. The checks cover the following cases:
- Using a redundant
field:site target in injected properties- Using a redundant
@JvmStaticin object modules.- Annotating companion objects with
@Module(@Moduleshould just be on the enclosing class)These checks are included by default for users of
dagger-androidandhilt-android. For Kotlin only projects the checks are available in a new artifact,com.google.dagger:dagger-lint:<version>and can be applied via thelintChecksconfiguration in Gradle:
Commits
38acce72.28.3 release667a8e2Add backwards compatibility with ApplicationComponent for libraries using pre...09d60beAdd artifact tests to javatests/artifacts29e080fAdd FIELD annotation target to @ActivityContext qualifier.c8a737fpedantic update to commentf14d319Add SingletonComponent and temporarily map the old ApplicationComponent to that.f3ff00aInternal refactorc5de4abUpdate Dagger's Bazel Common dependency that contains the JavaPoet 1.13.0 upd...62d1e49Internal cleanup884fee5Ignore abstract methods when transforming @AndroidEntryPoint-annotated classes.- Additional commits viewable in compare view
Updates dagger-android-support from 2.18 to 2.28.3
Release notes
Sourced from dagger-android-support's releases.
Dagger 2.28.3
Bug fixes
Hilt
- Fix #1987: Fixes a bug in version 2.28.2 that occurs when a transitive dependency installs something into
ApplicationComponentand depends on a version of Hilt less than 2.28.2. (667a8e25)Dagger 2.28.2
What’s new
Hilt
The Hilt class
dagger.hilt.android.components.ApplicationComponentis being renamed todagger.hilt.components.SingletonComponent. This release adds the newSingletonComponentclass in preparation for this change without removing the existingApplicationComponent. This rename is part of a plan to address google/dagger#1908 to allow usage of Hilt in non-Android Gradle modules when installing into theSingletonComponent. Current users can begin switching to the newSingletonComponentname as of this release. A future release will removeApplicationComponent.Bug fixes
Hilt
- Fix #1980: Added missing FIELD target to @ActivityContext qualifier. (29e080f0)
- Fix #1909: Update Dagger's JavaPoet dependency to 1.13.0 containing fixes for Dagger & Hilt related to generating code with overriding methods without annotations. (c5de4ab0)
- Fix #1955: Fixes issue with bytecode transformation in Gradle plugin to allow @AndroidEntryPoint annotations to be used with abstract classes containing abstract methods. (884fee53)
- Fix #1947: Fixes issue with Hilt base classes that extend other Hilt base classes. (61c5c433)
- Fix #1917: Fixes Hilt example app for Gradle users on mac. (5b3a9661)
Dagger 2.28.1
What's New
New Bazel helper macros for using Dagger. See the updated README for instructions. There are also examples using these macros for Dagger and Hilt (9494f40f).
Bug fixes
Hilt
- Throws an error when @AndroidEntryPoint base classes use default params in Kotlin. This is a temporary stopgap while support is investigated (2d433491).
- Fixes #1910: Allow usage of an @AndroidEntryPoint class having an @AndroidEntryPoint base class when using the gradle plugin (3a31bf65).
- Fixes #1864: Add minSdkVersion to Lint AndroidManifest.xml. This fixes problems of incorrect added permissions to the manifest (85f285c2).
Dagger 2.28
What's New
Hilt Alpha Release
Hilt is a new library that layers on top of Dagger and provides a standard way to incorporate Dagger into an Android application. For more information, see https://dagger.dev/hilt.
Lint checks in Dagger for Kotlin (2597f5a6)
Dagger now includes Lint checks for Kotlin users. The checks cover the following cases:
- Using a redundant
field:site target in injected properties- Using a redundant
@JvmStaticin object modules.- Annotating companion objects with
@Module(@Moduleshould just be on the enclosing class)These checks are included by default for users of
dagger-androidandhilt-android. For Kotlin only projects the checks are available in a new artifact,com.google.dagger:dagger-lint:<version>and can be applied via thelintChecksconfiguration in Gradle:
Commits
38acce72.28.3 release667a8e2Add backwards compatibility with ApplicationComponent for libraries using pre...09d60beAdd artifact tests to javatests/artifacts29e080fAdd FIELD annotation target to @ActivityContext qualifier.c8a737fpedantic update to commentf14d319Add SingletonComponent and temporarily map the old ApplicationComponent to that.f3ff00aInternal refactorc5de4abUpdate Dagger's Bazel Common dependency that contains the JavaPoet 1.13.0 upd...62d1e49Internal cleanup884fee5Ignore abstract methods when transforming @AndroidEntryPoint-annotated classes.- Additional commits viewable in compare view
Updates dagger-android-processor from 2.18 to 2.28.3
Release notes
Sourced from dagger-android-processor's releases.
Dagger 2.28.3
Bug fixes
Hilt
- Fix #1987: Fixes a bug in version 2.28.2 that occurs when a transitive dependency installs something into
ApplicationComponentand depends on a version of Hilt less than 2.28.2. (667a8e25)Dagger 2.28.2
What’s new
Hilt
The Hilt class
dagger.hilt.android.components.ApplicationComponentis being renamed todagger.hilt.components.SingletonComponent. This release adds the newSingletonComponentclass in preparation for this change without removing the existingApplicationComponent. This rename is part of a plan to address google/dagger#1908 to allow usage of Hilt in non-Android Gradle modules when installing into theSingletonComponent. Current users can begin switching to the newSingletonComponentname as of this release. A future release will removeApplicationComponent.Bug fixes
Hilt
- Fix #1980: Added missing FIELD target to @ActivityContext qualifier. (29e080f0)
- Fix #1909: Update Dagger's JavaPoet dependency to 1.13.0 containing fixes for Dagger & Hilt related to generating code with overriding methods without annotations. (c5de4ab0)
- Fix #1955: Fixes issue with bytecode transformation in Gradle plugin to allow @AndroidEntryPoint annotations to be used with abstract classes containing abstract methods. (884fee53)
- Fix #1947: Fixes issue with Hilt base classes that extend other Hilt base classes. (61c5c433)
- Fix #1917: Fixes Hilt example app for Gradle users on mac. (5b3a9661)
Dagger 2.28.1
What's New
New Bazel helper macros for using Dagger. See the updated README for instructions. There are also examples using these macros for Dagger and Hilt (9494f40f).
Bug fixes
Hilt
- Throws an error when @AndroidEntryPoint base classes use default params in Kotlin. This is a temporary stopgap while support is investigated (2d433491).
- Fixes #1910: Allow usage of an @AndroidEntryPoint class having an @AndroidEntryPoint base class when using the gradle plugin (3a31bf65).
- Fixes #1864: Add minSdkVersion to Lint AndroidManifest.xml. This fixes problems of incorrect added permissions to the manifest (85f285c2).
Dagger 2.28
What's New
Hilt Alpha Release
Hilt is a new library that layers on top of Dagger and provides a standard way to incorporate Dagger into an Android application. For more information, see https://dagger.dev/hilt.
Lint checks in Dagger for Kotlin (2597f5a6)
Dagger now includes Lint checks for Kotlin users. The checks cover the following cases:
- Using a redundant
field:site target in injected properties- Using a redundant
@JvmStaticin object modules.- Annotating companion objects with
@Module(@Moduleshould just be on the enclosing class)These checks are included by default for users of
dagger-androidandhilt-android. For Kotlin only projects the checks are available in a new artifact,com.google.dagger:dagger-lint:<version>and can be applied via thelintChecksconfiguration in Gradle:
Commits
38acce72.28.3 release667a8e2Add backwards compatibility with ApplicationComponent for libraries using pre...09d60beAdd artifact tests to javatests/artifacts29e080fAdd FIELD annotation target to @ActivityContext qualifier.c8a737fpedantic update to commentf14d319Add SingletonComponent and temporarily map the old ApplicationComponent to that.f3ff00aInternal refactorc5de4abUpdate Dagger's Bazel Common dependency that contains the JavaPoet 1.13.0 upd...62d1e49Internal cleanup884fee5Ignore abstract methods when transforming @AndroidEntryPoint-annotated classes.- 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) -
@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language -
@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)