This is an automated email from the ASF dual-hosted git repository.
Yicong-Huang pushed a change to branch
backport/6908-update-dependency-ajv-to-v8-18-0-securit-v1.2
in repository https://gitbox.apache.org/repos/asf/texera.git
omit a291a9fab3 fix(v1.2): resolve backport conflict in
frontend/LICENSE-binary
omit 12520a3f50 fix(deps, frontend): update dependency ajv to v8.18.0
[security] (#6908)
add fd5f487074 fix(deps, ci, v1.2): bump sbt/setup-sbt to v1.5.2 for ASF
actions allowlist (#6990)
add 7148033fdc fix(deps, frontend): update dependency ajv to v8.18.0
[security] (#6908)
add bb301e3681 fix(v1.2): resolve backport conflict in
frontend/LICENSE-binary
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 (a291a9fab3)
\
N -- N -- N
refs/heads/backport/6908-update-dependency-ajv-to-v8-18-0-securit-v1.2
(bb301e3681)
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:
.github/workflows/build-and-push-images.yml | 6 +++---
.github/workflows/build.yml | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
