This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/frontend/xmldom/xmldom-0.8.13
in repository https://gitbox.apache.org/repos/asf/texera.git
omit 3355cf4715 chore(deps): bump @xmldom/xmldom from 0.8.10 to 0.8.13 in
/frontend
add ea110e798a chore(dependencies): pin torch to CPU wheel on Linux x86_64
(#4473)
add 7486f61e17 feat(frontend): fix console message display issue (#4483)
add 7ccc97a1d9 fix(dependencies): remove jschardet from the frontend
dependency graph (#4480)
add 0091658b9e chore(deps): bump @xmldom/xmldom from 0.8.10 to 0.8.13 in
/frontend
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 (3355cf4715)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/frontend/xmldom/xmldom-0.8.13 (0091658b9e)
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/operator-requirements.txt | 7 ++++++-
frontend/.yarnrc.yml | 5 -----
frontend/package.json | 3 ++-
.../console-frame/console-frame.component.scss | 24 +++++++++++++---------
.../tools/jschardet-stub/index.js | 11 ++++++++--
frontend/tools/jschardet-stub/package.json | 7 +++++++
frontend/yarn.lock | 9 ++++----
7 files changed, 42 insertions(+), 24 deletions(-)
copy
amber/src/main/scala/org/apache/texera/amber/engine/architecture/controller/execution/ChannelExecution.scala
=> frontend/tools/jschardet-stub/index.js (66%)
create mode 100644 frontend/tools/jschardet-stub/package.json
