Bump daggerVersion from 2.25.2 to 2.30.1

[dependabot]

Bumps daggerVersion from 2.25.2 to 2.30.1.
Updates dagger from 2.25.2 to 2.30.1

Release notes

Sourced from dagger's releases.

Dagger 2.30.1

Bug fixes

• Sets the default value for experimentalDaggerErrorMessages back to disabled since it breaks hyperlinks in AndroidStudio (6a8bbbf03) . Note that this reverses the change to the default value made in the release 2.30.
• Fixes #2190: Dagger was unnecessarily inspecting all fields of a class and attempting to find their Kotlin metadata, which sometimes led to crashing the processor. Now, Dagger inspects the Kotlin metadata lazily, and only on the fields that require it. (a885c85cb)

Dagger 2.30

What’s new

Hilt

Hilt has deprecated ApplicationComponent (6313cbdf2), and it will soon be removed in a future release. Use SingletonComponent instead.

Hilt now supports @BindValue val fields in Kotlin without the use of @JvmField (802882dd4). For example:

// Before
@BindValue @JvmField val bindStr = "STRING_BINDING"
// Now
@BindValue val bindStr = "STRING_BINDING"

Dagger

Dagger now uses the “experimentalDaggerErrorMessages” by default (See #1769 for more information). The old error message format can still be used by setting -Adagger.experimentalDaggerErrorMessages=disabled as a javacopt.

Bug Fixes

• [Dagger]: Fixes a Dagger compiler crash that occurred when an @Inject was placed in a Kotlin object class. (0816c43f5)
• [Hilt]: Fixes #2156: Update Dagger's androidx dependencies to the latest stable versions. (deff5e59e)
• [Hilt]: Fixes suppress deprecation warning in Hilt generated Fragment class. (0a463eb84)
• [Hilt]: Removes Hilt's dependency on jsr250 for @Generated. (8dca74b) Note: Hilt previously depended on jsr250 for the @Generated annotation, but this behavior has now been changed to match Dagger (see #95). Now, Hilt only adds the @Generated annotation only if the Generated class is present in the classpath. Thus, since we’ve now removed the jsr250 dependency from Hilt, the generated code will no longer contain the @Generated annotation by default.

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.

... (truncated)

Commits

• 1c923c8 2.30.1 release
• 6a8bbbf Flip the default for experimentalDaggerErrorMessages back to disabled since i...
• a885c85 Lazily match fields to their Kotlin property metadata.
• e0d9ef2 Add a missing @Override on #injectTest.
• 8dca74b Remove erroneously added JSR250 deps from the Hilt runtime.
• 6313cbd Deprecate ApplicationComponent for SingletonComponent.
• 0e8f761 Turn on experimental dagger error messages by default. The old messages can s...
• 55c06b5 Internal refactor.
• 8cafe80 Rollback of Migrating @ViewModelInject into Hilt's codebase.
• b02960c Migrating @ViewModelInject into Hilt's codebase.
• Additional commits viewable in compare view

Updates dagger-android-support from 2.25.2 to 2.30.1

Release notes

Sourced from dagger-android-support's releases.

Dagger 2.30.1

Bug fixes

• Sets the default value for experimentalDaggerErrorMessages back to disabled since it breaks hyperlinks in AndroidStudio (6a8bbbf03) . Note that this reverses the change to the default value made in the release 2.30.
• Fixes #2190: Dagger was unnecessarily inspecting all fields of a class and attempting to find their Kotlin metadata, which sometimes led to crashing the processor. Now, Dagger inspects the Kotlin metadata lazily, and only on the fields that require it. (a885c85cb)

Dagger 2.30

What’s new

Hilt

Hilt has deprecated ApplicationComponent (6313cbdf2), and it will soon be removed in a future release. Use SingletonComponent instead.

Hilt now supports @BindValue val fields in Kotlin without the use of @JvmField (802882dd4). For example:

// Before
@BindValue @JvmField val bindStr = "STRING_BINDING"
// Now
@BindValue val bindStr = "STRING_BINDING"

Dagger

Dagger now uses the “experimentalDaggerErrorMessages” by default (See #1769 for more information). The old error message format can still be used by setting -Adagger.experimentalDaggerErrorMessages=disabled as a javacopt.

Bug Fixes

• [Dagger]: Fixes a Dagger compiler crash that occurred when an @Inject was placed in a Kotlin object class. (0816c43f5)
• [Hilt]: Fixes #2156: Update Dagger's androidx dependencies to the latest stable versions. (deff5e59e)
• [Hilt]: Fixes suppress deprecation warning in Hilt generated Fragment class. (0a463eb84)
• [Hilt]: Removes Hilt's dependency on jsr250 for @Generated. (8dca74b) Note: Hilt previously depended on jsr250 for the @Generated annotation, but this behavior has now been changed to match Dagger (see #95). Now, Hilt only adds the @Generated annotation only if the Generated class is present in the classpath. Thus, since we’ve now removed the jsr250 dependency from Hilt, the generated code will no longer contain the @Generated annotation by default.

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.

... (truncated)

Commits

• 1c923c8 2.30.1 release
• 6a8bbbf Flip the default for experimentalDaggerErrorMessages back to disabled since i...
• a885c85 Lazily match fields to their Kotlin property metadata.
• e0d9ef2 Add a missing @Override on #injectTest.
• 8dca74b Remove erroneously added JSR250 deps from the Hilt runtime.
• 6313cbd Deprecate ApplicationComponent for SingletonComponent.
• 0e8f761 Turn on experimental dagger error messages by default. The old messages can s...
• 55c06b5 Internal refactor.
• 8cafe80 Rollback of Migrating @ViewModelInject into Hilt's codebase.
• b02960c Migrating @ViewModelInject into Hilt's codebase.
• Additional commits viewable in compare view

Updates dagger-compiler from 2.25.2 to 2.30.1

Release notes

Sourced from dagger-compiler's releases.

Dagger 2.30.1

Bug fixes

• Sets the default value for experimentalDaggerErrorMessages back to disabled since it breaks hyperlinks in AndroidStudio (6a8bbbf03) . Note that this reverses the change to the default value made in the release 2.30.
• Fixes #2190: Dagger was unnecessarily inspecting all fields of a class and attempting to find their Kotlin metadata, which sometimes led to crashing the processor. Now, Dagger inspects the Kotlin metadata lazily, and only on the fields that require it. (a885c85cb)

Dagger 2.30

What’s new

Hilt

Hilt has deprecated ApplicationComponent (6313cbdf2), and it will soon be removed in a future release. Use SingletonComponent instead.

Hilt now supports @BindValue val fields in Kotlin without the use of @JvmField (802882dd4). For example:

// Before
@BindValue @JvmField val bindStr = "STRING_BINDING"
// Now
@BindValue val bindStr = "STRING_BINDING"

Dagger

Dagger now uses the “experimentalDaggerErrorMessages” by default (See #1769 for more information). The old error message format can still be used by setting -Adagger.experimentalDaggerErrorMessages=disabled as a javacopt.

Bug Fixes

• [Dagger]: Fixes a Dagger compiler crash that occurred when an @Inject was placed in a Kotlin object class. (0816c43f5)
• [Hilt]: Fixes #2156: Update Dagger's androidx dependencies to the latest stable versions. (deff5e59e)
• [Hilt]: Fixes suppress deprecation warning in Hilt generated Fragment class. (0a463eb84)
• [Hilt]: Removes Hilt's dependency on jsr250 for @Generated. (8dca74b) Note: Hilt previously depended on jsr250 for the @Generated annotation, but this behavior has now been changed to match Dagger (see #95). Now, Hilt only adds the @Generated annotation only if the Generated class is present in the classpath. Thus, since we’ve now removed the jsr250 dependency from Hilt, the generated code will no longer contain the @Generated annotation by default.

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.

... (truncated)

Commits

• 1c923c8 2.30.1 release
• 6a8bbbf Flip the default for experimentalDaggerErrorMessages back to disabled since i...
• a885c85 Lazily match fields to their Kotlin property metadata.
• e0d9ef2 Add a missing @Override on #injectTest.
• 8dca74b Remove erroneously added JSR250 deps from the Hilt runtime.
• 6313cbd Deprecate ApplicationComponent for SingletonComponent.
• 0e8f761 Turn on experimental dagger error messages by default. The old messages can s...
• 55c06b5 Internal refactor.
• 8cafe80 Rollback of Migrating @ViewModelInject into Hilt's codebase.
• b02960c Migrating @ViewModelInject into Hilt's codebase.
• Additional commits viewable in compare view

Updates dagger-android-processor from 2.25.2 to 2.30.1

Release notes

Sourced from dagger-android-processor's releases.

Dagger 2.30.1

Bug fixes

• Sets the default value for experimentalDaggerErrorMessages back to disabled since it breaks hyperlinks in AndroidStudio (6a8bbbf03) . Note that this reverses the change to the default value made in the release 2.30.
• Fixes #2190: Dagger was unnecessarily inspecting all fields of a class and attempting to find their Kotlin metadata, which sometimes led to crashing the processor. Now, Dagger inspects the Kotlin metadata lazily, and only on the fields that require it. (a885c85cb)

Dagger 2.30

What’s new

Hilt

Hilt has deprecated ApplicationComponent (6313cbdf2), and it will soon be removed in a future release. Use SingletonComponent instead.

Hilt now supports @BindValue val fields in Kotlin without the use of @JvmField (802882dd4). For example:

// Before
@BindValue @JvmField val bindStr = "STRING_BINDING"
// Now
@BindValue val bindStr = "STRING_BINDING"

Dagger

Dagger now uses the “experimentalDaggerErrorMessages” by default (See #1769 for more information). The old error message format can still be used by setting -Adagger.experimentalDaggerErrorMessages=disabled as a javacopt.

Bug Fixes

• [Dagger]: Fixes a Dagger compiler crash that occurred when an @Inject was placed in a Kotlin object class. (0816c43f5)
• [Hilt]: Fixes #2156: Update Dagger's androidx dependencies to the latest stable versions. (deff5e59e)
• [Hilt]: Fixes suppress deprecation warning in Hilt generated Fragment class. (0a463eb84)
• [Hilt]: Removes Hilt's dependency on jsr250 for @Generated. (8dca74b) Note: Hilt previously depended on jsr250 for the @Generated annotation, but this behavior has now been changed to match Dagger (see #95). Now, Hilt only adds the @Generated annotation only if the Generated class is present in the classpath. Thus, since we’ve now removed the jsr250 dependency from Hilt, the generated code will no longer contain the @Generated annotation by default.

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.

... (truncated)

Commits

• 1c923c8 2.30.1 release
• 6a8bbbf Flip the default for experimentalDaggerErrorMessages back to disabled since i...
• a885c85 Lazily match fields to their Kotlin property metadata.
• e0d9ef2 Add a missing @Override on #injectTest.
• 8dca74b Remove erroneously added JSR250 deps from the Hilt runtime.
• 6313cbd Deprecate ApplicationComponent for SingletonComponent.
• 0e8f761 Turn on experimental dagger error messages by default. The old messages can s...
• 55c06b5 Internal refactor.
• 8cafe80 Rollback of Migrating @ViewModelInject into Hilt's codebase.
• b02960c Migrating @ViewModelInject into Hilt's codebase.
• 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)