Bump the java-production-dependencies group across 1 directory with 4 updates

[dependabot]

Bumps the java-production-dependencies group with 4 updates in the / directory: com.google.dagger:dagger, com.google.dagger:dagger-compiler, com.google.guava:guava and com.github.ben-manes.caffeine:caffeine.

Updates com.google.dagger:dagger from 2.51.1 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)

Dagger 2.54

Bug fixes

• Fixed #4303: Upgrade Hilt Gradle Plugin to support KSP2 configuration. (76b581999)
• Fixed #4544: Removes private from InstanceHolder field to avoid unnecessary accessor method. (07d8f883f)
• Fixed #4533: Fixes path separator for Windows when creating LazyClassKey proguard file. (efa421a3f)

Notable changes

• In preparation for jakarta support, Dagger’s generated factories now include a create() method that uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() method is also kept for compatibility, but it will be removed in a future release. When that happens, libraries built with the newer version of Dagger may break downstream users of @Component that are built with an older version of Dagger. (d60729d20)

Dagger 2.53.1

Bug fixes

• Fixes #4525: Update kotlin-jvm-metadata to 2.0.21 to remove dependency on Beta version. (84d3aa5f1)
• Fixes #4526: Add the originating element in LazyMapKeyProxyGenerator. (5fd8ec1a3)

Dagger 2.53

Potentially breaking changes:

@Binds methods now requires explicit nullability

New: @Binds methods must explicitly declare nullability (previously we tried to infer it from the parameter). This change aligns the nullability behavior of @Binds with how nullability is treated elsewhere in Dagger by requiring it to be explict at the request and declaration sites. (4941926c5)

Suggested fix: If you get a failure due to this change, add the proper nullability to your @Binds method/parameter. For example:

@Module
interface MyModule {
-    @Binds fun bindToNullableImpl(impl: FooImpl): Foo
+    @Binds fun bindToNullableImpl(impl: FooImpl?): Foo?
}

... (truncated)

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.51.1 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)

Dagger 2.54

Bug fixes

• Fixed #4303: Upgrade Hilt Gradle Plugin to support KSP2 configuration. (76b581999)
• Fixed #4544: Removes private from InstanceHolder field to avoid unnecessary accessor method. (07d8f883f)
• Fixed #4533: Fixes path separator for Windows when creating LazyClassKey proguard file. (efa421a3f)

Notable changes

• In preparation for jakarta support, Dagger’s generated factories now include a create() method that uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() method is also kept for compatibility, but it will be removed in a future release. When that happens, libraries built with the newer version of Dagger may break downstream users of @Component that are built with an older version of Dagger. (d60729d20)

Dagger 2.53.1

Bug fixes

• Fixes #4525: Update kotlin-jvm-metadata to 2.0.21 to remove dependency on Beta version. (84d3aa5f1)
• Fixes #4526: Add the originating element in LazyMapKeyProxyGenerator. (5fd8ec1a3)

Dagger 2.53

Potentially breaking changes:

@Binds methods now requires explicit nullability

New: @Binds methods must explicitly declare nullability (previously we tried to infer it from the parameter). This change aligns the nullability behavior of @Binds with how nullability is treated elsewhere in Dagger by requiring it to be explict at the request and declaration sites. (4941926c5)

Suggested fix: If you get a failure due to this change, add the proper nullability to your @Binds method/parameter. For example:

@Module
interface MyModule {
-    @Binds fun bindToNullableImpl(impl: FooImpl): Foo
+    @Binds fun bindToNullableImpl(impl: FooImpl?): Foo?
}

... (truncated)

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.guava:guava from 33.2.1-jre to 33.4.0-jre

Release notes

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

33.4.0

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.4.0-jre</version>
  <!-- or, for Android: -->
  <version>33.4.0-android</version>
</dependency>

Jar files

• 33.4.0-jre.jar
• 33.4.0-android.jar

Guava requires one runtime dependency, which you can download here:

• failureaccess-1.0.2.jar

Javadoc

• 33.4.0-jre
• 33.4.0-android

JDiff

• 33.4.0-jre vs. 33.3.1-jre
• 33.4.0-android vs. 33.3.1-android
• 33.4.0-android vs. 33.4.0-jre

Changelog

• Exposed additional Java 8 APIs to Android users. (6082782134, 9b0109c662, 6ace8bc8ea, b650b9fe77, c6c268006c, 984f713d76, f9f3fffb87, cdc225474e)
• base: Deprecated Charsets constants in favor of StandardCharsets. We will not remove the constants, but we recommend using StandardCharsets for consistency. (45e6be2688)
• base: Added ToStringHelper.omitEmptyValues(). (f5ec2ab85c)
• collect: Added an optimized copyOf method to TreeRangeMap. (a46565dd1c)
• collect.testing: Fixed @Require annotations so that features implied by absent features are not also required to be absent. (81be061f85)
• io: Changed ByteSink and CharSink to no longer call flush() in some cases before close(). This is a no-op for well-behaved streams, which internally flush their data as part of closing. However, we have discovered some stream implementations that have overridden close() to do nothing, including not to flush some buffered data. If this change causes problems, the simplest fix is usually to change the close() override to at least call flush(). (6ace8bc8ea)
• net: Added HttpHeaders.ALT_SVC and MediaType.CBOR. (503ba429f9, 7c0bf0892d)

33.3.1

Maven

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
</tr></table> 

... (truncated)

Commits

• See full diff in compare view

Updates com.github.ben-manes.caffeine:caffeine from 3.1.8 to 3.2.0

Release notes

Sourced from com.github.ben-manes.caffeine:caffeine's releases.

3.2.0

Cache

• Added Sigstore signing of maven artifacts
• Added Expiry static factory methods (#1499)
• Migrated to JSpecify annotations (was checker framework)
• Fixed variable expiration calculation when nearing overflow
• Added logging when an async cache's removal listener fails
• Added an expiration write optimization to more operations (#1320)
• Fixed when a Weigher or Expiry fail on an async completion (#1687)
• Fixed cases when the expiration ticker was also used for statistics (#1678)
• Fixed refresh handling to skip if the async cache's entry is still loading (#1478)
• Fixed containsKey for an async cache's synchronous view while in-flight (#1626)
• Fixed premature expiration for an async cache when using nearly immediate expiration (#1623)
• For a bulk async load returning extra mappings, wait to be added to the cache before returning (#1409)

Guava

• Relaxed the OSGi version requirement (#1160)

JCache

• Allow hibernate.javax.cache.uri to load the configuration from a jar (#1347)

Commits

• 93d845e prepare for next release
• 8022a16 expand expire write optimization to more operations (fixes #1320)
• 9b65365 Avoid early expiration of an pending future due to delayed pinning (fixes #1623)
• 25405d6 skip refreshing if the async cache entry is still loading (fixes #1478)
• 2d93f2b fix variable expiration calculation when nearing overflow
• 3ff2445 migrate to the maintained javapoet project
• bbf54be minor polish and fixes #1820
• b09770f upgrade to apache commons collections' junit5 test suite
• 70f5cf8 use jakarta.inject for jcache guice integration test
• ae21802 add missing asserts to openjdk tests that check only in their custom harness
• Additional commits viewable in compare view

Updates com.google.dagger:dagger-compiler from 2.51.1 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)

Dagger 2.54

Bug fixes

• Fixed #4303: Upgrade Hilt Gradle Plugin to support KSP2 configuration. (76b581999)
• Fixed #4544: Removes private from InstanceHolder field to avoid unnecessary accessor method. (07d8f883f)
• Fixed #4533: Fixes path separator for Windows when creating LazyClassKey proguard file. (efa421a3f)

Notable changes

• In preparation for jakarta support, Dagger’s generated factories now include a create() method that uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() method is also kept for compatibility, but it will be removed in a future release. When that happens, libraries built with the newer version of Dagger may break downstream users of @Component that are built with an older version of Dagger. (d60729d20)

Dagger 2.53.1

Bug fixes

• Fixes #4525: Update kotlin-jvm-metadata to 2.0.21 to remove dependency on Beta version. (84d3aa5f1)
• Fixes #4526: Add the originating element in LazyMapKeyProxyGenerator. (5fd8ec1a3)

Dagger 2.53

Potentially breaking changes:

@Binds methods now requires explicit nullability

New: @Binds methods must explicitly declare nullability (previously we tried to infer it from the parameter). This change aligns the nullability behavior of @Binds with how nullability is treated elsewhere in Dagger by requiring it to be explict at the request and declaration sites. (4941926c5)

Suggested fix: If you get a failure due to this change, add the proper nullability to your @Binds method/parameter. For example:

@Module
interface MyModule {
-    @Binds fun bindToNullableImpl(impl: FooImpl): Foo
+    @Binds fun bindToNullableImpl(impl: FooImpl?): Foo?
}

... (truncated)

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions