Repository navigation
ci(release): a push that releases nothing leaves 10 red conda checks on main while 1.5.0b12 is unfinished (#1634) #1748
Description
Describe the bug
A push to main that releases nothing ends with 10 red Conda deployment (release) checks on its commit. This is the case for 87d96459a and twice for 0cdd3cdd1. It is #1634's guard working as designed:
v1.5.0b12names2025da5e5, and anaconda holds only 1 of its 10 files, because the re-run was declined on ci: anaconda.org rejects the 1.5.0b12 conda uploads (402, storage limit), so every later Create Release run on main fails at the #1634 guard #1704.- So every Create Release that a push-triggered Vendor Update starts runs the 12-minute test gate and 10 runners, only for each conda leg to refuse to publish this tree under that tag (
create-release.yml~1126). Release statusitself stays green, with a warning.mainstays red until the next version bump.
Side finding: a Vendor Update whose verdict is "not covered" still concludes success (run 38650191283). Create Release treats it as a real Vendor Update, so 0cdd3cdd1 got two Create Release runs and 20 red checks.
Options
| Option | Effect |
|---|---|
A. version_check records whether the version's tag names another commit. If so, and the ref is not a v* tag, the gate, tag, pypi and conda skip, and Release status posts a ::notice (release complete) or a ::warning (release unfinished, re-run the tagged commit's run) and stays green |
main goes green. #1634's guard is unchanged for real releases. An unfinished release on a later commit becomes a warning rather than a red run |
| B. Keep as is | Red until 1.5.0 |
C. Finish 1.5.0b12 by re-running the run for 2025da5e5 |
Green, but #1704 declined it |
Recommendation: A, plus a fix for the side finding: a "not covered" Vendor Update concludes skipped, or Create Release reads its verdict. The pinned tests, test_release_tags_the_run_sha_1634.py and test_release_gates.py, gain rows; the #888 stranded-partial case must still exit 1.
Activity
JarryShaw commentedon Oct 14, 2026
take recommendations
JarryShaw commentedon Oct 14, 2026
Recorded: option A, together with the side-finding fix.
version_checkrecords whether the version's tag names another commit. If it does, and the ref is not av*tag, the test gate,tag,pypiandcondaskip, andRelease statusposts a::notice(release complete) or a::warning(release unfinished) and stays green. fix(ci): Create Release tags main's tip at approval time, not the commit it was created for #1634's guard is untouched for real releases, and the fix(ci): a half-finished release leaves a v* tag that makes every retry skip silently #888 stranded-partial case still exits 1.A worker is on it.
ci(release): a push that releases nothing stays green when its versio…
ci(release): a push that releases nothing stays green when its versio…
docs(tests): second pass over tests outside tests/protocols (#1103)
docs(tests): second pass over tests outside tests/protocols (#1103) (#…