Skip to content

chore(deps): bump torch from 2.11.0 to 2.12.0 #187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): bump torch from 2.11.0 to 2.12.0 #187

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[build-system]
# Note: The torch version here is the default. When building releases,
# use tools/release.sh with --torch-version to specify different versions
requires = ["setuptools>=68.0.0", "pyyaml", "torch==2.11.0", "toml"]
requires = ["setuptools>=68.0.0", "pyyaml", "torch==2.12.0", "toml"]
build-backend = "setuptools.build_meta"

[project]
Expand Down Expand Up @@ -29,7 +29,7 @@ dependencies = [
"pytz>=2025.2",
"prometheus-client>=0.21.1",
"py-grpc-prometheus>=0.8.0",
"torch==2.11.0",
"torch==2.12.0",
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep Bazel libtorch pin in sync with torch dependency

Updating pyproject.toml to torch==2.12.0 without updating Bazel’s libtorch archive leaves the repo on mixed PyTorch C++ ABIs: Python/build deps now resolve 2.12, but BUILD_CORE=1 still compiles core/daemon against torch-2.11.0+cu128 from MODULE.bazel (see http_archive(name = "libtorch") around lines 124-130). In the documented source build flow (BUILD_CORE=1 BUILD_EXTENSION=1 python setup.py build_ext), this mismatch can produce undefined-symbol/dlopen failures at import/runtime. The torch bump should include the matching Bazel libtorch update in the same commit.

Useful? React with 👍 / 👎.

"protobuf==6.31.1",
# OpenTelemetry is a required dependency. No automatic downgrade.
"opentelemetry-api>=1.36.0",
Expand Down
Loading