update version compatibility table #3455
Open
Conversation
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/3455
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit d82fb0a with merge base aa21b80 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
bot
added
the
CLA Signed
danielvegamyhre
added
the
topic: not user facing
jerryzh168
reviewed
Dec 6, 2025
| # Built against torch 2.9.1 | ||
| (_parse_version("0.15.0"), _parse_version("2.9.1")), | ||
| (_parse_version("0.15.0"), _parse_version("2.10.0.dev")), | ||
| # Current torchao version |
Contributor
There was a problem hiding this comment.
should the current torchao version also be updated?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
for 0.15.0 release. will need to cherry pick this into the release branch i think, the release runbook had the steps out of order, i updated it accordingly.