Skip to content

Bump dagger from 2.28.3 to 2.29.1#58

Open
dependabot-preview[bot] wants to merge 1 commit intomasterfrom
dependabot/gradle/dagger-2.29.1
Open

Bump dagger from 2.28.3 to 2.29.1#58
dependabot-preview[bot] wants to merge 1 commit intomasterfrom
dependabot/gradle/dagger-2.29.1

Conversation

@dependabot-preview
Copy link
Copy Markdown
Contributor

Bumps dagger from 2.28.3 to 2.29.1.
Updates dagger from 2.28.3 to 2.29.1

Release notes

Sourced from dagger's releases.

Dagger 2.29.1

What’s New

Hilt

Hilt has two new artifacts hilt-core and hilt-compiler that allow Hilt to be used with pure Java/Kotlin libraries within an AndroidApplication (see issue #1908 for the full motivation/discussion).

The hilt-core artifact contains the core (non-Android) Hilt APIs. Note that this artifact is only meant to be used by pure Java/Kotlin libraries within an Android application. Hilt does not currently support non-Android applications or non-Android tests.

The hilt-compiler artifact is just a rename of hilt-android-compiler. The motivation here is to have a single compiler artifact that works with both Android and non-Android libraries. The hilt-android-compiler artifact will be deprecated in a future release, so please migrate to hilt-compiler.

The example below shows which artifacts to use in an Android vs pure Java/Kotlin library.

// Android library deps
dependencies {
  implementation "com.google.dagger:hilt-android:2.29-alpha"
  androidTestImplementation "com.google.dagger:hilt-android-testing:2.29-alpha"
  annotationProcessor "com.google.dagger:hilt-compiler:2.29-alpha" // or kapt
}
// Pure Java/Kotlin library deps
dependencies {
implementation "com.google.dagger:hilt-core:2.29-alpha"
annotationProcessor "com.google.dagger:hilt-compiler:2.29-alpha" // or kapt
}

Dagger:

A new Dagger compiler option was added to allow disabling transitive validation of component dependency, dagger.validateTransitiveComponentDependencies,. The default value for the flag is enabled (same as before). To disable it, add the following to your compiler options: -Adagger.validateTransitiveComponentDependencies=DISABLED. For a full motivation/discussion, see issue #970.

A new Dagger compiler option was added to fix an issue with map binding contributions that depend on subcomponent bindings, dagger.strictMultibindingValidation. The default value for the flag is disabled (same as before). However, we will be enabling this flag in a future release. To check if your application will be affected, you can enable the flag by adding the following to your compiler options: -Adagger.strictMultibindingValidation=ENABLED. See #2085 for details.

Potential breaking changes

  • Fix an issue where in some cases missing bindings may have been missed during validation. This issue also affects the binding graph that SPI plugins receive so this fix may cause changes where a previously incorrect binding graph was being supplied. (08193ad70)

Bug Fixes

  • Fix #1955, #2065: Hilt would incorrectly try to transform native methods on classes annotated with @AndroidEntryPoint. (2099bade9, 2099bad)
  • Fix #1918: Support BroadcastReceiver with @AndroidEntryPoint transform. (ede018b7a)
  • Fix #1997: Allow Hilt modules to have constructors with params as long as a no-arg constructor exists. (07a7fa979)
  • Fix #2042: Fix bug in OriginatingElementProcessor and ban @AndroidEntryPoint classes with type parameters. (bee2e9a51)
  • Fix #970: Add -Adagger.validateTransitiveComponentDependencies compiler option to prevent validating transitive component dependencies. (6deafc748)
  • Add -Adagger.strictMultibindingValidation compiler option to fix map binding contributions that depend on subcomponent bindings. (fb47e1179)
  • Fix issue with @Binds when the impl extends a generated type. (71509b841)
  • Add support for receiving a callback for when the activity retained component will no longer be used and destroyed. (6300d0277, 218df98db)
  • Throw when a race is detected adding a OnClearedListener. (7cf8b11d6)
  • Reduce constant pool usage by renaming private methods (4a3115780)
Commits
  • f3be0a9 2.29.1 release
  • 6e71d51 Update Hilt Gradle Plugin to recognize hilt-compiler artifact.
  • fb47e11 This is a rollforward with fixes.
  • 1ddc41f Internal change
  • fbedecc Internal change
  • e861c27 Fix redundant memoization for scoped bindings in fastInit.
  • b15fa61 [Hilt]: Add 'hilt-compiler' artifact to replace 'hilt-android-compiler'.
  • 01859b5 [Dagger]: Make everything use dagger.model.BindingGraph
  • bca0f9d Internal change
  • 37d537b Internal change
  • Additional commits viewable in compare view

Updates dagger-android-support from 2.28.3 to 2.29.1

Release notes

Sourced from dagger-android-support's releases.

Dagger 2.29.1

What’s New

Hilt

Hilt has two new artifacts hilt-core and hilt-compiler that allow Hilt to be used with pure Java/Kotlin libraries within an AndroidApplication (see issue #1908 for the full motivation/discussion).

The hilt-core artifact contains the core (non-Android) Hilt APIs. Note that this artifact is only meant to be used by pure Java/Kotlin libraries within an Android application. Hilt does not currently support non-Android applications or non-Android tests.

The hilt-compiler artifact is just a rename of hilt-android-compiler. The motivation here is to have a single compiler artifact that works with both Android and non-Android libraries. The hilt-android-compiler artifact will be deprecated in a future release, so please migrate to hilt-compiler.

The example below shows which artifacts to use in an Android vs pure Java/Kotlin library.

// Android library deps
dependencies {
  implementation "com.google.dagger:hilt-android:2.29-alpha"
  androidTestImplementation "com.google.dagger:hilt-android-testing:2.29-alpha"
  annotationProcessor "com.google.dagger:hilt-compiler:2.29-alpha" // or kapt
}
// Pure Java/Kotlin library deps
dependencies {
implementation "com.google.dagger:hilt-core:2.29-alpha"
annotationProcessor "com.google.dagger:hilt-compiler:2.29-alpha" // or kapt
}

Dagger:

A new Dagger compiler option was added to allow disabling transitive validation of component dependency, dagger.validateTransitiveComponentDependencies,. The default value for the flag is enabled (same as before). To disable it, add the following to your compiler options: -Adagger.validateTransitiveComponentDependencies=DISABLED. For a full motivation/discussion, see issue #970.

A new Dagger compiler option was added to fix an issue with map binding contributions that depend on subcomponent bindings, dagger.strictMultibindingValidation. The default value for the flag is disabled (same as before). However, we will be enabling this flag in a future release. To check if your application will be affected, you can enable the flag by adding the following to your compiler options: -Adagger.strictMultibindingValidation=ENABLED. See #2085 for details.

Potential breaking changes

  • Fix an issue where in some cases missing bindings may have been missed during validation. This issue also affects the binding graph that SPI plugins receive so this fix may cause changes where a previously incorrect binding graph was being supplied. (08193ad70)

Bug Fixes

  • Fix #1955, #2065: Hilt would incorrectly try to transform native methods on classes annotated with @AndroidEntryPoint. (2099bade9, 2099bad)
  • Fix #1918: Support BroadcastReceiver with @AndroidEntryPoint transform. (ede018b7a)
  • Fix #1997: Allow Hilt modules to have constructors with params as long as a no-arg constructor exists. (07a7fa979)
  • Fix #2042: Fix bug in OriginatingElementProcessor and ban @AndroidEntryPoint classes with type parameters. (bee2e9a51)
  • Fix #970: Add -Adagger.validateTransitiveComponentDependencies compiler option to prevent validating transitive component dependencies. (6deafc748)
  • Add -Adagger.strictMultibindingValidation compiler option to fix map binding contributions that depend on subcomponent bindings. (fb47e1179)
  • Fix issue with @Binds when the impl extends a generated type. (71509b841)
  • Add support for receiving a callback for when the activity retained component will no longer be used and destroyed. (6300d0277, 218df98db)
  • Throw when a race is detected adding a OnClearedListener. (7cf8b11d6)
  • Reduce constant pool usage by renaming private methods (4a3115780)
Commits
  • f3be0a9 2.29.1 release
  • 6e71d51 Update Hilt Gradle Plugin to recognize hilt-compiler artifact.
  • fb47e11 This is a rollforward with fixes.
  • 1ddc41f Internal change
  • fbedecc Internal change
  • e861c27 Fix redundant memoization for scoped bindings in fastInit.
  • b15fa61 [Hilt]: Add 'hilt-compiler' artifact to replace 'hilt-android-compiler'.
  • 01859b5 [Dagger]: Make everything use dagger.model.BindingGraph
  • bca0f9d Internal change
  • 37d537b Internal change
  • Additional commits viewable in compare view

Updates dagger-compiler from 2.28.3 to 2.29.1

Release notes

Sourced from dagger-compiler's releases.

Dagger 2.29.1

What’s New

Hilt

Hilt has two new artifacts hilt-core and hilt-compiler that allow Hilt to be used with pure Java/Kotlin libraries within an AndroidApplication (see issue #1908 for the full motivation/discussion).

The hilt-core artifact contains the core (non-Android) Hilt APIs. Note that this artifact is only meant to be used by pure Java/Kotlin libraries within an Android application. Hilt does not currently support non-Android applications or non-Android tests.

The hilt-compiler artifact is just a rename of hilt-android-compiler. The motivation here is to have a single compiler artifact that works with both Android and non-Android libraries. The hilt-android-compiler artifact will be deprecated in a future release, so please migrate to hilt-compiler.

The example below shows which artifacts to use in an Android vs pure Java/Kotlin library.

// Android library deps
dependencies {
  implementation "com.google.dagger:hilt-android:2.29-alpha"
  androidTestImplementation "com.google.dagger:hilt-android-testing:2.29-alpha"
  annotationProcessor "com.google.dagger:hilt-compiler:2.29-alpha" // or kapt
}
// Pure Java/Kotlin library deps
dependencies {
implementation "com.google.dagger:hilt-core:2.29-alpha"
annotationProcessor "com.google.dagger:hilt-compiler:2.29-alpha" // or kapt
}

Dagger:

A new Dagger compiler option was added to allow disabling transitive validation of component dependency, dagger.validateTransitiveComponentDependencies,. The default value for the flag is enabled (same as before). To disable it, add the following to your compiler options: -Adagger.validateTransitiveComponentDependencies=DISABLED. For a full motivation/discussion, see issue #970.

A new Dagger compiler option was added to fix an issue with map binding contributions that depend on subcomponent bindings, dagger.strictMultibindingValidation. The default value for the flag is disabled (same as before). However, we will be enabling this flag in a future release. To check if your application will be affected, you can enable the flag by adding the following to your compiler options: -Adagger.strictMultibindingValidation=ENABLED. See #2085 for details.

Potential breaking changes

  • Fix an issue where in some cases missing bindings may have been missed during validation. This issue also affects the binding graph that SPI plugins receive so this fix may cause changes where a previously incorrect binding graph was being supplied. (08193ad70)

Bug Fixes

  • Fix #1955, #2065: Hilt would incorrectly try to transform native methods on classes annotated with @AndroidEntryPoint. (2099bade9, 2099bad)
  • Fix #1918: Support BroadcastReceiver with @AndroidEntryPoint transform. (ede018b7a)
  • Fix #1997: Allow Hilt modules to have constructors with params as long as a no-arg constructor exists. (07a7fa979)
  • Fix #2042: Fix bug in OriginatingElementProcessor and ban @AndroidEntryPoint classes with type parameters. (bee2e9a51)
  • Fix #970: Add -Adagger.validateTransitiveComponentDependencies compiler option to prevent validating transitive component dependencies. (6deafc748)
  • Add -Adagger.strictMultibindingValidation compiler option to fix map binding contributions that depend on subcomponent bindings. (fb47e1179)
  • Fix issue with @Binds when the impl extends a generated type. (71509b841)
  • Add support for receiving a callback for when the activity retained component will no longer be used and destroyed. (6300d0277, 218df98db)
  • Throw when a race is detected adding a OnClearedListener. (7cf8b11d6)
  • Reduce constant pool usage by renaming private methods (4a3115780)
Commits
  • f3be0a9 2.29.1 release
  • 6e71d51 Update Hilt Gradle Plugin to recognize hilt-compiler artifact.
  • fb47e11 This is a rollforward with fixes.
  • 1ddc41f Internal change
  • fbedecc Internal change
  • e861c27 Fix redundant memoization for scoped bindings in fastInit.
  • b15fa61 [Hilt]: Add 'hilt-compiler' artifact to replace 'hilt-android-compiler'.
  • 01859b5 [Dagger]: Make everything use dagger.model.BindingGraph
  • bca0f9d Internal change
  • 37d537b Internal change
  • Additional commits viewable in compare view

Updates dagger-android-processor from 2.28.3 to 2.29.1

Release notes

Sourced from dagger-android-processor's releases.

Dagger 2.29.1

What’s New

Hilt

Hilt has two new artifacts hilt-core and hilt-compiler that allow Hilt to be used with pure Java/Kotlin libraries within an AndroidApplication (see issue #1908 for the full motivation/discussion).

The hilt-core artifact contains the core (non-Android) Hilt APIs. Note that this artifact is only meant to be used by pure Java/Kotlin libraries within an Android application. Hilt does not currently support non-Android applications or non-Android tests.

The hilt-compiler artifact is just a rename of hilt-android-compiler. The motivation here is to have a single compiler artifact that works with both Android and non-Android libraries. The hilt-android-compiler artifact will be deprecated in a future release, so please migrate to hilt-compiler.

The example below shows which artifacts to use in an Android vs pure Java/Kotlin library.

// Android library deps
dependencies {
  implementation "com.google.dagger:hilt-android:2.29-alpha"
  androidTestImplementation "com.google.dagger:hilt-android-testing:2.29-alpha"
  annotationProcessor "com.google.dagger:hilt-compiler:2.29-alpha" // or kapt
}
// Pure Java/Kotlin library deps
dependencies {
implementation "com.google.dagger:hilt-core:2.29-alpha"
annotationProcessor "com.google.dagger:hilt-compiler:2.29-alpha" // or kapt
}

Dagger:

A new Dagger compiler option was added to allow disabling transitive validation of component dependency, dagger.validateTransitiveComponentDependencies,. The default value for the flag is enabled (same as before). To disable it, add the following to your compiler options: -Adagger.validateTransitiveComponentDependencies=DISABLED. For a full motivation/discussion, see issue #970.

A new Dagger compiler option was added to fix an issue with map binding contributions that depend on subcomponent bindings, dagger.strictMultibindingValidation. The default value for the flag is disabled (same as before). However, we will be enabling this flag in a future release. To check if your application will be affected, you can enable the flag by adding the following to your compiler options: -Adagger.strictMultibindingValidation=ENABLED. See #2085 for details.

Potential breaking changes

  • Fix an issue where in some cases missing bindings may have been missed during validation. This issue also affects the binding graph that SPI plugins receive so this fix may cause changes where a previously incorrect binding graph was being supplied. (08193ad70)

Bug Fixes

  • Fix #1955, #2065: Hilt would incorrectly try to transform native methods on classes annotated with @AndroidEntryPoint. (2099bade9, 2099bad)
  • Fix #1918: Support BroadcastReceiver with @AndroidEntryPoint transform. (ede018b7a)
  • Fix #1997: Allow Hilt modules to have constructors with params as long as a no-arg constructor exists. (07a7fa979)
  • Fix #2042: Fix bug in OriginatingElementProcessor and ban @AndroidEntryPoint classes with type parameters. (bee2e9a51)
  • Fix #970: Add -Adagger.validateTransitiveComponentDependencies compiler option to prevent validating transitive component dependencies. (6deafc748)
  • Add -Adagger.strictMultibindingValidation compiler option to fix map binding contributions that depend on subcomponent bindings. (fb47e1179)
  • Fix issue with @Binds when the impl extends a generated type. (71509b841)
  • Add support for receiving a callback for when the activity retained component will no longer be used and destroyed. (6300d0277, 218df98db)
  • Throw when a race is detected adding a OnClearedListener. (7cf8b11d6)
  • Reduce constant pool usage by renaming private methods (4a3115780)
Commits
  • f3be0a9 2.29.1 release
  • 6e71d51 Update Hilt Gradle Plugin to recognize hilt-compiler artifact.
  • fb47e11 This is a rollforward with fixes.
  • 1ddc41f Internal change
  • fbedecc Internal change
  • e861c27 Fix redundant memoization for scoped bindings in fastInit.
  • b15fa61 [Hilt]: Add 'hilt-compiler' artifact to replace 'hilt-android-compiler'.
  • 01859b5 [Dagger]: Make everything use dagger.model.BindingGraph
  • bca0f9d Internal change
  • 37d537b Internal change
  • 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 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 use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will 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)

Bumps `dagger` from 2.28.3 to 2.29.1.

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

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

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

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

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Sep 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants