Skip to content

Document compatible GPU release repair and legacy upgrades #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tarsur909 merged 1 commit into from
Oct 4, 2026
Merged

Document compatible GPU release repair and legacy upgrades #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 11 additions & 7 deletions docs/operations/gpu-bundles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,15 +63,19 @@ then qualifies them on two SM90 GPUs. GPU qualification must succeed before
PyPI publication. The GitHub release stays a draft until every asset is
uploaded successfully. No self-hosted runner is needed.

To repair an unpublished tagged release after an orchestration failure, run
For v0.1.4 or newer tags with the runtime-wheel manifest format, repair an
unpublished release after an orchestration failure by running
**Release** from the `main` branch with its immutable version tag. The
portable artifacts and native wheels are built from that tag, even when the
workflow repair is newer. The `pypi` environment allows `v*` tags. A repair from `main` also requires
that environment to allow the `main` branch during the repair. Published PyPI versions cannot
be overwritten.

For an existing portable-only release, run **GPU validation** from Actions
with its version tag. This builds the exact tagged commit without
workflow repair is newer. The `pypi` environment allows `v*` tags. A repair
from `main` also requires that environment to allow the `main` branch during
the repair. Published PyPI versions cannot be overwritten.

For a compatible v0.1.4 or newer release missing GPU assets, run
**GPU validation** from Actions with its version tag. The older v0.1.1
installer and manifest do not support the new runtime wheels; upgrade
instead of backfilling that portable-only release. Validation builds the
exact tagged commit without
republishing PyPI. Successful runs upload the wheels, compatibility
manifest, qualification reports, checksums, and SBOMs; `gpu-bundles.json`
is uploaded last so automatic installation cannot select an unfinished
Expand Down
Loading