This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/pip/core/amber/scikit-learn-1.5.0
in repository https://gitbox.apache.org/repos/asf/texera.git
omit 5637f974bd chore(deps): bump scikit-learn from 1.4.0 to 1.5.0 in
/core/amber
add bc260178be chore(deps): bump torch from 2.4.1 to 2.8.0 and
typing_extensions from 4.9.0 to 4.10.0 (#3800)
add e6977b3f96 chore(deps): bump scikit-learn from 1.4.0 to 1.5.0 in
/core/amber
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 (5637f974bd)
\
N -- N -- N
refs/heads/dependabot/pip/core/amber/scikit-learn-1.5.0 (e6977b3f96)
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:
core/amber/operator-requirements.txt | 2 +-
core/amber/requirements.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
