This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch 
dependabot/npm_and_yarn/experimental/traffic-portal/multi-d66d039ac5
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git


 discard c075d94bb3 Bump serve-static and express in 
/experimental/traffic-portal
     add ff386e747b Bump send and express in /traffic_portal (#8076)
     add 10ee38ef36 Bump send and express in /traffic_portal/app/src (#8075)
     add de2784c245 Bump elliptic from 6.5.4 to 6.5.7 in /traffic_portal (#8064)
     add b5c65c5eb8 Bump serve-static and express in 
/experimental/traffic-portal

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   (c075d94bb3)
            \
             N -- N -- N   
refs/heads/dependabot/npm_and_yarn/experimental/traffic-portal/multi-d66d039ac5 
(b5c65c5eb8)

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:
 traffic_portal/app/src/package-lock.json |  461 +++++++++----
 traffic_portal/app/src/package.json      |    2 +-
 traffic_portal/package-lock.json         | 1067 +++++++++++++-----------------
 traffic_portal/package.json              |    2 +-
 4 files changed, 811 insertions(+), 721 deletions(-)

Reply via email to