Bump dagger-compiler from 2.33 to 2.36

[dependabot[bot]]

Bumps dagger-compiler from 2.33 to 2.36.

Release notes

Sourced from dagger-compiler's releases.

Dagger 2.36

What’s New in Dagger

New breaking changes

• Added compile time set binding validation for cases where the same key is bound into a set multiple times. Previously, cases of this could result in a runtime failure due to a similar check at runtime, but in rare cases that don’t trigger the runtime error, this could be a breaking change. (cf2047099)

Bug Fixes

• Make nested subcomponents and switching provider impls static within the generated component class. This is in preparation for eventually unnesting these classes from within their parent component to avoid issues that arise from deeply nested class names being too long. (d9f08aa3c)

What’s New in Hilt

Fragment#getContext() behavior fixed behind a flag

Currently, a Hilt fragment’s getContext() method incorrectly continues to return a context value even after the fragment is removed. This differs from the behavior of a regular fragment. Fixing this is a breaking change that may introduce crashes at runtime if code incorrectly accessed the fragment’s context after removal and relied on Hilt’s incorrect behavior, so a flag has been introduced with the new fixed behavior default off.

Please enable the flag with -Adagger.hilt.android.useFragmentGetContextFix=true to roll out this change at your own discretion. You may choose to, for example, start by enabling this only in development or some small testing population to find errors. In a future release, this flag will be defaulted to true and then in some release after that, the flag will be removed. (5ce0ceadd)

Bug Fixes

• Fix a bug where a Hilt fragment’s getContext() method could not be called before super.onAttach(). (8acc4336f)
• Fix compatibility issue with the Hilt Gradle Plugin and Android Gradle Plugin 7.0 (371a2c366)
• Fix lint issue with Hilt testing classes that get compiled to reference invalid ReflectiveOperationException for API < 19. (e58abc3f7)

Dagger 2.35.1

Hilt bug fixes

• Fix #2577: Adds a flag to disable the cross-compilation root validation that was enabled by default as of version 2.35. (See https://dagger.dev/hilt/compiler-options#disable-cross-compilation-root-validation for more details). (bfdb10962)
• Reduce the possibility of OOMs in the local unit test transform task that is executed for users with AGP older than 4.2.0. (61ef9d879)

Dagger 2.35

What’s New in Hilt

Hilt is now stable!

This means that Hilt is ready for use in production. Thanks for all the feedback through our alpha and beta stages! From now on, Hilt will no longer have alpha/beta releases and instead will be released with the same process as Dagger.

New breaking changes

• In the rare case that an app is relying on an @EarlyEntryPoint usage in a library that is built using an older version of Hilt, the @EarlyEntryPoint will no longer be picked up, resulting in a runtime error in tests (production code will be unaffected). To fix, all upstream usages of @EarlyEntryPoint must be built using this version of Hilt or later. (27a28276b)
• Hilt now checks that builds with @HiltAndroidApp do not depend on targets with @HiltAndroidTest and vice versa as this can cause confusion with which modules are included in which Dagger components. Hilt version 2.35.1 adds a flag to disable this check.

Bug fixes

• Fix an issue where internal Kotlin object modules were incorrectly depended on directly by the component, which could result in a build failure if the component did not have visibility to the module. (115eaac88)
• Fix an issue in the Hilt Gradle Plugin where determining AGP version failed if the AGP version being used was older than 3.6. (0218653f9)

Dagger 2.34.1

Hilt Bug fixes

• Fix #2070: Fix leak in FragmentContextWrapper by also releasing the inflators, if they exists. (41c4e04da)

Dagger 2.34

What’s New in Dagger

... (truncated)

Commits

• 32b4f90 2.36 release
• 5ce0cea Adds the dagger.hilt.android.useFragmentGetContextFix flag to guard the corre...
• 9bfc67e Temporarily hide the 'enableAggregatingTask' option.
• 6bd3c6e Group BindingExpression and CreationExpression factories into UnscopedDirectI...
• 266100e Enable Gradle config cache in test projects when AGP is 4.2.0+
• 935a437 Refactor BindingExpressions and CreationExpressions to use assisted injection.
• 8bba02f Use WorkerApi in HiltGradlePlugin's AggregateDepsTask
• efcf848 Update Hilt incremental processor tests to verify isolating and aggregating t...
• 0057216 Share aggregating logic between RootProcessor and Gradle plugin.
• f227774 Add the concept of ShardImplementation.
• 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[bot]]

Superseded by #373.