This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.jgrapht-jgrapht-core-1.5.3
in repository https://gitbox.apache.org/repos/asf/storm.git
discard 6b2029912 Bump org.jgrapht:jgrapht-core from 0.9.0 to 1.5.3
add c4d2d02a4 Bump org.apache.hbase:hbase-client from 2.6.4-hadoop3 to
2.6.5-hadoop3
add 25d028bc1 Bump org.rocksdb:rocksdbjni from 10.10.1 to 10.10.1.1
add bf970558e Bump bouncycastle.version from 1.83 to 1.84
add 321562d17 Bump org.apache.commons:commons-configuration2 from 2.13.0
to 2.14.0
add b46e00357 Bump com.google.guava:guava from 33.5.0-jre to 33.6.0-jre
add 318072787 Bump org.jgrapht:jgrapht-core from 0.9.0 to 1.5.3
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (6b2029912)
\
N -- N -- N
refs/heads/dependabot/maven/org.jgrapht-jgrapht-core-1.5.3 (318072787)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
pom.xml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
