Sourced fromcom.google.guava:guava's releases.

32.0.0

Maven

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

Jar files

• 32.0.0-jre.jar
• 32.0.0-android.jar

Guava requiresone runtime dependency, which you can download here:

• failureaccess-1.0.1.jar

Javadoc

• 32.0.0-jre
• 32.0.0-android

JDiff

• 32.0.0-jre vs. 31.1-jre
• 32.0.0-android vs. 31.1-android
• 32.0.0-android vs. 32.0.0-jre

Changelog

Security fixes

• ReimplementedFiles.createTempDir andFileBackedOutputStream to further addressCVE-2020-8908 (#4011) andCVE-2023-2976 (#2575). (feb83a1c8f)

WhileCVE-2020-8908 was officially closed when we deprecatedFiles.createTempDir inGuava 30.0, we've heard from users that even recent versions of Guava have been listed as vulnerable inother databases of security vulnerabilities. In response, we've reimplemented the method (and the very rarely usedFileBackedOutputStream class, which had a similar issue) to eliminate the insecure behavior entirely. This change could technically affect users in a number of different ways (discussed under "Incompatible changes" below), but in practice, the only problem users are likely to encounter is with Windows. If you are using those APIs under Windows, you should skip 32.0.0 and go straight to32.0.1 which fixes the problem. (Unfortunately, we didn't think of the Windows problem until after the release. And while wewarn thatcommon.io in particular may not work under Windows, we didn't intend to regress support.) Sorry for the trouble.

Incompatible changes

Although this release bumps Guava's major version number, it makesno binary-incompatible changes to theguava artifact.

One change could cause issues for Widows users, and a few other changes could cause issues for users in more usual situations:

• The new implementations ofFiles.createTempDir andFileBackedOutputStreamthrow an exception under Windows. This is fixed in32.0.1. Sorry for the trouble.
• guava-gwt nowrequires GWT2.10.0.
• This release makes a binary-incompatible change to a@Beta API in theseparate artifactguava-testlib. Specifically, we changed the return type ofTestingExecutors.sameThreadScheduledExecutor toListeningScheduledExecutorService. The old return type was a package-private class, which caused the Kotlin compiler to produce warnings. (dafaa3e435)

... (truncated)

• See full diff incompare view

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)
  You can disable automated security fix PRs for this repo from theSecurity Alerts page.