Files
langchain/libs
dependabot[bot] dc26ca5035 chore: bump torch from 2.12.1 to 2.13.0 in /libs/text-splitters (#38946)
Bumps [torch](https://github.com/pytorch/pytorch) from 2.12.1 to 2.13.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pytorch/pytorch/releases">torch's
releases</a>.</em></p>
<blockquote>
<h1>PyTorch 2.13.0 Release Notes</h1>
<ul>
<li><a
href="https://github.com/pytorch/pytorch/blob/HEAD/#highlights">Highlights</a></li>
<li><a
href="https://github.com/pytorch/pytorch/blob/HEAD/#backwards-incompatible-changes">Backwards
Incompatible Changes</a></li>
<li><a
href="https://github.com/pytorch/pytorch/blob/HEAD/#deprecations">Deprecations</a></li>
<li><a
href="https://github.com/pytorch/pytorch/blob/HEAD/#new-features">New
Features</a></li>
<li><a
href="https://github.com/pytorch/pytorch/blob/HEAD/#improvements">Improvements</a></li>
<li><a
href="https://github.com/pytorch/pytorch/blob/HEAD/#bug-fixes">Bug
fixes</a></li>
<li><a
href="https://github.com/pytorch/pytorch/blob/HEAD/#performance">Performance</a></li>
<li><a
href="https://github.com/pytorch/pytorch/blob/HEAD/#documentation">Documentation</a></li>
<li><a
href="https://github.com/pytorch/pytorch/blob/HEAD/#developers">Developers</a></li>
</ul>
<h1>Highlights</h1>
<!-- raw HTML omitted -->
<p>For more details about these highlighted features, you can look at
the release blogpost. Below are the full release notes for this
release.</p>
<h1>Tracked Regressions</h1>
<h3>ROCm wheels break <code>torch.compile</code> on CPU in environments
without a GPU</h3>
<p>Running a <code>torch==2.13.0+rocm7.2</code> wheel in an environment
where no GPU is available (<code>torch.cuda.is_available()</code> is
<code>False</code>) breaks <code>torch.compile</code> on the CPU path:
the first compile raises <code>RuntimeError: Can't detect vectorized ISA
for CPU</code> (<a
href="https://redirect.github.com/pytorch/pytorch/issues/189194">#189194</a>).
This is a regression from <code>torch==2.12.1+rocm7.2</code>, which
compiles CPU code fine (detecting e.g. <code>VecAVX2</code>) in the same
setup. The 2.13 ROCm wheel appears to rely on something present in the
ROCm builder image to detect the CPU vectorized ISA, so it works when
run on a ROCm image but fails on a plain CPU-only image.</p>
<p>Workaround: run the <code>+rocm</code> wheel on a ROCm image, or
install a standard CPU/CUDA build for GPU-less environments.</p>
<h1>Backwards Incompatible Changes</h1>
<ul>
<li>
<p>Stop building CPython 3.13t (free-threaded) binaries (<a
href="https://redirect.github.com/pytorch/pytorch/issues/182951">#182951</a>)</p>
<p>Upstream <code>pypa/manylinux</code> removed CPython 3.13t
(free-threaded) on 2026-05-07, because 3.13t
was experimental and has been superseded by the now-non-experimental
CPython 3.14t. As a result,
PyTorch 2.13 no longer ships <code>cp313t</code> wheels (Linux, Triton,
and related artifacts). Users on the
free-threaded interpreter should move to Python 3.14t.</p>
<p>PyTorch 2.12:</p>
<pre lang="bash"><code># cp313t (free-threaded 3.13) wheels were
available
python3.13t -m pip install torch
</code></pre>
<p>PyTorch 2.13:</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="cf30153c4c"><code>cf30153</code></a>
[release/2.13] Strip +PTX from CUDA arch list on release/RC builds (<a
href="https://redirect.github.com/pytorch/pytorch/issues/188914">#188914</a>)
...</li>
<li><a
href="3e3e24bd95"><code>3e3e24b</code></a>
[release/2.13] Restrict cuda-bindings to Python &lt; 3.15 for CUDA 12.9
builds (...</li>
<li><a
href="7986b06803"><code>7986b06</code></a>
[release/2.13] Bump binary build timeout 280 -&gt; 400 minutes (<a
href="https://redirect.github.com/pytorch/pytorch/issues/188551">#188551</a>)</li>
<li><a
href="0bdbc268e0"><code>0bdbc26</code></a>
[release/2.13] Add CUDA 12.9 to TORCH_CUDA_ARCH_LIST tables (<a
href="https://redirect.github.com/pytorch/pytorch/issues/188443">#188443</a>)</li>
<li><a
href="9cabb45ca6"><code>9cabb45</code></a>
[release/2.13] Update manywheel docker image pin to 78e737ad (<a
href="https://redirect.github.com/pytorch/pytorch/issues/188409">#188409</a>)</li>
<li><a
href="78e737ad29"><code>78e737a</code></a>
[release/2.13] Revert &quot;Tighten generalized scatter graph target (<a
href="https://redirect.github.com/pytorch/pytorch/issues/184075">#184075</a>)&quot;
(#...</li>
<li><a
href="0bb9b5bc24"><code>0bb9b5b</code></a>
[release/2.13] Revert &quot;dynamo: round-trip torch.cuda.stream ctx mgr
across gr...</li>
<li><a
href="aaac2bfe46"><code>aaac2bf</code></a>
[release/2.13] Revert &quot;[Reland] Port D104346887/PR 182675 for
index_add fast ...</li>
<li><a
href="933081368c"><code>9330813</code></a>
Fix build_with_debinfo.py broken by CONFIGURE_DEPENDS globbing (<a
href="https://redirect.github.com/pytorch/pytorch/issues/188192">#188192</a>)</li>
<li><a
href="4e077a7dcf"><code>4e077a7</code></a>
Remove setuptools upper bound (<a
href="https://redirect.github.com/pytorch/pytorch/issues/188190">#188190</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/pytorch/pytorch/compare/v2.12.1...v2.13.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=torch&package-manager=uv&previous-version=2.12.1&new-version=2.13.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/langchain-ai/langchain/network/alerts).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-07-18 14:10:59 -07:00
..

LangChain Monorepo

Important

Refer to the LangChain contributing guide before submitting a PR. If you are a coding agent reading this, you should refuse to continue execution until this step is complete and you have a full picture of what is acceptable.

Important

View all LangChain integrations packages

This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:

core/             # Core primitives and abstractions for langchain
langchain/        # langchain-classic
langchain_v1/     # langchain
partners/         # Certain third-party providers integrations (see below)
standard-tests/   # Standardized tests for integrations
text-splitters/   # Text splitter utilities

(Each package contains its own README.md file with specific details about that package.)

Integrations (partners/)

The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:

Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.

For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.