Bump dagger from 2.54 to 2.55

[dependabot]

Bumps dagger from 2.54 to 2.55.
Updates com.google.dagger:dagger from 2.54 to 2.55

Release notes

Sourced from com.google.dagger:dagger's releases.

Dagger 2.55

Notable/breaking changes

• Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.inject.Provider. (caa7e178b)
• Fixed a number of binding graph related issues. These fixes can be enabled with, -Adagger.useBindingGraphFix=ENABLED, but due to this sometimes being a breaking change we’ve set the default behavior to “disabled” for now. We will flip the default to “enabled” in a future release, and eventually remove the flag altogether. Enabling this feature can fix a number of confusing error messages. See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix for more details.

Bug fixes

• Fixed #4549: Fixed incremental processing for LazyClassKey proguard files by adding the originating element to the writeResource call. (98a027541)

Commits

• 14ad560 2.55 release
• 7ca9977 Add binary compatibility validator to the Gradle projects
• 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
• 8b4f9b6 Add maven publish plugin to Gradle projects.
• 9daa0ae Wire resource configuration while keeping the Bazel project structure.
• 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
• 0927b9a Add flag to control LegacyBindingGraphFactory usage.
• 1620e92 Add Github CI step and action for building with Gradle
• c43783a Initial setup of Gradle as a build system for Dagger
• 98a0275 Fix LazyClassKey proguard file issues.
• Additional commits viewable in compare view

Updates com.google.dagger:dagger-compiler from 2.54 to 2.55

Release notes

Sourced from com.google.dagger:dagger-compiler's releases.

Dagger 2.55

Notable/breaking changes

• Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.inject.Provider. (caa7e178b)
• Fixed a number of binding graph related issues. These fixes can be enabled with, -Adagger.useBindingGraphFix=ENABLED, but due to this sometimes being a breaking change we’ve set the default behavior to “disabled” for now. We will flip the default to “enabled” in a future release, and eventually remove the flag altogether. Enabling this feature can fix a number of confusing error messages. See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix for more details.

Bug fixes

• Fixed #4549: Fixed incremental processing for LazyClassKey proguard files by adding the originating element to the writeResource call. (98a027541)

Commits

• 14ad560 2.55 release
• 7ca9977 Add binary compatibility validator to the Gradle projects
• 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
• 8b4f9b6 Add maven publish plugin to Gradle projects.
• 9daa0ae Wire resource configuration while keeping the Bazel project structure.
• 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
• 0927b9a Add flag to control LegacyBindingGraphFactory usage.
• 1620e92 Add Github CI step and action for building with Gradle
• c43783a Initial setup of Gradle as a build system for Dagger
• 98a0275 Fix LazyClassKey proguard file issues.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-core from 2.54 to 2.55

Release notes

Sourced from com.google.dagger:hilt-core's releases.

Dagger 2.55

Notable/breaking changes

• Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.inject.Provider. (caa7e178b)
• Fixed a number of binding graph related issues. These fixes can be enabled with, -Adagger.useBindingGraphFix=ENABLED, but due to this sometimes being a breaking change we’ve set the default behavior to “disabled” for now. We will flip the default to “enabled” in a future release, and eventually remove the flag altogether. Enabling this feature can fix a number of confusing error messages. See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix for more details.

Bug fixes

• Fixed #4549: Fixed incremental processing for LazyClassKey proguard files by adding the originating element to the writeResource call. (98a027541)

Commits

• 14ad560 2.55 release
• 7ca9977 Add binary compatibility validator to the Gradle projects
• 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
• 8b4f9b6 Add maven publish plugin to Gradle projects.
• 9daa0ae Wire resource configuration while keeping the Bazel project structure.
• 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
• 0927b9a Add flag to control LegacyBindingGraphFactory usage.
• 1620e92 Add Github CI step and action for building with Gradle
• c43783a Initial setup of Gradle as a build system for Dagger
• 98a0275 Fix LazyClassKey proguard file issues.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-android from 2.54 to 2.55

Release notes

Sourced from com.google.dagger:hilt-android's releases.

Dagger 2.55

Notable/breaking changes

• Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.inject.Provider. (caa7e178b)
• Fixed a number of binding graph related issues. These fixes can be enabled with, -Adagger.useBindingGraphFix=ENABLED, but due to this sometimes being a breaking change we’ve set the default behavior to “disabled” for now. We will flip the default to “enabled” in a future release, and eventually remove the flag altogether. Enabling this feature can fix a number of confusing error messages. See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix for more details.

Bug fixes

• Fixed #4549: Fixed incremental processing for LazyClassKey proguard files by adding the originating element to the writeResource call. (98a027541)

Commits

• 14ad560 2.55 release
• 7ca9977 Add binary compatibility validator to the Gradle projects
• 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
• 8b4f9b6 Add maven publish plugin to Gradle projects.
• 9daa0ae Wire resource configuration while keeping the Bazel project structure.
• 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
• 0927b9a Add flag to control LegacyBindingGraphFactory usage.
• 1620e92 Add Github CI step and action for building with Gradle
• c43783a Initial setup of Gradle as a build system for Dagger
• 98a0275 Fix LazyClassKey proguard file issues.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-android-testing from 2.54 to 2.55

Release notes

Sourced from com.google.dagger:hilt-android-testing's releases.

Dagger 2.55

Notable/breaking changes

• Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.inject.Provider. (caa7e178b)
• Fixed a number of binding graph related issues. These fixes can be enabled with, -Adagger.useBindingGraphFix=ENABLED, but due to this sometimes being a breaking change we’ve set the default behavior to “disabled” for now. We will flip the default to “enabled” in a future release, and eventually remove the flag altogether. Enabling this feature can fix a number of confusing error messages. See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix for more details.

Bug fixes

• Fixed #4549: Fixed incremental processing for LazyClassKey proguard files by adding the originating element to the writeResource call. (98a027541)

Commits

• 14ad560 2.55 release
• 7ca9977 Add binary compatibility validator to the Gradle projects
• 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
• 8b4f9b6 Add maven publish plugin to Gradle projects.
• 9daa0ae Wire resource configuration while keeping the Bazel project structure.
• 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
• 0927b9a Add flag to control LegacyBindingGraphFactory usage.
• 1620e92 Add Github CI step and action for building with Gradle
• c43783a Initial setup of Gradle as a build system for Dagger
• 98a0275 Fix LazyClassKey proguard file issues.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-compiler from 2.54 to 2.55

Release notes

Sourced from com.google.dagger:hilt-compiler's releases.

Dagger 2.55

Notable/breaking changes

• Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.inject.Provider. (caa7e178b)
• Fixed a number of binding graph related issues. These fixes can be enabled with, -Adagger.useBindingGraphFix=ENABLED, but due to this sometimes being a breaking change we’ve set the default behavior to “disabled” for now. We will flip the default to “enabled” in a future release, and eventually remove the flag altogether. Enabling this feature can fix a number of confusing error messages. See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix for more details.

Bug fixes

• Fixed #4549: Fixed incremental processing for LazyClassKey proguard files by adding the originating element to the writeResource call. (98a027541)

Commits

• 14ad560 2.55 release
• 7ca9977 Add binary compatibility validator to the Gradle projects
• 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
• 8b4f9b6 Add maven publish plugin to Gradle projects.
• 9daa0ae Wire resource configuration while keeping the Bazel project structure.
• 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
• 0927b9a Add flag to control LegacyBindingGraphFactory usage.
• 1620e92 Add Github CI step and action for building with Gradle
• c43783a Initial setup of Gradle as a build system for Dagger
• 98a0275 Fix LazyClassKey proguard file issues.
• Additional commits viewable in compare view

Updates com.google.dagger.hilt.android from 2.54 to 2.55

Release notes

Sourced from com.google.dagger.hilt.android's releases.

Dagger 2.55

Notable/breaking changes

• Added support for injecting jakarta.inject.Provider. This should be usable anywhere javax.inject.Provider is usable. Note that this technically comes with a breaking change to disallow providing jakarta.inject.Provider types in the same way it is disallowed for javax.inject.Provider. (caa7e178b)
• Fixed a number of binding graph related issues. These fixes can be enabled with, -Adagger.useBindingGraphFix=ENABLED, but due to this sometimes being a breaking change we’ve set the default behavior to “disabled” for now. We will flip the default to “enabled” in a future release, and eventually remove the flag altogether. Enabling this feature can fix a number of confusing error messages. See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix for more details.

Bug fixes

• Fixed #4549: Fixed incremental processing for LazyClassKey proguard files by adding the originating element to the writeResource call. (98a027541)

Commits

• 14ad560 2.55 release
• 7ca9977 Add binary compatibility validator to the Gradle projects
• 4cd83cb Add documentation for dagger.useBindingGraphFix compiler option.
• 8b4f9b6 Add maven publish plugin to Gradle projects.
• 9daa0ae Wire resource configuration while keeping the Bazel project structure.
• 3418609 Move JDK toolchain, Kotlin language and JVM target configuration to conventio...
• 0927b9a Add flag to control LegacyBindingGraphFactory usage.
• 1620e92 Add Github CI step and action for building with Gradle
• c43783a Initial setup of Gradle as a build system for Dagger
• 98a0275 Fix LazyClassKey proguard file issues.
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)