This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/traffic_portal/app/src/semver-5.7.2
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git
omit 5014326ca2 Bump semver from 5.7.1 to 5.7.2 in /traffic_portal/app/src
add 205d7bb61b Bump semver from 5.7.1 to 5.7.2 in
/experimental/traffic-portal (#7632)
add 75ec56fa1b Bump tough-cookie from 4.1.2 to 4.1.3 in
/experimental/traffic-portal (#7624)
add c81e42775e Bump semver from 5.7.1 to 5.7.2 in /traffic_portal/app/src
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 (5014326ca2)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/traffic_portal/app/src/semver-5.7.2
(c81e42775e)
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 | 468 ++++++++++++++++----------
1 file changed, 287 insertions(+), 181 deletions(-)
