Skip to content

Update prerelease install docs for repo.amd.com - #101

Open
marbre wants to merge 1 commit into
mainfrom
users/marbre/release_repo_amd_doc_updates
Open

Update prerelease install docs for repo.amd.com#101
marbre wants to merge 1 commit into
mainfrom
users/marbre/release_repo_amd_doc_updates

Conversation

@marbre

@marbre marbre commented Aug 21, 2026

Copy link
Copy Markdown
Member

Motivation

Point current prerelease installs at the RC aggregate and core artifact paths while directing ROCm 10.0.0 release-candidate users to the preserved legacy locations.

Submission Checklist

@marbre
marbre requested a review from ScottTodd August 21, 2026 21:38

@ScottTodd ScottTodd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This can wait to merge until we have our first rc packages at the new url

@marbre marbre changed the title Update Prerelease Install Docs for repo.amd.com Update prerelease install socs for repo.amd.com Aug 21, 2026
@marbre marbre changed the title Update prerelease install socs for repo.amd.com Update prerelease install docs for repo.amd.com Aug 21, 2026
Base automatically changed from users/marbre/release_repo_amd_bucket_rewire to main August 22, 2026 09:45
Point current prerelease installs at the RC aggregate and Core artifact paths while directing ROCm 10.0.0 release-candidate users to the preserved legacy locations.

Test Plan:
- run git diff --check
- verify current README examples contain no legacy release URLs
- verify pip examples do not use product-local indexes

Test Result:
- Passed: diff check
- Passed: legacy URL search
- Passed: product-local pip index search
@marbre
marbre force-pushed the users/marbre/release_repo_amd_doc_updates branch from 11a0e24 to f8433dd Compare August 22, 2026 09:45
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.

2 participants