This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch update-license-files
in repository https://gitbox.apache.org/repos/asf/storm.git
discard 78686a7e0 Regenerate license files after dependency changes
add 50e52b4c1 build(deps): bump js-yaml from 5.4.2 to 5.5.0 in
/storm-webapp
add 8631ccb50 Merge pull request #9236 from
apache/dependabot/npm_and_yarn/storm-webapp/js-yaml-5.5.0
add 502d98086 build(deps): bump datatables.net-dt from 3.1.2 to 3.1.4 in
/storm-webapp
add 7b8eab40d Merge pull request #9237 from
apache/dependabot/npm_and_yarn/storm-webapp/datatables.net-dt-3.1.4
add 3690eff7d build(deps-dev): bump cypress from 16.1.1 to 16.2.1 in
/storm-webapp
add 975ff31e2 Merge pull request #9238 from
apache/dependabot/npm_and_yarn/storm-webapp/cypress-16.2.1
add 5c200c001 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 (78686a7e0)
\
N -- N -- N refs/heads/update-license-files (5c200c001)
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:
storm-webapp/package-lock.json | 52 +++++++++++++++++++++++++++---------------
storm-webapp/package.json | 6 ++---
2 files changed, 37 insertions(+), 21 deletions(-)