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/test/integration/axios-0.28.0
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git
discard 786f8104dd Bump axios from 0.21.2 to 0.28.0 in
/traffic_portal/test/integration
add dc995a950e Update Go version to 1.22.1 (#7955)
add 0839096065 Fix incorrect display of delivery services for an ORG
server (#7957)
add 26a2f6a5e8 Update Chromedriver Versions (#7963)
add f16e3ad33e Bump axios from 0.21.2 to 0.28.0 in
/traffic_portal/test/integration
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 (786f8104dd)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/traffic_portal/test/integration/axios-0.28.0
(f16e3ad33e)
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:
.env | 2 +-
CHANGELOG.md | 3 ++-
GO_VERSION | 2 +-
experimental/traffic-portal/package-lock.json | 8 ++++----
experimental/traffic-portal/package.json | 2 +-
.../api/v3/servers_id_deliveryservices_test.go | 3 +--
.../api/v4/servers_id_deliveryservices_test.go | 3 +--
.../api/v5/servers_id_deliveryservices_test.go | 3 +--
.../deliveryservice/servers/servers.go | 24 +++++++++++++++-------
traffic_portal/test/integration/package-lock.json | 14 ++++++-------
traffic_portal/test/integration/package.json | 2 +-
11 files changed, 37 insertions(+), 29 deletions(-)
