add migration for pytorch 2.6 #7035
Merged
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.
After conda-forge/pytorch-cpu-feedstock#326. As I mentioned there, the plan is to roll out 2.6 across existing feedstocks first, and then do it again more slowly with a piggyback migrator that removes
skip: true [win](though of course feedstock maintainers are encouraged to try that out individually as well).It's possible we still have some bugs to iron out, in particular:
Please raise issues on the pytorch feedstock if something fishy is going on in one of the upgrade PRs.