Automate release branch preparation - #23287
Draft
JacobSzwejbka wants to merge 14 commits into
Draft
JacobSzwejbka wants to merge 14 commits into
JacobSzwejbka wants to merge 14 commits into
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/23287
Note: Links to docs will display an error until the docs builds have been completed. ❌ 20 New Failures, 1 Unrelated FailureAs of commit ad6781a with merge base 7dc8dd9 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
Bot
added
the
CLA Signed
This PR needs a
|
JacobSzwejbka
force-pushed
the
automate/release-branch-prep
branch
from
October 1, 2026 16:39
7a4f14d to
0d92965
Compare
JacobSzwejbka
changed the title
Authored with assistance from Codex.
Preserve release-specific source synchronization while incorporating the weekly TorchAO pin automation.\n\nAuthored with assistance from Codex.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Automate the deterministic branch-cut work so release creation no longer depends on a manual checklist. The normal invocation is
DRY_RUN=disabled ./scripts/release/cut-release-branch.sh; the release version comes fromviable/strict, and the raw cut is preserved before the prepared release branch is committed and pushed.PyTorch candidate wheels on the test index use final-form package versions, while source candidates use
vX.Y.Z-rcNtags. Preparation now treats those as separate facts: it selects the next final-form wheel train, resolves the newest matching RC source tag, and synchronizes the source pin plus c10 headers to that tag. It reads torchvision and torchaudio wheel metadata to select versions that declare the exact Torch dependency, and requires the same Torch/domain train on cu134 before mutating the checkout. The exceptional cu134 package list is rewritten to those release artifacts.The pre-commit hook preserves release source pins instead of replacing them with the main nightly. Release metadata uses a dedicated build marker, so ordinary wheel jobs no longer trigger the unrelated QNN SDK shortcut. CPU wheels declare a bounded Torch range; CUDA wheels declare the exact matching build. CUDA jobs reject a missing variant in their environment setup. Minimal and source installs do not acquire release-wheel metadata, and main plus release lint use the same test index until finalization.
Stable dependency finalization remains in follow-up #23289. This PR does not change the current dependency pins or ExecuTorch version.
Test plan
2.9.0resolves torchvision0.24.0and torchaudio2.9.02.9.0resolves its newestv2.9.0-rcNsource tagsetup.pygit diff --checkAuthored with OpenAI Codex.