Bump hilt_version from 2.38.1 to 2.40.1

[dependabot]

Bumps hilt_version from 2.38.1 to 2.40.1.
Updates hilt-android-gradle-plugin from 2.38.1 to 2.40.1

Release notes

Sourced from hilt-android-gradle-plugin's releases.

Dagger 2.40.1

Bug Fixes

• Fix an AGP 7.2 incompatibility issue in the Hilt Gradle Plugin due to AGP breaking their API when cleaning up a deprecated type. (ed677ba1c)
• Fix #2986 - An issue in the Dagger processor where it would crash due to a bad initialization. (608bcba38)

Dagger 2.40

What’s New in Hilt

New Changes

• Flip the runtime flag default so that the fix is off and remove the compiler option for the Fragment.getContext() fix to make it easier to roll out the fix. This does not change the current default behavior of having the fix be off. (1c24b9718, e61ff7239)
• Turn ON enableAggregatingTask by default in Hilt (90ea6a604)

Bug fixes

• EarlyEntryPoints#get() will now throw if there are no @​EarlyEntryPoint annotated interfaces. (b5ef01c04)
• Avoid using UAST implementation classes in Lint checkers. (44e1f056e)
• Fix an issue where @OptionalInject activity/fragment classes could not be used with non-Hilt ViewModels. (8ef08fa07)

Dagger 2.39.1

Hilt bug fixes

• Fix #2834: Hilt processor now checks the correct "names" property when getting values from Kotlin @Suppress annotations. (db21d3fd1)
• Fix #2904: Change toImmutableSet to use DaggerStreams rather than Guava. (43a7fe1ba)

Dagger 2.39

What’s new in Hilt

New breaking changes

• The compiler flag shareTestComponents now defaults to true. This may significantly improve test compilation time for large projects, but is a breaking change for some tests due to changed visibility requirements. See Hilt’s flags documentation for details. (7e09cee32)
• Hilt compiler flags are now strictly verified. Invalid flags will no longer compile. (742ba95e4)

Bug fixes

• Fix #2779: Dagger no longer requires the additional google repository mentioned in the Dagger 2.28 release notes. (01cf47b26)
• There is now a runtime flag to control the Fragment.getContext() fix submitted in google/dagger#2620. This allows enabling or disabling the fix without a compiler flag in order to permit a staged rollout. (c3f613f4c)
• Fix #2789: Fixes issue with using EarlyEntryPoints being dropped when using enableAggregatingTask (38db196d7)
• Fix a remote cache miss due to @Input parameter in ASM transform. (2f5003545)

Commits

• 07dc99d 2.40.1 release
• 68a22b7 Update Bazel check in deploy script as we now use Bazel 4.2.1.
• 3703588 Change ComponentTreeDepsIrCreator to use linkedSetOf instead of mutableSetOf.
• 2fa9aa7 Upgrade to Bazel 4.2.1
• 608bcba Inject the processor earlier in the initialize method rather than in processi...
• e4519f6 Internal changes.
• 3d71e84 Make FrameworkInstanceBindingRepresentation do not use `DirectInstanceBindi...
• 1577b44 Internal changes.
• f5b06c5 Internal refactor
• 4329998 Migrate Scopes to XProcessing.
• Additional commits viewable in compare view

Updates hilt-android from 2.38.1 to 2.40.1

Release notes

Sourced from hilt-android's releases.

Dagger 2.40.1

Bug Fixes

• Fix an AGP 7.2 incompatibility issue in the Hilt Gradle Plugin due to AGP breaking their API when cleaning up a deprecated type. (ed677ba1c)
• Fix #2986 - An issue in the Dagger processor where it would crash due to a bad initialization. (608bcba38)

Dagger 2.40

What’s New in Hilt

New Changes

• Flip the runtime flag default so that the fix is off and remove the compiler option for the Fragment.getContext() fix to make it easier to roll out the fix. This does not change the current default behavior of having the fix be off. (1c24b9718, e61ff7239)
• Turn ON enableAggregatingTask by default in Hilt (90ea6a604)

Bug fixes

• EarlyEntryPoints#get() will now throw if there are no @​EarlyEntryPoint annotated interfaces. (b5ef01c04)
• Avoid using UAST implementation classes in Lint checkers. (44e1f056e)
• Fix an issue where @OptionalInject activity/fragment classes could not be used with non-Hilt ViewModels. (8ef08fa07)

Dagger 2.39.1

Hilt bug fixes

• Fix #2834: Hilt processor now checks the correct "names" property when getting values from Kotlin @Suppress annotations. (db21d3fd1)
• Fix #2904: Change toImmutableSet to use DaggerStreams rather than Guava. (43a7fe1ba)

Dagger 2.39

What’s new in Hilt

New breaking changes

• The compiler flag shareTestComponents now defaults to true. This may significantly improve test compilation time for large projects, but is a breaking change for some tests due to changed visibility requirements. See Hilt’s flags documentation for details. (7e09cee32)
• Hilt compiler flags are now strictly verified. Invalid flags will no longer compile. (742ba95e4)

Bug fixes

• Fix #2779: Dagger no longer requires the additional google repository mentioned in the Dagger 2.28 release notes. (01cf47b26)
• There is now a runtime flag to control the Fragment.getContext() fix submitted in google/dagger#2620. This allows enabling or disabling the fix without a compiler flag in order to permit a staged rollout. (c3f613f4c)
• Fix #2789: Fixes issue with using EarlyEntryPoints being dropped when using enableAggregatingTask (38db196d7)
• Fix a remote cache miss due to @Input parameter in ASM transform. (2f5003545)

Commits

• 07dc99d 2.40.1 release
• 68a22b7 Update Bazel check in deploy script as we now use Bazel 4.2.1.
• 3703588 Change ComponentTreeDepsIrCreator to use linkedSetOf instead of mutableSetOf.
• 2fa9aa7 Upgrade to Bazel 4.2.1
• 608bcba Inject the processor earlier in the initialize method rather than in processi...
• e4519f6 Internal changes.
• 3d71e84 Make FrameworkInstanceBindingRepresentation do not use `DirectInstanceBindi...
• 1577b44 Internal changes.
• f5b06c5 Internal refactor
• 4329998 Migrate Scopes to XProcessing.
• Additional commits viewable in compare view

Updates hilt-android-compiler from 2.38.1 to 2.40.1

Release notes

Sourced from hilt-android-compiler's releases.

Dagger 2.40.1

Bug Fixes

• Fix an AGP 7.2 incompatibility issue in the Hilt Gradle Plugin due to AGP breaking their API when cleaning up a deprecated type. (ed677ba1c)
• Fix #2986 - An issue in the Dagger processor where it would crash due to a bad initialization. (608bcba38)

Dagger 2.40

What’s New in Hilt

New Changes

• Flip the runtime flag default so that the fix is off and remove the compiler option for the Fragment.getContext() fix to make it easier to roll out the fix. This does not change the current default behavior of having the fix be off. (1c24b9718, e61ff7239)
• Turn ON enableAggregatingTask by default in Hilt (90ea6a604)

Bug fixes

• EarlyEntryPoints#get() will now throw if there are no @​EarlyEntryPoint annotated interfaces. (b5ef01c04)
• Avoid using UAST implementation classes in Lint checkers. (44e1f056e)
• Fix an issue where @OptionalInject activity/fragment classes could not be used with non-Hilt ViewModels. (8ef08fa07)

Dagger 2.39.1

Hilt bug fixes

• Fix #2834: Hilt processor now checks the correct "names" property when getting values from Kotlin @Suppress annotations. (db21d3fd1)
• Fix #2904: Change toImmutableSet to use DaggerStreams rather than Guava. (43a7fe1ba)

Dagger 2.39

What’s new in Hilt

New breaking changes

• The compiler flag shareTestComponents now defaults to true. This may significantly improve test compilation time for large projects, but is a breaking change for some tests due to changed visibility requirements. See Hilt’s flags documentation for details. (7e09cee32)
• Hilt compiler flags are now strictly verified. Invalid flags will no longer compile. (742ba95e4)

Bug fixes

• Fix #2779: Dagger no longer requires the additional google repository mentioned in the Dagger 2.28 release notes. (01cf47b26)
• There is now a runtime flag to control the Fragment.getContext() fix submitted in google/dagger#2620. This allows enabling or disabling the fix without a compiler flag in order to permit a staged rollout. (c3f613f4c)
• Fix #2789: Fixes issue with using EarlyEntryPoints being dropped when using enableAggregatingTask (38db196d7)
• Fix a remote cache miss due to @Input parameter in ASM transform. (2f5003545)

Commits

• 07dc99d 2.40.1 release
• 68a22b7 Update Bazel check in deploy script as we now use Bazel 4.2.1.
• 3703588 Change ComponentTreeDepsIrCreator to use linkedSetOf instead of mutableSetOf.
• 2fa9aa7 Upgrade to Bazel 4.2.1
• 608bcba Inject the processor earlier in the initialize method rather than in processi...
• e4519f6 Internal changes.
• 3d71e84 Make FrameworkInstanceBindingRepresentation do not use `DirectInstanceBindi...
• 1577b44 Internal changes.
• f5b06c5 Internal refactor
• 4329998 Migrate Scopes to XProcessing.
• Additional commits viewable in compare view

Updates hilt-core from 2.38.1 to 2.40.1

Release notes

Sourced from hilt-core's releases.

Dagger 2.40.1

Bug Fixes

• Fix an AGP 7.2 incompatibility issue in the Hilt Gradle Plugin due to AGP breaking their API when cleaning up a deprecated type. (ed677ba1c)
• Fix #2986 - An issue in the Dagger processor where it would crash due to a bad initialization. (608bcba38)

Dagger 2.40

What’s New in Hilt

New Changes

• Flip the runtime flag default so that the fix is off and remove the compiler option for the Fragment.getContext() fix to make it easier to roll out the fix. This does not change the current default behavior of having the fix be off. (1c24b9718, e61ff7239)
• Turn ON enableAggregatingTask by default in Hilt (90ea6a604)

Bug fixes

• EarlyEntryPoints#get() will now throw if there are no @​EarlyEntryPoint annotated interfaces. (b5ef01c04)
• Avoid using UAST implementation classes in Lint checkers. (44e1f056e)
• Fix an issue where @OptionalInject activity/fragment classes could not be used with non-Hilt ViewModels. (8ef08fa07)

Dagger 2.39.1

Hilt bug fixes

• Fix #2834: Hilt processor now checks the correct "names" property when getting values from Kotlin @Suppress annotations. (db21d3fd1)
• Fix #2904: Change toImmutableSet to use DaggerStreams rather than Guava. (43a7fe1ba)

Dagger 2.39

What’s new in Hilt

New breaking changes

• The compiler flag shareTestComponents now defaults to true. This may significantly improve test compilation time for large projects, but is a breaking change for some tests due to changed visibility requirements. See Hilt’s flags documentation for details. (7e09cee32)
• Hilt compiler flags are now strictly verified. Invalid flags will no longer compile. (742ba95e4)

Bug fixes

• Fix #2779: Dagger no longer requires the additional google repository mentioned in the Dagger 2.28 release notes. (01cf47b26)
• There is now a runtime flag to control the Fragment.getContext() fix submitted in google/dagger#2620. This allows enabling or disabling the fix without a compiler flag in order to permit a staged rollout. (c3f613f4c)
• Fix #2789: Fixes issue with using EarlyEntryPoints being dropped when using enableAggregatingTask (38db196d7)
• Fix a remote cache miss due to @Input parameter in ASM transform. (2f5003545)

Commits

• 07dc99d 2.40.1 release
• 68a22b7 Update Bazel check in deploy script as we now use Bazel 4.2.1.
• 3703588 Change ComponentTreeDepsIrCreator to use linkedSetOf instead of mutableSetOf.
• 2fa9aa7 Upgrade to Bazel 4.2.1
• 608bcba Inject the processor earlier in the initialize method rather than in processi...
• e4519f6 Internal changes.
• 3d71e84 Make FrameworkInstanceBindingRepresentation do not use `DirectInstanceBindi...
• 1577b44 Internal changes.
• f5b06c5 Internal refactor
• 4329998 Migrate Scopes to XProcessing.
• 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]

Superseded by #19.