pytorch
[v1.0.1] Release Tracker
The v1.0.1 release will be cut from the "release/1.0" branch for critical fixes to the v1.0.0 release.
Intended Release Date: 11/20/2025 Cherry-Pick Submission Cutoff: 11/17/2025
This issue is for tracking cherry-picks to the release branch.
Cherry-Pick Criteria
Cherry-picks will be accepted for the following:
- Critical Fixes - crashes, correctness issues, critical memory or memory regressions, or setup and installation issues.
- Documentation and example updates.
New features will not be accepted.
Cherry-Pick Process
-
Ensure your PR has landed in main. This does not apply for release-branch specific changes (see Phase 1 criteria).
-
Create (but do not land) a PR against the release branch. Option 1: Use
pytorchbotto cherry pick a PR that has been committed to the main branch using@pytorchbot cherry-pickcommand as follows.@pytorchbot cherry-pick --onto release/1.0 -c {regression,critical,fixnewfeature,docs,release}usage: @pytorchbot cherry-pick --onto ONTO [--fixes FIXES] -c {regression,critical,fixnewfeature,docs,release} Cherry pick a pull request onto a release branch for inclusion in a release optional arguments: --onto ONTO Branch you would like to cherry pick onto (Example: release/1.0) --fixes FIXES Link to the issue that your PR fixes (i.e. https://github.com/pytorch/executorch/issues/2345) -c {regression,critical,fixnewfeature,docs,release} A machine-friendly classification of the cherry-pick reason.Option 2: Manually create a cherry pick PR using git command as follows.
# Find the hash of the commit you want to cherry pick # (for example, abcdef12345) git log git fetch origin release/1.0 git checkout release/1.0 git cherry-pick -x abcdef12345 # Submit a PR based against 'release/1.0' either: # via the GitHub UI git push my-fork # via the GitHub CLI gh pr create --base release/1.0 -
Make a request below with the following format:
Link to landed trunk PR:
*
Link to release branch PR:
*
Criteria category and reasons:
*
- Someone from the release team will reply with approved / denied or ask for more information.
- If approved, someone from the release team will merge your PR once the tests pass. Do not land the release branch PR yourself.
Please note HUD Link with branch CI status and link to the HUD to be provided here. HUD
Versions
1.0.1
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15366
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15646
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15540
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15652
Criteria Category: Docs -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15622
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15657
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15648
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15717
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15625
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15718
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15605
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15782
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15627
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15783
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15584
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15784
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15628
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15785
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15647
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15786
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15723
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15803
Criteria Category: Fixnewfeature -
@GregoryComer as FYI, we will need to merge https://github.com/pytorch/executorch/pull/15814 into main and onto 1.0 branch before patch release. Currently investigating CI failures, though.
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15829
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15834
Criteria Category: Critical -
@SS-JIA: Could not automatically cherry pick the original PR because it modified some new operators not in release/1.0 as well.
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15787
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15835
Criteria Category: Critical -
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15814
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15839
Criteria Category: Fixnewfeature -
Manual pick to update torchcodec nightly pin: https://github.com/pytorch/executorch/pull/15879
Use the release torchao version with OpenVINO: https://github.com/pytorch/executorch/pull/15880
Link to landed trunk PR (if applicable):
- https://github.com/pytorch/executorch/pull/15684
Link to release branch PR:
- https://github.com/pytorch/executorch/pull/15905
Criteria Category: Critical -