Bump torch from 2.12.1 to 2.13.0 - #1192
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [torch](https://github.com/pytorch/pytorch) from 2.12.1 to 2.13.0. - [Release notes](https://github.com/pytorch/pytorch/releases) - [Changelog](https://github.com/pytorch/pytorch/blob/main/RELEASE.md) - [Commits](pytorch/pytorch@v2.12.1...v2.13.0) --- updated-dependencies: - dependency-name: torch dependency-version: 2.13.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
✅ Deploy Preview for neo4j-graph-data-science-client canceled.
|
FlorentinD
added a commit
that referenced
this pull request
Jul 27, 2026
Batches the applicable open dependabot bumps into one commit so that pyproject.toml and uv.lock stay consistent: - mypy 2.2.0 -> 2.3.0 (#1178) - tox 4.56.2 -> 4.58.0 (#1193) - sphinx 7.3.7 -> 8.1.3 (#1179) - nbclient 0.10.4 -> 0.11.0 (#1180) - nbconvert 7.16.6 -> 7.17.1 (#1093) Verified: ruff, mypy and the unit tests pass; the sphinx API docs still build with -W. Sphinx 8 changes no rendered output beyond a doctools.js cache-bust hash and one core aria-label; enum-tools autoenum and autodoc_pydantic render unchanged. nbconvert produces byte-identical asciidoc for the tutorial notebooks. The torch 2.12.1 -> 2.13.0 bump (#1192, #1186) is left out: the PyG wheel index for torch 2.13.0 ships only pyg_lib, no torch-scatter/torch-sparse wheels, so notebook-ci would have to build those from source. Also switch dependabot from the pip to the uv ecosystem, so future PRs update pyproject.toml and uv.lock together instead of opening duplicate pip/uv PRs that leave the lockfile stale. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
FlorentinD
added a commit
that referenced
this pull request
Jul 27, 2026
Batches the applicable open dependabot bumps into one commit so that pyproject.toml and uv.lock stay consistent: - mypy 2.2.0 -> 2.3.0 (#1178) - tox 4.56.2 -> 4.58.0 (#1193) - sphinx 7.3.7 -> 8.1.3 (#1179) - nbclient 0.10.4 -> 0.11.0 (#1180) - nbconvert 7.16.6 -> 7.17.1 (#1093) Verified: ruff, mypy and the unit tests pass; the sphinx API docs still build with -W. Sphinx 8 changes no rendered output beyond a doctools.js cache-bust hash and one core aria-label; enum-tools autoenum and autodoc_pydantic render unchanged. nbconvert produces byte-identical asciidoc for the tutorial notebooks. The torch 2.12.1 -> 2.13.0 bump (#1192, #1186) is left out: the PyG wheel index for torch 2.13.0 ships only pyg_lib, no torch-scatter/torch-sparse wheels, so notebook-ci would have to build those from source. Also switch dependabot from the pip to the uv ecosystem, so future PRs update pyproject.toml and uv.lock together instead of opening duplicate pip/uv PRs that leave the lockfile stale. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
FlorentinD
added a commit
that referenced
this pull request
Aug 7, 2026
* Apply dependabot dependency updates Batches the applicable open dependabot bumps into one commit so that pyproject.toml and uv.lock stay consistent: - ruff 0.15.20 -> 0.16.1 (#1203 proposed 0.16.0; 0.16.1 is the latest and adds only bug fixes and preview-rule changes on top of it) - types-setuptools 83.0.0.20260706 -> 83.0.0.20260724 (#1202) - types-python-dateutil 2.9.0.20260518 -> 2.9.0.20260716 (#1201) - types-tqdm 4.68.0.20260608 -> 4.70.0.20260805 (#1199) - neo4j-viz 1.6.0 -> 1.7.0 (#1200, lock only; the >=1.6.0 floor stays put so the constraint remains permissive for library consumers) - aiohttp 3.14.1 -> 3.14.3 (#1214) - cryptography 49.0.0 -> 50.0.0 (#1216) Also re-resolves the whole lockfile with `uv lock --upgrade` rather than only the packages dependabot filed PRs for, which moves 48 packages in total. The ones worth noting beyond the list above: pyarrow 24.0.0 -> 25.0.0, tqdm 4.68.4 -> 4.70.0 and multimethod 2.0.2 -> 2.1 are runtime dependencies; pandas goes 3.0.3 -> 3.0.5; twine 6.2.0 -> 7.0.0 affects the publish group only; and sphinx-autodoc-typehints 2.3.0 -> 3.0.1 plus alabaster 0.7.16 -> 1.0.0 are major bumps but transitive only, since neither is in the sphinx extension list and the theme is the vendored neo4j one. pyarrow 25 needs the mypy.ini change. It withdraws the py.typed marker and inline annotations that 24 shipped (apache/arrow#50168), because those annotations were incomplete and broke type checkers on submodules such as pyarrow.compute (apache/arrow#49831). Without py.typed, strict mypy reports 26 import-untyped errors across the arrow client. Restoring ignore_missing_imports for pyarrow reverts exactly what #1164 removed when it adopted pyarrow 24, so this is the pre-24 behaviour rather than a new relaxation. pyarrow-stubs is not a usable alternative: it targets the pyarrow 20 API and yields 35 errors in 7 files. The stanza can go once upstream ships complete annotations (apache/arrow#32609). Verified: ruff 0.16.1 reformats nothing and reports no new findings (the 0.16 default-rule expansion does not reach us because tool.ruff.lint.select is explicit, and the new markdown formatting is excluded by include), mypy is clean, and the 632 unit tests pass. The sphinx API docs still build with -W and the rendered HTML is byte-identical to a pre-upgrade build, so the sphinx transitive majors change no output. nbconvert still produces byte-identical asciidoc for the tutorial notebooks despite the mistune 3.3.2 -> 3.3.4 bump. The torch 2.12.1 -> 2.13.0 bump (#1186, #1192) is still left out, for the same reason as in #1196 and re-checked today: the PyG wheel index for torch-2.13.0+cpu ships only pyg_lib, no torch-scatter or torch-sparse wheels, so notebook-ci would fall back to building those from source. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Drop older pyarrow version --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps torch from 2.12.1 to 2.13.0.
Release notes
Sourced from torch's releases.
... (truncated)
Commits
cf30153[release/2.13] Strip +PTX from CUDA arch list on release/RC builds (#188914) ...3e3e24b[release/2.13] Restrict cuda-bindings to Python < 3.15 for CUDA 12.9 builds (...7986b06[release/2.13] Bump binary build timeout 280 -> 400 minutes (#188551)0bdbc26[release/2.13] Add CUDA 12.9 to TORCH_CUDA_ARCH_LIST tables (#188443)9cabb45[release/2.13] Update manywheel docker image pin to 78e737ad (#188409)78e737a[release/2.13] Revert "Tighten generalized scatter graph target (#184075)" (#...0bb9b5b[release/2.13] Revert "dynamo: round-trip torch.cuda.stream ctx mgr across gr...aaac2bf[release/2.13] Revert "[Reland] Port D104346887/PR 182675 for index_add fast ...9330813Fix build_with_debinfo.py broken by CONFIGURE_DEPENDS globbing (#188192)4e077a7Remove setuptools upper bound (#188190)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)