Skip to content

Bump torchao to 03ca489dc and nightly wheel to dev20260729 - #21476

Open
rascani wants to merge 2 commits into
pytorch:mainfrom
rascani:bump-torchao-20260729
Open

Bump torchao to 03ca489dc and nightly wheel to dev20260729#21476
rascani wants to merge 2 commits into
pytorch:mainfrom
rascani:bump-torchao-20260729

Conversation

@rascani

@rascani rascani commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Summary

Advances both torchao pins to the same upstream source. The pip nightly wheel moves from 0.18.0.dev20260715 to 0.18.0.dev20260729, and the third-party/ao submodule moves from 4aa810113 (v0.17.0-178) to 03ca489dc (v0.17.0-224), which is the exact torchao main commit the dev20260729 nightly wheel was built from. Previously the two pins were roughly six weeks apart; keeping them on the same commit avoids source-versus-wheel skew between the built-from-source kernels and the installed package.

This change was authored with Claude Code.

Advances both torchao pins to the same upstream source. The pip nightly
wheel moves from 0.18.0.dev20260715 to 0.18.0.dev20260729, and the
third-party/ao submodule moves from 4aa810113 (v0.17.0-178) to 03ca489dc
(v0.17.0-224), which is the exact torchao main commit the dev20260729
nightly wheel was built from. Previously the two pins were roughly six
weeks apart; keeping them on the same commit avoids source-versus-wheel
skew between the built-from-source kernels and the installed package.

This change was authored with Claude Code.
@pytorch-bot

pytorch-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit 18ea04e with merge base f4a21b8 (image):

NEW FAILURE - The following job has failed:

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

@rascani
rascani requested a review from JacobSzwejbka July 29, 2026 20:24
@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 Jul 29, 2026
@github-actions

Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

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.

2 participants