Skip to content

Allow ROCm packages from a PEP 503 index (e.g. repo.amd.com)#53

Draft
ethanwee1 wants to merge 2 commits into
mainfrom
ethanwee/pytorch-wheels-rocm-index-url
Draft

Allow ROCm packages from a PEP 503 index (e.g. repo.amd.com)#53
ethanwee1 wants to merge 2 commits into
mainfrom
ethanwee/pytorch-wheels-rocm-index-url

Conversation

@ethanwee1

@ethanwee1 ethanwee1 commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds optional rocm_package_index_url to the rockrel multi-arch PyTorch wheel release workflow so ROCm packages can be installed from a PEP 503 simple index (e.g. https://repo.amd.com/rocm/whl-multi-arch/) instead of only a flat --find-links page.

Changes

  • multi_arch_release_linux_pytorch_wheels.yml: new rocm_package_index_url input; either index URL or find-links URL can be supplied
  • Pins the reusable workflow to a TheRock branch that implements index-url support in the build pipeline

Why

Some AMD ROCm package hosts expose wheels via PEP 503 index layout rather than a single flat HTML find-links page. This lets release dispatches target those indexes without manual URL workarounds.

ethanwee1 added 2 commits June 8, 2026 17:15
Add an optional rocm_package_index_url input and forward it to the TheRock
reusable workflow, and make rocm_package_find_links_url optional. This lets
the multi-arch PyTorch wheel release build install ROCm from a PEP 503 index
such as the released wheels at repo.amd.com/rocm/whl-multi-arch instead of
only a flat find-links page.
Route the rockrel wrapper to the TheRock PR branch so the pre-merge ROCm 7.13 released-index build can be dispatched before the reusable workflow change lands on main.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant