NeilandOrca 6303bdb50f fix(release): recover orphan tags instead of hard-failing the cut (#1335) ...

If a cut pushes the tag but the workflow is cancelled (or the dependent
release.yml job otherwise fails to start) before a GitHub release is
published, every subsequent patch cut recomputes the same version and
dies on "Tag already exists." This wedged the pipeline on 2026-05-01
when v1.3.26 was pushed by cancelled run 25237882049 — patch cuts kept
failing for hours until release.yml was dispatched by hand.

When the tag exists but no published release is attached, skip the
bump/push steps and emit the existing tag as the job output so
release.yml runs against it and finishes what the prior attempt
started. Still refuse the collision when a real published release
exists — that's a genuine conflict (e.g. a hand-tagged version) and
needs human attention.

Co-authored-by: Orca <help@stably.ai>

2026-05-01 20:13:46 -07:00

..

ISSUE_TEMPLATE

Simplify remaining Orca issue forms

2026-04-14 23:29:55 -07:00

workflows

fix(release): recover orphan tags instead of hard-failing the cut (#1335)

2026-05-01 20:13:46 -07:00

CONTRIBUTING.md

chore: reduce root-directory clutter (#1275)

2026-04-30 00:09:46 -07:00

pull_request_template.md

docs: add contribution guide and PR template (#163)

2026-03-28 10:44:02 -07:00