Skip to content

fix(deps): update dependency com.google.guava:guava to v33.8.0 - #265

Open
renovate-bot wants to merge 1 commit into
googleapis:mainfrom
renovate-bot:renovate/guava-monorepo
Open

fix(deps): update dependency com.google.guava:guava to v33.8.0#265
renovate-bot wants to merge 1 commit into
googleapis:mainfrom
renovate-bot:renovate/guava-monorepo

Conversation

@renovate-bot

@renovate-bot renovate-bot commented May 2, 2024 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
com.google.guava:guava 33.1.0-jre → 33.8.0-jre age confidence

Release Notes

google/guava (com.google.guava:guava)

v33.8.0: 33.8.0

Compare Source

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

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

Javadoc
JDiff
Changelog

v33.7.2: 33.7.2

Compare Source

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

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

Javadoc
JDiff
Changelog

v33.7.1: 33.7.1

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

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

Javadoc
JDiff
Changelog

Guava 33.7.1 removes the Multi-Release line from our jar manifest, fixing an issue under Java 9 and 10 that was introduced to guava-jre in version 33.7.0. Sorry for the trouble.

v33.7.0: 33.7.0

Newly introduced problem for Java 9 and Java 10 only

Guava 33.7.0 includes a Multi-Release line in its jar manifest, even though it is no longer a multi-release jar. This causes some problems with tools from Java 9 and Java 10. The issue is fixed in version 33.7.1. Sorry for the trouble.

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

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

Javadoc
JDiff
Changelog
  • The Android jar now contains our Proguard configs. (b0668e7)
  • The Guava module-info.class is now present at the root of the jar instead of under a multi-release root. This prevents the jar from containing a file at META-INF/versions/9/OSGI-INF/MANIFEST.MF, which occasionally causes trouble for some users. (230019b)
  • Our Android minSdkVersion is now 24 (Nougat). This follows the minimum of Google's foundational Android libraries, and we expect it to have no practical impact on users. (ea0af87)
  • collect: Changed some ImmutableMap implementations to create a new, lightweight object on each call to view methods like keySet(), rather than creating and storing that object during the first call for reuse later. This is likely to slightly improve performance for some users, but it could lead to regressions in unusual cases, such as repeatedly calling asMultimap().inverse() on the same ImmutableMap instance. (e87d019)
  • net: Added HttpHeaders constant for on-prefetch-activation. (abd06a3)
  • net: Added MediaType constants for application/yaml and application/x-pem-file. (a8e9533, 1d40e27)
  • util.concurrent: Fixed ExecutionSequencer queue stall when delegate executor throws RejectedExecutionException. (8410194)

v33.6.0: 33.6.0

Compare Source

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

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

Javadoc
JDiff
Changelog
  • Migrated some classes from finalize() to PhantomReference in preparation for the removal of finalization. (786b619, 7c6b17c, aeef909)
  • cache: Deprecated CacheBuilder APIs that use TimeUnit in favor of those that use Duration. (73f8b0b)
  • collect: Added toImmutableSortedMap collectors that use the natural comparator. (64d70b9)
  • collect: Changed ConcurrentHashMultiset, ImmutableMultimap, and TreeMultiset deserialization to avoid mutating final fields. In extremely unlikely scenarios in which an instance of that type contains an object that refers back to that instance, this could lead to a broken instance that throws NullPointerException when used. (8240c7e, 0464680)
  • graph: Removed @Beta from all APIs in the package. (dae9566)
  • graph: Added support to Graphs.transitiveClosure() for different strategies for adding self-loops. (2e13df2)
  • graph: Added an asNetwork() view to Graph and ValueGraph. (909c593)
  • hash: Added BloomFilter.serializedSize(). (df9bcc2)
  • net: Added HttpHeaders.CDN_CACHE_CONTROL. (75331b5)

v33.5.0: 33.5.0

Compare Source

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

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

Javadoc
JDiff
Changelog
  • Restored the Automatic-Module-Name to guava-android. (It, unlike, guava-jre, is not a proper module.) (7a04a8a)
  • For users of guava-gwt: Google has moved off GWT internally. We plan to continue to release guava-gwt for users of GWT and J2CL, but the artifact is no longer tested for GWT-specific issues, and we have limited resources to fix any unexpected issues that might arise. While we do not anticipate any specific problems, we can't guarantee how long support will continue.
  • Increased our Android minSdkVersion to 23 (Marshmallow). This follows the minimum of Google's foundational Android libraries, and we expect it to have no practical impact on users. (5c23347)
  • Listed the JSpecify annotations as an optional dependency in our OSGi metadata. (2dfd572)
  • cache: Improved the handling of exceptions from compute functions in Cache.asMap(). (We do still recommend using Caffeine rather than com.google.common.cache.) (087f2c4)
  • collect: Improved Iterators.mergeSorted() to preserve stability for equal elements. (4dc93be)
  • math: Added saturatedAbs methods to IntMath and LongMath. (ed0e518)
  • net: Added image/avif to MediaType. (53344ca)
  • testing: Made CollectorTester available to Android users. (294c251)
  • util.concurrent: Added Striped.custom. (1586eb2)

v33.4.8: 33.4.8

Compare Source

Guava 33.4.8 fixes a problem that we introduced while starting to migrate guava-android off Unsafe in 33.4.7.

Even if you're not upgrading from Guava 33.4.0 or earlier, still read the release notes for Guava 33.4.1. Those release notes contain information about the effects of Guava 33.4.5 and higher on the module system.

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

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

Javadoc
JDiff
Changelog
  • util.concurrent: Removed our VarHandle code from guava-android. While the code was never used at runtime under Android, it was causing problems under the Android Gradle Plugin with a minSdkVersion below 26. To continue to avoid sun.misc.Unsafe under the JVM, guava-android will now always use AtomicReferenceFieldUpdater when run there. (75da924)

v33.4.7: 33.4.7

Compare Source

Prefer to upgrade straight to 33.4.8: 33.4.7 breaks the build of Android apps with a minSdkVersion below 26. We will publish a fixed version soon. This problem is fixed in 33.4.8.

Guava 33.4.7, like 33.4.6, fixes two problems that we introduced while modularizing Guava and migrating off Unsafe in 33.4.5.

Even if you're not upgrading from Guava 33.4.0 or earlier, still read the release notes for Guava 33.4.1. Those release notes contain information about the effects of Guava 33.4.5 and higher on the module system.

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

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

Javadoc
JDiff
Changelog
  • Modified the guava module's dependency on failureaccess to be transitive. Also, modified the guava-testlib module to make its dependency on guava transitive, to remove its dependency on failureaccess, and to add a dependency (transitive) on junit. (63ecdf2)
  • util.concurrent: Modified our fast paths to ensure that they continue to work when run through optimizers, such as those commonly used by Android apps. This fixes problems that some users may have seen since Guava 33.4.5. (b8dcaed, f9eff73)
  • util.concurrent: Changed the guava-android copy of AbstractFuture to try VarHandle before Unsafe, eliminating a warning under newer JDKs. (7336af1)

v33.4.6: 33.4.6

Compare Source

Prefer to upgrade straight to 33.4.8: While Guava 33.4.6 fixes two problems that we introduced while modularizing Guava in 33.4.5, it still contains some small problems with the module system, and it may still cause trouble for optimizers, and the subsequent 33.4.7 breaks the build of Android apps with a minSdkVersion below 26. These problems have been fixed in 33.4.8.

Even if you're not upgrading from Guava 33.4.0 or earlier, still read the release notes for Guava 33.4.1. Those release notes contain information about the effects of Guava 33.4.5 and higher on the module system.

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

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

Javadoc
JDiff
Changelog
  • Removed the extra copy of each class from the Guava jar. The extra copies were an accidental addition from the modularization work in Guava 33.4.5. (40485b9)
  • Fixed annotation-related warnings when using Guava in modular builds. The most common such warning is Cannot find annotation method 'value()' in type 'DoNotMock': .... (7e15ab3)

v33.4.5: 33.4.5

Compare Source

Use Guava 33.4.8, not Guava 33.4.5. 33.4.5 was our first attempt to modularize Guava, but we misconfigured our build, so it:

33.4.5 (and 33.4.6) also may cause trouble for some optimizers (like those commonly used for Android apps), and 33.4.7 breaks the build of Android apps with a minSdkVersion below 26.

All these issues are fixed by release 33.4.8. Sorry for the trouble.

When you read the release notes for 33.4.8, you should also read the release notes for Guava 33.4.1, even if you're not upgrading from Guava 33.4.0 or earlier: Those release notes contain information about the effect of Guava 33.4.5 and higher on the module system.

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

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

Javadoc
JDiff
Changelog

Special thanks to @​sgammon for his modularization efforts.

v33.4.4: 33.4.4

Compare Source

This is one of a series of releases that improve Guava's nullness annotations. For more information, including troubleshooting help, see the release notes for Guava 33.4.1. Most users can update directly to Guava 33.4.8.

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

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

Javadoc
JDiff
Changelog
  • Migrated from Checker Framework annotations to JSpecify annotations. (2cc8c5e)
  • Made our usages of nullness annotations available in our GWT artifact. GWT users will need to upgrade to GWT 2.12.1, which makes GWT as tolerant of Java 8 type-use annotations as it is of other annotations. (80559d2)

v33.4.3: 33.4.3

Compare Source

This is one of a series of releases that improve Guava's nullness annotations. For more information, including troubleshooting help, see the release notes for Guava 33.4.1. Most users can update directly to Guava 33.4.8.

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

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

Javadoc
JDiff
Changelog
  • Migrated from @CheckForNull to the Checker Framework @Nullable. Most tools recognize both annotations, so we expect this to be a no-op in almost all cases. This release removes our dependency on JSR-305. (d997ad9)

v33.4.2: 33.4.2

Compare Source

This is one of a series of releases that improve Guava's nullness annotations. For more information, including troubleshooting help, see the release notes for Guava 33.4.1. Most users can update directly to Guava 33.4.8.

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

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

Javadoc
JDiff
Changelog
  • Changed @ParametricNullness into a no-op for Kotlin and IntelliJ. Before now, it was forcing many usages of type variables to have platform types, which meant that Kotlin couldn't check those usages for nullness errors. With this change, Kotlin can detect more errors. (ae36f57)

v33.4.1: 33.4.1

Compare Source

Today, we are releasing Guava 33.4.1 and a few other 33.4.x releases. All the releases maintain binary compatibility, but they include changes to nullness and the module system that may be disruptive to some users.

Most users can jump straight to 33.4.8 to pick up a few small improvements with no disruption.

If you encounter trouble with 33.4.8, then read on.

Module-system trouble

First, use Guava 33.4.8, not Guava 33.4.5. 33.4.5 was our first attempt to modularize Guava, but we made a few mistakes, so it:

33.4.5 (and 33.4.6) also may cause trouble for some optimizers (like those commonly used for Android apps), and 33.4.7 breaks the build of Android apps with a minSdkVersion below 26.

All these issues are fixed by release 33.4.8. Sorry for the trouble.

Guava 33.4.8 (after a false start in Guava 33.4.5) changes Guava to be a Java module. You can still use Guava without using the module system yourself. However, if your build system automatically recognizes Guava as a module, then you may see errors. As a temporary fix, you can upgrade only to 33.4.4 while you investigate the module problems.

If you see build errors (such as package com.google.common.collect is not visible), try modifying your module-info.java to include requires com.google.common;.

If you see runtime errors, then you may be performing reflection on Guava internals. We recommend not doing this, since Guava internals change frequently, potentially breaking such code. The module system is designed to call attention to this situation, but you can always silence it with --add-opens, passing the module name (com.google.common) and package name from your error message along with the name of the module that is accessing Guava's internals (which is also shown in the error message).

Nullness trouble

Nullness annotations have no effect on Java itself, but they do affect nullness checkers, such as NullAway, the Checker Framework, and Kotlin.

If you encounter only a modest number of nullness errors, we recommend upgrading straight to 33.4.8 or higher, suppressing or fixing the errors to prepare for the change.

For build errors from a Java nullness checker, you can generally silence them with @SuppressWarnings (docs: NullAway, the Checker Framework, Error Prone). Of course, we recommend inspecting at least a few new errors so that you can judge whether the errors are worth fixing instead of just suppressing.

For build errors from Kotlin, there is no supported way to suppress. (If, after reading the instructions here, you believe that one would be valuable, please share your experiences with the Kotlin developers.) You'll instead need to change your code, often in one of the following ways:

  • To insert a null value into a collection, you may need to change the collection's type, like from Multiset<Foo> to Multiset<Foo?>.
    • The same kind of change can be useful for other generic types, like in changing a FutureCallback<Foo> to a FutureCallback<Foo?> so that its onSuccess method can still be declared to accept a Foo?.
  • When using our immutable collections or other null-hostile types, you may need to make the opposite change, like by using ImmutableList<Foo> instead of ImmutableList<Foo?>.
    • If you are writing your own generic API, you may need to restrict your type argument to non-null types. For example, for ImmutableList<T> to be valid, you may need to change your type-parameter declaration from <T> to <T: Any>. Occasionally, you may want to keep the type-parameter declaration as it is but change to using ImmutableList<T & Any>.
  • You can change the nullness of a type by using !! or a cast. These operators sometimes introduce a runtime check where there was not one before.
  • Or there may be better fixes, such as changing the types of your own parameters to forbid null.
Gradual migration

If you encounter a large number of errors when upgrading, then you may wish to upgrade your Guava version incrementally. Guava 33.4.1, 33.4.2, 33.4.3, and 33.4.4 are each one step toward improving Guava's nullness annotations. You may find it easier to upgrade one version at a time. By doing so, you can handle all problems of a particular "kind" at once. Then, once you submit the upgrade, you prevent backsliding of that kind. (Almost all problems should surface in the upgrade to 33.4.1 or the upgrade to 33.4.2.)

If you take this path, you may wish to set -Xjsr305=strict before even the first Guava upgrade. That flag may identify a subset of problems ahead of the Guava changes. Note, however, that it may also cause Kotlin to detect nullness errors in your usages of any other libraries that use custom nullness annotations. If so, the flag would cause you to have to perform a larger cleanup that the Guava upgrade requires, so you'll have to judge whether that flag would be helpful on net.

Temporary emergency fallback option: Disabling current and future checking of Java APIs

In the worst case, it is possible to tell Kotlin not to produce errors for any usages of JSpecify annotations, both those in Guava and those in other libraries (such as Caffeine and the forthcoming Spring Framework 7). You can do this by setting -Xjspecify-annotations=warn. If you are considering this, we recommend instead deferring your upgrade of Guava to give yourself time to work through the nullness errors. We are making an effort not to publish a release with new APIs in the near future, so you should be able to safely defer upgrading for a while. If you do still choose to set the flag, we recommend working to remove it in the future, since it will hide more and more errors as time goes by.

For more help

We monitor for Guava questions on StackOverflow. If you believe that you are seeing a bug in a nullness checker, you can report it to the tool owners (e.g., NullAway, the Checker Framework). If you believe that you are seeing a problem with these instructions or with Guava's nullness annotations, report a bug to us.

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

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

Javadoc
JDiff
Changelog

v33.4.0: 33.4.0

Compare Source

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

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot
renovate-bot requested a review from a team May 2, 2024 16:16
@trusted-contributions-gcf trusted-contributions-gcf Bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label May 2, 2024
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.2.0-jre fix(deps): update dependency com.google.guava:guava to v33.2.1-jre May 31, 2024
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 2598b93 to 42f109e Compare May 31, 2024 19:58
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 42f109e to c067d7e Compare August 17, 2024 00:50
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.2.1-jre fix(deps): update dependency com.google.guava:guava to v33.3.0-jre Aug 17, 2024
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.3.0-jre fix(deps): update dependency com.google.guava:guava to v33.3.1-jre Sep 23, 2024
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from c067d7e to 54af6e1 Compare September 23, 2024 21:33
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 54af6e1 to 98ccd1e Compare December 16, 2024 23:39
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.3.1-jre fix(deps): update dependency com.google.guava:guava to v33.4.0-jre Dec 16, 2024
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.4.0-jre fix(deps): update dependency com.google.guava:guava to v33.4.5-jre Mar 20, 2025
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 98ccd1e to e926dd1 Compare March 20, 2025 01:50
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.4.5-jre fix(deps): update dependency com.google.guava:guava to v33.4.6-jre Mar 25, 2025
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from e926dd1 to 30ac9f1 Compare March 25, 2025 19:51
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 30ac9f1 to 8e1e37a Compare April 8, 2025 19:31
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.4.6-jre fix(deps): update dependency com.google.guava:guava to v33.4.7-android Apr 8, 2025
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.4.7-android fix(deps): update dependency com.google.guava:guava to v33.4.7-jre Apr 9, 2025
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 8e1e37a to 8f9011a Compare April 9, 2025 18:49
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.4.7-jre fix(deps): update dependency com.google.guava:guava to v33.4.8-jre Apr 14, 2025
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 8f9011a to 2634238 Compare April 14, 2025 18:37
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 2634238 to 7cada87 Compare June 15, 2025 22:47
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.4.8-jre fix(deps): update dependency com.google.guava:guava to v33.5.0-jre Sep 18, 2025
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 7cada87 to 2180cb6 Compare September 18, 2025 02:48
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 2180cb6 to c33da84 Compare November 10, 2025 17:58
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from c33da84 to 03150a7 Compare February 2, 2026 15:02
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 03150a7 to 42ececf Compare February 12, 2026 11:56
@renovate-bot
renovate-bot requested a review from a team as a code owner February 12, 2026 11:56
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.5.0-jre fix(deps): update dependency com.google.guava:guava to v33.6.0-jre Apr 14, 2026
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 42ececf to 2108d0e Compare April 14, 2026 20:58
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.6.0-jre fix(deps): update guava monorepo to v33.6.0-jre Jun 2, 2026
@renovate-bot renovate-bot changed the title fix(deps): update guava monorepo to v33.6.0-jre fix(deps): update guava monorepo Jun 22, 2026
@renovate-bot renovate-bot changed the title fix(deps): update guava monorepo fix(deps): update dependency com.google.guava:guava to v33.6.0-jre Jun 25, 2026
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from 2108d0e to cde88e7 Compare October 10, 2026 20:52
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.6.0-jre fix(deps): update dependency com.google.guava:guava to v33.7.2-jre Oct 10, 2026
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.7.2-jre fix(deps): update dependency com.google.guava:guava to v33.7.2 Nov 2, 2026
@renovate-bot renovate-bot changed the title fix(deps): update dependency com.google.guava:guava to v33.7.2 fix(deps): update dependency com.google.guava:guava to v33.8.0 Nov 2, 2026
@renovate-bot
renovate-bot force-pushed the renovate/guava-monorepo branch from cde88e7 to 295d786 Compare November 2, 2026 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

kokoro:force-run Add this label to force Kokoro to re-run the tests.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@renovate-bot