This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch update-license-files-2.x
in repository https://gitbox.apache.org/repos/asf/storm.git
discard f3a38656d Regenerate license files after dependency changes
add fe895a02d Bump cytoscape from 3.33.2 to 3.33.3 in /storm-webapp (#8619)
add ccb7ffccf Bump prometheus.client.version from 1.5.1 to 1.6.1 (#8614)
add 8443d1e7c Bump commons-codec:commons-codec from 1.21.0 to 1.22.0
(#8607)
add aa5ad17fd Bump org.apache:apache from 37 to 38 (#8604)
add 4a9b0f684 Bump vis-data from 8.0.3 to 8.0.4 in /storm-webapp (#8602)
add ecd86dbd2 Bump spring.version from 7.0.6 to 7.0.7 (#8601)
add bc9cdf6d0 Regenerate license files after dependency changes
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 (f3a38656d)
\
N -- N -- N refs/heads/update-license-files-2.x (bc9cdf6d0)
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:
DEPENDENCY-LICENSES | 44 +++++++++++++++----------------
LICENSE-binary | 2 +-
examples/storm-jms-examples/pom.xml | 2 +-
external/storm-metrics-prometheus/pom.xml | 2 +-
pom.xml | 4 +--
storm-webapp/package-lock.json | 18 ++++++-------
storm-webapp/package.json | 4 +--
7 files changed, 38 insertions(+), 38 deletions(-)
