Skip to content

Automate stable release dependency finalization - #23289

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

JacobSzwejbka wants to merge 8 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.

Candidate package versions are already final-form on the PyTorch test index. Finalization therefore verifies that Torch, torchvision, and torchaudio have reached PyPI and that their cu134 variants exist on the stable PyTorch index; it does not invent or remap companion versions. It switches installs from the test index to stable, moves the PyTorch source pin and vendored c10 headers from the newest RC tag to the final vX.Y.Z tag, finalizes TorchAO, pytorch-tokenizers, TorchCodec and submodule tags, and marks the branch finalized. All planned text, source, and submodule changes are covered by rollback.

Final ExecuTorch tags require the finalized marker and a plain final Torch version. The script prepares a reviewable diff only: it does not commit, push, tag, publish wheels, or perform an ExecuTorch release.

Test plan

  • finalization suite: 2 tests
  • combined preparation and finalization pytest collection: 4 tests
  • mypy, ufmt, flake8, and 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 Pending, 2 Unclassified Failures

As of commit 3eb605e with merge base c5f2b7a (image):

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
@JacobSzwejbka
JacobSzwejbka force-pushed the automate/release-finalization branch from ed7ce47 to 1b4c431 Compare October 1, 2026 16:40
@JacobSzwejbka
JacobSzwejbka force-pushed the automate/release-finalization branch from 1b4c431 to 9801368 Compare October 1, 2026 20:14
@JacobSzwejbka
JacobSzwejbka force-pushed the automate/release-finalization branch from 9801368 to b303b04 Compare October 1, 2026 20:15
@JacobSzwejbka
JacobSzwejbka force-pushed the automate/release-finalization branch from 1e87109 to 7b2a44c Compare October 1, 2026 21:50

This branch was successfully deployed

1 active deployment
cadence — 3eb605eb Deployed Oct 1, 2026 by JacobSzwejbka via hifi-op-test / hifi4 #30945
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