build(deps): bump guava from 32.0.1-jre to 32.1.1-jre

[dependabot]

Bumps guava from 32.0.1-jre to 32.1.1-jre.

Release notes

Sourced from guava's releases.

32.1.1

Maven

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

Jar files

• 32.1.1-jre.jar
• 32.1.1-android.jar

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

• failureaccess-1.0.1.jar

Javadoc

• 32.1.1-jre
• 32.1.1-android

JDiff

• 32.1.1-jre vs. 32.1.0-jre
• 32.1.1-android vs. 32.1.0-android
• 32.1.1-android vs. 32.1.1-jre

Changelog

• Fixed our broken Gradle metadata from 32.1.0. Sorry again for the trouble. If you use Gradle, please still read the release notes from that version: You may still see errors from the new checking that the metadata enables, and the release notes discuss how to fix those errors.

32.1.0

Warning: Gradle metadata is broken. Read these notes, but skip to 32.1.1

We made a mistake in our release script, so the new Gradle metadata (discussed below) is broken in 32.1.0. Sorry for the trouble and for the need for another quick patch release. We recommend upgrading straight to release 32.1.1, especially if you use Gradle or if you publish a library whose users might use Gradle. Still, read the release notes below if you use Gradle, since the fixed Gradle metadata in 32.1.1 may still require action on your part.

Maven

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

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

[aikebah]

@jeremylong @nhumblot any of you in an ecosystem where the effects of the guava gradle metadata can be easily checked with a local snapshot build of the gradle plugin and this branch of the ODC project before integrating this into the main codebase? See the guava release notes (under 32.1.0) on some symptoms that might occur depending on the project's guava versions (transitively) referenced by dependencies/plugins.

[nhumblot]

@aikebah 👋

I don't have such kind of environment unfortunately but I can look to reproduce one?

[dependabot]

Superseded by #5850.