Skip to content

ci: build release artifacts in release workflows #1760

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

Closed
cpcloud wants to merge 1 commit into from
Closed

ci: build release artifacts in release workflows #1760

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/release_checklist.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ body:
- label: "Finalize the doc update, including release notes (\"Note: Touching docstrings/type annotations in code is OK during code freeze, apply your best judgement!\")"
- label: Update the docs for the new version
- label: Create a public release tag
- label: Wait for the tag-triggered CI run to complete, and use that run ID for release workflows
- label: Confirm the tagged commit already has a green CI run on main, then run the release workflow for that tag
- label: If any code change happens, rebuild the wheels from the new tag
- label: Upload wheels to PyPI
- label: Update the conda recipe & release conda packages
Expand Down
19 changes: 8 additions & 11 deletions .github/RELEASE-core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,16 +108,14 @@ git push origin cuda-core-v0.6.0

---

## Wait for the tag-triggered CI run to complete
## Verify the tagged commit already passed CI on `main`

Pushing the tag triggers a CI run automatically. Monitor it in the
**Actions** tab on GitHub.
Before running release, confirm that the tagged commit already has a
successful `CI` run on `main`. The release workflow now checks this as a
preflight step, but it is still worth verifying up front.

- **All CI tests should succeed.** If any fail, investigate and rerun as
needed.
- Note the **run ID** of the successful tag-triggered run. The release
workflow can auto-detect it from the tag, but you can also provide it
explicitly.
- **All CI tests on `main` should already be green.** If any fail, fix them
before tagging or release will be blocked.

---

Expand All @@ -129,9 +127,8 @@ publish to TestPyPI, then publish the same wheel set to PyPI.
1. Go to **Actions > CI: Release** and run the workflow with:
- **Component**: `cuda-core`
- **The release git tag**: `cuda-core-v0.6.0`

The workflow automatically looks up the successful tag-triggered CI run
for the selected release tag.
The workflow builds the release artifacts directly from the selected tag
after verifying that the tagged commit already passed `CI` on `main`.

2. Wait for the workflow to complete. It will:
- publish the selected wheels to TestPyPI
Expand Down
Loading