This is an automated email from the ASF dual-hosted git repository.
xuang7 pushed a change to branch
backport/8494-update-dependency-angular-core-to-v21-2-v1.2
in repository https://gitbox.apache.org/repos/asf/texera.git
discard 441d9393c4 fix(deps, frontend): update dependency @angular/core to
v21.2.20 (#8494)
add e7f5fbfd59 fix(deps, frontend, v1.2): update dependency
@angular/common to v21.2.20 (#8657)
add 1c39c0412d fix(amber, v1.2): refresh transitive versions in
LICENSE-binary-python (#8653)
add eba7581b31 fix(deps, frontend): update dependency @angular/core to
v21.2.20 (#8494)
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 (441d9393c4)
\
N -- N -- N
refs/heads/backport/8494-update-dependency-angular-core-to-v21-2-v1.2
(eba7581b31)
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:
amber/LICENSE-binary-python | 70 ++++++++++++++++++++++-----------------------
frontend/LICENSE-binary | 2 +-
frontend/package.json | 2 +-
frontend/yarn.lock | 12 ++++----
4 files changed, 43 insertions(+), 43 deletions(-)
