This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch dependabot/uv/torch-2.13.0
in repository https://gitbox.apache.org/repos/asf/mahout.git
omit 1f3bb5d07 chore(deps-dev): bump torch from 2.9.0 to 2.13.0
add 794404510 chore(deps): update website dependencies (#1459)
add 6c967cc11 chore(deps): bump pyasn1 from 0.6.3 to 0.6.4 (#1453)
add 2b23495fe chore(deps-dev): bump torch from 2.12.0 to 2.13.0 in
/qdp/qdp-python (#1444)
add 8ea064c5b chore(deps): bump pillow from 12.2.0 to 12.3.0 (#1446)
add f98c56fd1 chore(deps-dev): bump setuptools from 80.9.0 to 83.0.0
(#1452)
add b5fd3d4c9 chore(deps): bump quinn-proto from 0.11.14 to 0.11.16 in
/qdp (#1455)
add c24221c2f chore(deps-dev): bump torch from 2.9.0 to 2.13.0
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 (1f3bb5d07)
\
N -- N -- N refs/heads/dependabot/uv/torch-2.13.0 (c24221c2f)
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:
qdp/Cargo.lock | 90 ++-
qdp/qdp-python/uv.lock | 80 +-
uv.lock | 172 ++--
website/docusaurus.config.ts | 2 +-
website/package-lock.json | 1822 ++++++++++++++++++++++++------------------
website/package.json | 31 +-
website/tsconfig.json | 14 +-
7 files changed, 1270 insertions(+), 941 deletions(-)
