# PyTorch Release 2.14.1

**URL:** <https://dev-discuss.pytorch.org/t/pytorch-release-2-14-1/3444>\
**Category:** Release Announcements\
**Created:** [September 22, 2026, 6:13pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-14-1/3444 "2026-09-22T18:13:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![atalman](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/atalman/32/1857_2.png) [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Post date:** [September 22, 2026, 6:13pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-14-1/3444/1 "2026-09-22T18:13:11Z")

</div>

Hi everyone,

We are going to be releasing PyTorch 2.14.1, a patch release for the 2.14 line, following the usual patch release process.

## Milestones

| Milestone | Description | Date |
| --- | --- | --- |
| **M1** | Patch Release Announcement | **September 22** |
| **M2** | Cherry-pick post deadline (end of day, 5PM PST) | **September 25** |
| **M3** | All RC binaries ready for testing | **September 28** |
| **M4** | General Availability | **September 30** |

## Tracking

Work for this release is tracked on GitHub:

- Milestone: [GitHub · Where software is built](https://github.com/pytorch/pytorch/milestone/70)
- Release Tracker: [[v2.14.1] Release Tracker · Issue #198239 · pytorch/pytorch · GitHub](https://github.com/pytorch/pytorch/issues/198239)

## Submitting a cherry-pick

Your fix must land in `main` first. Once the PR is merged, request the cherry-pick by commenting on that same merged PR:

```auto
@pytorchbot cherry-pick --onto release/2.14 -c <classification>

```

Valid classifications are `regression`, `critical`, `fixnewfeature`, `docs` and `release`.

Only low-risk changes will be cherry-picked from `main`. All requests must be posted before the **M2** deadline above.

## What qualifies for a cherry-pick

- Critical, low-risk fixes for silent correctness, backwards compatibility, crashes, deadlocks, or (large) memory leaks
- Regressions against PyTorch 2.14.0
- Documentation improvements
- Changes specific to the release branch, such as blocking CI fixes and version identifiers
- Urgent fixes to features that first shipped in 2.14.0

## What does not qualify

- Feature work
- Anything risky or large in scope
- Numerical or performance changes that do not repair a regression

Thanks,

Team PyTorch