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 dae820674 Regenerate license files after dependency changes
    omit 60c10100f Merge pull request #8753 from 
apache/dependabot/npm_and_yarn/storm-webapp/2.x/cypress-15.16.0
    omit ab6ac714a Merge pull request #8755 from 
apache/dependabot/npm_and_yarn/storm-webapp/2.x/js-yaml-4.2.0
    omit 5df0c6d99 Merge pull request #8764 from 
apache/dependabot/maven/2.x/activemq.version-6.2.6
    omit 24a90d90b Bump js-yaml from 4.1.1 to 4.2.0 in /storm-webapp
    omit 0fe11c7f7 Bump cypress from 15.15.0 to 15.16.0 in /storm-webapp
    omit fa56b9113 Bump activemq.version from 6.2.5 to 6.2.6
     add 76bc3af64 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   (dae820674)
            \
             N -- N -- N   refs/heads/update-license-files-2.x (76bc3af64)

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            |  2 +-
 pom.xml                        |  4 +-
 storm-webapp/package-lock.json | 93 ++++++++++++++++++++++++++++++------------
 storm-webapp/package.json      |  4 +-
 4 files changed, 72 insertions(+), 31 deletions(-)

Reply via email to