Skip to content

Automate stable release dependency finalization - #23289

Draft
JacobSzwejbka wants to merge 3 commits into
automate/release-branch-prepfrom
automate/release-finalization
Draft

JacobSzwejbka wants to merge 3 commits into
automate/release-branch-prepfrom
automate/release-finalization

Conversation

@JacobSzwejbka

@JacobSzwejbka JacobSzwejbka commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #23287. This keeps stable dependency finalization separate from branch-cut preparation.

Review the artifact preflight first: the script derives final PyTorch, torchvision, and torchaudio versions from the RC train and verifies those packages together with TorchAO, pytorch-tokenizers, TorchCodec, and required submodule tags before editing. Then review the planned text and submodule updates, which finalize dependency pins and index URLs with rollback for partial failures. The wheel checks allow upstream RC dependencies for ExecuTorch RC tags but require a plain final PyTorch version and finalized dependencies for final ExecuTorch tags.

The script prepares a reviewable diff only. It does not commit, push, tag, publish wheels, or perform an ExecuTorch release.

Test plan

  • python3 scripts/release/test_finalize_release.py (2 tests)
  • mypy, ufmt, and flake8
  • RC-to-final dependency promotion in an isolated checkout
  • git diff --check

Authored with OpenAI Codex.

@pytorch-bot

pytorch-bot Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/23289

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 2 Pending, 2 Unclassified Failures

As of commit 1b4c431 with merge base c5f2b7a (image):

NEW FAILURE - The following job has failed:

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 30, 2026
@JacobSzwejbka
JacobSzwejbka force-pushed the automate/release-finalization branch from 33abba3 to ca121f0 Compare October 1, 2026 16:22
@JacobSzwejbka
JacobSzwejbka force-pushed the automate/release-finalization branch from ca121f0 to ed7ce47 Compare October 1, 2026 16:37
@JacobSzwejbka
JacobSzwejbka force-pushed the automate/release-branch-prep branch from 7a4f14d to 0d92965 Compare October 1, 2026 16:39

This branch was successfully deployed

1 active deployment
cadence — 1b4c431a Deployed Oct 1, 2026 by JacobSzwejbka via hifi-op-test / hifi4 #30855
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant