Update Windows ROCm Python package index URLs to ROCm 10 - #1737
Merged
Conversation
mohnjiles
approved these changes
Sep 11, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Fast tracking update to new permanent AMD Stable/Nightly repository before other in-progress upcoming changes to ROCm handling to fix an issue regarding 7.14.1 ROCm/PyTorch AMD builds. Users on Stability Matrix discord have been reporting issues with
CUDA error: invalid argumentandhipErrorInvalidValuein workflows since the patch version bump from ROCm 7.14 to 7.14.1 that coincided with the release of ROCm 10. This has also been observed outside of Stability Matrix.Changes:
(ROCm 7.14.1) https://repo.amd.com/rocm/whl-multi-arch/ -> https://stable.repo.amd.com/rocm/whl-next/ (ROCm 10.0)
https://rocm.nightlies.amd.com/whl-multi-arch/ -> https://nightly.repo.amd.com/rocm/whl-next/
Users with pre-existing packages bearing 7.14.1 in it's installation will need to either install a new installation of the package and delete the original, or initiate a package update where the PyTorch upgrade path also runs during it (i.e.: ComfyUI) if the package is configured to do so.