Bump com.google.guava:guava from 32.0.1-jre to 32.1.0-jre

[dependabot[bot]]

Bumps com.google.guava:guava from 32.0.1-jre to 32.1.0-jre.

Release notes

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

32.1.0

Warning: Gradle metadata is broken

We made a mistake in our release script, so the new Gradle metadata (discussed below) is broken. We'll publish a 32.1.1 release with the fix. Sorry for the trouble and for the need for another quick patch release. We recommend waiting for us to release 32.1.1 if you use Gradle or if you publish a library whose users might use Gradle.

Maven

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

Jar files

• 32.1.0-jre.jar
• 32.1.0-android.jar

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

• failureaccess-1.0.1.jar

Javadoc

• 32.1.0-jre
• 32.1.0-android

JDiff

• 32.1.0-jre vs. 32.0.1-jre
• 32.1.0-android vs. 32.0.1-android
• 32.1.0-android vs. 32.1.0-jre

Changelog

Gradle Module Metadata

Warning: We made a mistake in our release script, so this is broken. We recommend waiting for us to release 32.1.1 if you use Gradle or if you publish a library whose users might use Gradle.

The Gradle team has contributed a metadata file for Guava. If you use Gradle 6 or higher, you will see better handling of two kinds of dependency conflicts, plus another small feature related to our dependencies:

Selecting the appropriate flavor

When Gradle automatically selects the newest version of Guava in your dependency graph, it will now also select the appropriate flavor (-android or -jre) based on whether you project targets Android or not. For example, if you depend on 32.1.0-android and 30.0-jre, Gradle will select 32.1.0-jre. This is the version most likely to be compatible with all your dependencies.

In the unusual event that you need to override Gradle's choice of flavor, you can do so as follows:

... (truncated)

Commits

• See full diff 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)

[asaarilahti]

I guess makes sense to wait for 32.1.1 as per the recommendation.

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.