This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/storm-client.version-2.8.3
in repository https://gitbox.apache.org/repos/asf/stormcrawler.git
omit 84081420 Bump storm-client.version from 2.8.2 to 2.8.3
add efa33716 Bump okhttp.version from 5.2.1 to 5.3.0 (#1708)
add ef989190 Bump com.ibm.icu:icu4j from 77.1 to 78.1 (#1713)
add 6747acf4 Bump junit.version from 6.0.0 to 6.0.1 (#1712)
add 65e5e478 Bump aws.version from 1.12.792 to 1.12.793 (#1711)
add 6040f85e Bump com.puppycrawl.tools:checkstyle from 12.0.1 to 12.1.1
(#1710)
add e1ccc019 Bump storm-client.version from 2.8.2 to 2.8.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 (84081420)
\
N -- N -- N
refs/heads/dependabot/maven/storm-client.version-2.8.3 (e1ccc019)
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:
core/pom.xml | 4 ++--
external/aws/pom.xml | 2 +-
pom.xml | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
