You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move release publishing away from tag-triggered CI artifact lookup by having release workflows verify main CI, build tagged artifacts in-run, and publish from those exact outputs. This cuts duplicate release work and keeps the release docs, assets, and wheel uploads tied to the same workflow execution.
Made-with: Cursor
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/release_checklist.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ body:
23
23
- label: "Finalize the doc update, including release notes (\"Note: Touching docstrings/type annotations in code is OK during code freeze, apply your best judgement!\")"
24
24
- label: Update the docs for the new version
25
25
- label: Create a public release tag
26
-
- label: Wait for the tag-triggered CI run to complete, and use that run ID for release workflows
26
+
- label: Confirm the tagged commit already has a green CI run on main, then run the release workflow for that tag
27
27
- label: If any code change happens, rebuild the wheels from the new tag
28
28
- label: Upload wheels to PyPI
29
29
- label: Update the conda recipe & release conda packages
0 commit comments