saphidandClaude Opus 5.5 0304575e5b release.yml: create the draft through the REST API so its id comes straight back ...

v0.4.2's first run created the draft with gh release create, then looked its
id up in the release list, which didn't show the fresh draft yet; the PATCH
went to releases/ (404) and the builds were skipped. Now the draft is POSTed
and the id read from the response, after checking the tag exists on GitHub
(what --verify-tag guarded). A rerun still reuses the draft found by tag_name,
and an empty id stops the job instead of PATCHing releases/.

tests/test_release_workflow.py runs the step against tests/fakegh, which now
answers POST releases and applies --jq through jq when installed.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-08 20:28:07 +11:00

..

ISSUE_TEMPLATE

Website with a feedback form that opens GitHub issues, and pi's contributor gate

2026-09-28 14:26:33 +10:00

workflows

release.yml: create the draft through the REST API so its id comes straight back

2026-10-08 20:28:07 +11:00

APPROVED_CONTRIBUTORS

Website with a feedback form that opens GitHub issues, and pi's contributor gate

2026-09-28 14:26:33 +10:00

FUNDING.yml

Website: point the donate buttons at ko-fi.com/alexsouthwell; add FUNDING.yml

2026-09-28 16:18:12 +10:00