Skip to content

[v1.0.1] Release Tracker #15534

Closed
Closed
[v1.0.1] Release Tracker#15534
Assignees
GregoryComer
Labels
release tracker

Description

@GregoryComer
GregoryComer
opened on Nov 3, 2025

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

  1. Ensure your PR has landed in main. This does not apply for release-branch specific changes (see Phase 1 criteria).

  2. Create (but do not land) a PR against the release branch.
    Option 1: Use pytorchbot to cherry pick a PR that has been committed to the main branch using @pytorchbot cherry-pick command as follows.

    @pytorchbot cherry-pick --onto release/1.0 -c {regression,critical,fixnewfeature,docs,release}
    Details 
    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.

    Details 
    # 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

  3. Make a request below with the following format:

Link to landed trunk PR:
* 

Link to release branch PR:
* 

Criteria category and reasons:
*
  1. Someone from the release team will reply with approved / denied or ask for more information.
  2. 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

Activity

  1. GregoryComer
    self-assigned this
    on Nov 3, 2025
  2. GregoryComer
    added
    release tracker
    on Nov 3, 2025

  3. pytorchbot commented on Nov 6, 2025

    @pytorchbot
    pytorchbot
    on Nov 6, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  4. mergennachin
    pinned this issue on Nov 6, 2025

  5. pytorchbot commented on Nov 6, 2025

    @pytorchbot
    pytorchbot
    on Nov 6, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Docs -

  6. pytorchbot commented on Nov 6, 2025

    @pytorchbot
    pytorchbot
    on Nov 6, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  7. pytorchbot commented on Nov 10, 2025

    @pytorchbot
    pytorchbot
    on Nov 10, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  8. pytorchbot commented on Nov 10, 2025

    @pytorchbot
    pytorchbot
    on Nov 10, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  9. pytorchbot commented on Nov 12, 2025

    @pytorchbot
    pytorchbot
    on Nov 12, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  10. pytorchbot commented on Nov 12, 2025

    @pytorchbot
    pytorchbot
    on Nov 12, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  11. pytorchbot commented on Nov 12, 2025

    @pytorchbot
    pytorchbot
    on Nov 12, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  12. pytorchbot commented on Nov 12, 2025

    @pytorchbot
    pytorchbot
    on Nov 12, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  13. pytorchbot commented on Nov 12, 2025

    @pytorchbot
    pytorchbot
    on Nov 12, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  14. pytorchbot commented on Nov 13, 2025

    @pytorchbot
    pytorchbot
    on Nov 13, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Fixnewfeature -

  15. metascroy commented on Nov 14, 2025

    @metascroy
    metascroy
    on Nov 14, 2025
    Contributor

    @GregoryComer as FYI, we will need to merge #15814 into main and onto 1.0 branch before patch release. Currently investigating CI failures, though.

  16. SS-JIA commented on Nov 14, 2025

    @SS-JIA
    SS-JIA
    on Nov 14, 2025
    Contributor

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    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.

  17. pytorchbot commented on Nov 14, 2025

    @pytorchbot
    pytorchbot
    on Nov 14, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  18. pytorchbot commented on Nov 15, 2025

    @pytorchbot
    pytorchbot
    on Nov 15, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Fixnewfeature -

  19. GregoryComer commented on Nov 19, 2025

    @GregoryComer
    GregoryComer
    on Nov 19, 2025
    ContributorAuthor

    Manual pick to update torchcodec nightly pin: #15879

  20. GregoryComer commented on Nov 19, 2025

    @GregoryComer
    GregoryComer
    on Nov 19, 2025
    ContributorAuthor

    Use the release torchao version with OpenVINO: #15880

  21. pytorchbot commented on Nov 20, 2025

    @pytorchbot
    pytorchbot
    on Nov 20, 2025
    Collaborator

    Link to landed trunk PR (if applicable):

    Link to release branch PR:

    Criteria Category:
    Critical -

  22. mergennachin
    closed this as completedon Dec 1, 2025
  23. mergennachin
    unpinned this issue on Dec 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

release tracker

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions