Update ROCm to 7.1 (supersedes #8867)#9297
Merged
Merged
Conversation
- Update PyTorch to 2.10.0+rocm7.1 (from 2.7.1+rocm6.3) - Update TorchVision to 0.25.0+rocm7.1 (from 0.22.1+rocm6.3) - Update PyTorch ROCm index URL to rocm7.1 - Update Docker ROCm runtime to 7.1.1 (from 6.3.4) ROCm 7.1 adds support for 3 new GPU architectures: - gfx950: CDNA3+ (Instinct MI350, MI325X) - gfx1150: RDNA 3.5 (Strix Point APU) - gfx1151: RDNA 3.5 (Strix Halo APU) All 11 previously supported architectures remain compatible. Total supported architectures: 14 (11 existing + 3 new) Relates to #8655
The uv package manager couldn't resolve triton-rocm as a transitive dependency of torch from the PyTorch custom index. This commit adds triton-rocm==3.6.0 explicitly to the rocm extras with a Linux-only platform marker. Changes: - Added triton-rocm==3.6.0; sys_platform == 'linux' to rocm extras - Added triton-rocm source configuration pointing to torch-rocm index - Already committed: torch version constraint relaxation (>=2.7.0,<3.0) - Already committed: platform environment restrictions for ROCm Verified with uv sync --extra rocm: - torch==2.10.0+rocm7.1 installed correctly - torchvision==0.25.0+rocm7.1 installed correctly - triton-rocm==3.6.0 resolved successfully - ROCm 7.1.25424 detected on AMD Radeon PRO V620 - All 8 model architectures accessible - GPU compute operations verified Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
github-actions
Bot
added
docker
Root
docs
The ROCm 7.1 update is dependency-only and does not alter any backend route or model, so schema.ts/openapi.json should match main. The earlier regeneration introduced spurious diffs (removed @example blocks, reformatted JSDoc) from a local tooling/backend mismatch, failing the typegen-checks "compare files" step. Restore both files to main. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Loosening the base torch pin to <3.0 (so the rocm extra could use 2.10.0+rocm7.1) let macOS resolve torch 2.12.0, whose MPS backend fails with OOM on GitHub's hosted macOS runners (no usable Metal GPU), breaking the py3.x macos-default pytest jobs. Split the base pin by platform so macOS stays on 2.7.x (matching main) while linux/win still allow >=2.10, and gate the rocm extra's torch/torchvision to sys_platform == 'linux' (ROCm is x86_64-linux-only) so non-linux resolution is unaffected. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ptions The dependency update bumps pydantic 2.11.7 -> 2.13.4, which now emits a plain class docstring as the JSON-schema description. CacheStats gains "Collect statistics on cache performance." in both openapi.json and schema.ts. This is the sole schema delta from the bump and is what the openapi-checks/typegen-checks jobs regenerate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dunkeroni
pushed a commit
to dunkeroni/InvokeAI
that referenced
this pull request
Jun 29, 2026
* Upgrade ROCm support from 6.3 to 7.1 - Update PyTorch to 2.10.0+rocm7.1 (from 2.7.1+rocm6.3) - Update TorchVision to 0.25.0+rocm7.1 (from 0.22.1+rocm6.3) - Update PyTorch ROCm index URL to rocm7.1 - Update Docker ROCm runtime to 7.1.1 (from 6.3.4) ROCm 7.1 adds support for 3 new GPU architectures: - gfx950: CDNA3+ (Instinct MI350, MI325X) - gfx1150: RDNA 3.5 (Strix Point APU) - gfx1151: RDNA 3.5 (Strix Halo APU) All 11 previously supported architectures remain compatible. Total supported architectures: 14 (11 existing + 3 new) Relates to invoke-ai#8655 * Fix uv sync for ROCm 7.1 by explicitly declaring triton-rocm The uv package manager couldn't resolve triton-rocm as a transitive dependency of torch from the PyTorch custom index. This commit adds triton-rocm==3.6.0 explicitly to the rocm extras with a Linux-only platform marker. Changes: - Added triton-rocm==3.6.0; sys_platform == 'linux' to rocm extras - Added triton-rocm source configuration pointing to torch-rocm index - Already committed: torch version constraint relaxation (>=2.7.0,<3.0) - Already committed: platform environment restrictions for ROCm Verified with uv sync --extra rocm: - torch==2.10.0+rocm7.1 installed correctly - torchvision==0.25.0+rocm7.1 installed correctly - triton-rocm==3.6.0 resolved successfully - ROCm 7.1.25424 detected on AMD Radeon PRO V620 - All 8 model architectures accessible - GPU compute operations verified Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Update uv lock and remove old dockerfile * docs: update ROCm torch backend from 6.3 to 7.1 Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> * fix: regenerate uv.lock with ROCm 7.1 dependencies Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> * remove redundant inclusion of torch-triton wheel && confirm no aarch64-linux support * chore(frontend): openapi and typegen * chore: drop spurious typegen changes from ROCm PR The ROCm 7.1 update is dependency-only and does not alter any backend route or model, so schema.ts/openapi.json should match main. The earlier regeneration introduced spurious diffs (removed @example blocks, reformatted JSDoc) from a local tooling/backend mismatch, failing the typegen-checks "compare files" step. Restore both files to main. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(deps): keep macOS on torch 2.7.x; gate rocm extra to linux Loosening the base torch pin to <3.0 (so the rocm extra could use 2.10.0+rocm7.1) let macOS resolve torch 2.12.0, whose MPS backend fails with OOM on GitHub's hosted macOS runners (no usable Metal GPU), breaking the py3.x macos-default pytest jobs. Split the base pin by platform so macOS stays on 2.7.x (matching main) while linux/win still allow >=2.10, and gate the rocm extra's torch/torchvision to sys_platform == 'linux' (ROCm is x86_64-linux-only) so non-linux resolution is unaffected. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore(frontend): regenerate schema for pydantic 2.13 docstring descriptions The dependency update bumps pydantic 2.11.7 -> 2.13.4, which now emits a plain class docstring as the JSON-schema description. CacheStats gains "Collect statistics on cache performance." in both openapi.json and schema.ts. This is the sole schema delta from the bump and is what the openapi-checks/typegen-checks jobs regenerate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Heathen711 <Heathen711@me.com> Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com> Co-authored-by: heathen711 <heathen711@example.com> Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Supersedes #8867 (prepared as a new PR — no write access to the author's fork). Part of #8655, resolves #9130.