This is an automated email from the ASF dual-hosted git repository.
rzo1 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/storm.git
The following commit(s) were added to refs/heads/master by this push:
new 9be312825 build(deps): bump com.google.guava:guava from 33.6.0-jre to
33.7.1-jre in /examples (#9052)
9be312825 is described below
commit 9be3128251041330b5e32bb1b455cdc6ba3c782f
Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
AuthorDate: Tue Sep 1 11:40:09 2026 +0200
build(deps): bump com.google.guava:guava from 33.6.0-jre to 33.7.1-jre in
/examples (#9052)
* build(deps): bump com.google.guava:guava in /examples
Bumps [com.google.guava:guava](https://github.com/google/guava) from
33.6.0-jre to 33.7.1-jre.
- [Release notes](https://github.com/google/guava/releases)
- [Commits](https://github.com/google/guava/commits)
---
updated-dependencies:
- dependency-name: com.google.guava:guava
dependency-version: 33.7.1-jre
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
* Pin org.jspecify:jspecify so the daemon and worker classpaths agree
Guava 33.7.1-jre moves its jspecify transitive from 1.0.0 to 1.0.1. JUnit 6
also declares org.jspecify:jspecify, at a nearer depth than Guava, so the
two
classpaths of the binary distribution mediated to different versions: lib
(daemon) kept jspecify 1.0.0 while lib-common (worker) resolved 1.0.1, and
dedup-libs refused to assemble a distribution with shadowed jars.
Manage jspecify centrally so every module resolves the same version
regardless
of which path it arrives on, and keep the property next to guava.version so
the
two stay coupled. Refresh the guava and jspecify entries in LICENSE-binary
and
DEPENDENCY-LICENSES to match.
---------
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot]
<49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Richard Zowalla <[email protected]>
