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/chromedriver-119.0.1
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git
discard b586098094 Bump chromedriver in /experimental/traffic-portal
add f7f086d495 Bump @babel/traverse from 7.21.5 to 7.23.2 in
/experimental/traffic-portal (#7842)
add 4bc1b34e35 Bump crypto-js from 4.1.1 to 4.2.0 in
/experimental/traffic-portal (#7851)
add 64fc16bf76 Bump browserify-sign from 4.2.1 to 4.2.2 in /traffic_portal
(#7854)
add c9b80f99d0 Bump chromedriver from 117.0.3 to 119.0.1 in
/traffic_portal/test/integration (#7864)
add c24615daa9 Bump chromedriver 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 (b586098094)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/experimental/traffic-portal/chromedriver-119.0.1
(c24615daa9)
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:
experimental/traffic-portal/package-lock.json | 270 +++--
traffic_portal/package-lock.json | 1291 ++++++++++-----------
traffic_portal/test/integration/package-lock.json | 54 +-
traffic_portal/test/integration/package.json | 2 +-
4 files changed, 801 insertions(+), 816 deletions(-)
