Skip to content

Fix ci-release when an untagged ci draft blocks create - #15

Merged
kzu merged 1 commit into
mainfrom
dev/ci-release-untagged-draft
Aug 25, 2026
Merged

kzu merged 1 commit into
mainfrom
dev/ci-release-untagged-draft

Conversation

@kzu

@kzu kzu commented Aug 25, 2026

Copy link
Copy Markdown
Member

The rolling ci prerelease never survived a second publish. Native AOT jobs succeeded, then gh release create ci failed with a release with the same tag name already exists.

gh release view/delete ci looks up GET /releases/tags/ci. After the git tag is dropped, GitHub keeps an untagged draft that still has tag_name: ci. View 404s, create 422s, and ndnx --update ci 404s because there is no ci tag.

This sweep deletes every release with tag_name == ci by id (drafts included), drops refs/tags/ci, and retries create with backoff. Publishing is no longer cancelled in-flight, which is how those leftover drafts get created.

Once this lands, the next successful build (or a workflow_dispatch of ci-release) will replace the leftover untagged draft and restore ndnx --update ci.

gh release view/delete by tag miss leftover drafts that still claim tag_name=ci, so create 422s and ndnx --update ci 404s. Sweep those releases by id, retry create, and do not cancel an in-flight publish.
@kzu
kzu enabled auto-merge (rebase) August 25, 2026 17:54
@kzu

kzu commented Aug 25, 2026

Copy link
Copy Markdown
Member Author

188 passed 188 passed

🧪 Details on Ubuntu 24.04.4 LTS

from retest v1.1.0 on .NET 10.0.11 with 💜 by @devlooped

@kzu
kzu merged commit 0e3b1e8 into main Aug 25, 2026
4 checks passed
@kzu
kzu deleted the dev/ci-release-untagged-draft branch August 25, 2026 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant