Skip to content

Conversation

jainapurva
Copy link
Contributor

@jainapurva jainapurva commented Oct 7, 2025

Updated the version from 0.14.0 to 0.15.0.

Copy link

pytorch-bot bot commented Oct 7, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/3130

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

⏳ No Failures, 12 Pending

As of commit 29e6265 with merge base fd62d0e (image):
💚 Looks good so far! There are no failures yet. 💚

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 Oct 7, 2025
@jainapurva jainapurva added the topic: not user facing Use this tag if you don't want this PR to show up in release notes label Oct 7, 2025
@andrewor14
Copy link
Contributor

@liangel-02 anything we need to bump for the version compatibility?

@andrewor14 andrewor14 requested a review from liangel-02 October 7, 2025 21:09
@liangel-02 liangel-02 self-requested a review October 7, 2025 21:15
@liangel-02
Copy link
Contributor

@liangel-02 anything we need to bump for the version compatibility?

  1. In https://github.com/pytorch/ao/blob/main/torchao/__init__.py#L76, update the condition to 2.9.0dev and 0.14.0 (instead of 0.14.0dev). Then, add a new condition for 0.15.0dev and corresponding torch version - we want to add another "load .so files" condition when the user builds with the compatible version of torch for the updated torchao version.

  2. Add a new test for the new version in https://github.com/pytorch/ao/blob/main/scripts/test_torch_version_torchao_version_compatibility.sh . Manually run the bash script to verify these changes: .scripts/test_torch_version_torchao_version_compatibility.sh

  3. We can also update the compatibility table in torchao release compatibility table #2919 to reflect the latest updates

@vkuzo please comment if there's anything missing

Copy link
Contributor

@jerryzh168 jerryzh168 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be landed immediately after branch cut IIUC


v2_8_0 = _parse_version("2.8.0")
v0_13_0 = _parse_version("0.13.0")
v2_9_0_dev = _parse_version("2.9.0.dev")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As 2.9 has not been released yet, we might still need to call it dev, but the branch cut has been done in core, and the dev version has been updated to 2.10.0.dev. @liangel-02 How do we handle this?

@jainapurva jainapurva merged commit a5a8fe2 into main Oct 9, 2025
18 checks passed
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. topic: not user facing Use this tag if you don't want this PR to show up in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants