This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/examples/commons-logging-commons-logging-1.4.0
in repository https://gitbox.apache.org/repos/asf/storm.git
omit 4674659d3 build(deps): bump commons-logging:commons-logging in
/examples
add d4b894f30 build(deps-dev): bump webpack from 5.107.2 to 5.108.3 in
/storm-webapp (#8854)
add bd295cb9c build(deps): bump activemq.version from 6.2.6 to 6.2.7
(#8827)
add 25fca2e12 build(deps): bump commons-logging:commons-logging in
/examples
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 (4674659d3)
\
N -- N -- N
refs/heads/dependabot/maven/examples/commons-logging-commons-logging-1.4.0
(25fca2e12)
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 | 2 +-
storm-webapp/package-lock.json | 111 +++++++++++++++++++++++++++++++++--------
storm-webapp/package.json | 2 +-
3 files changed, 91 insertions(+), 24 deletions(-)
