Skip to content

CI: publish the tag's release directly instead of a draft - #15

Merged
df49b9cd merged 1 commit into
mainfrom
ci/publish-release
Nov 4, 2026
Merged

df49b9cd merged 1 commit into
mainfrom
ci/publish-release

Conversation

@df49b9cd

@df49b9cd df49b9cd commented Nov 4, 2026

Copy link
Copy Markdown
Owner

The v0.1.0 tag build created a draft release with all six assets. Drafts are only reachable through an untagged-… URL, so a second release was created by hand from the tag and published, with no assets. That's how the repo ended up with an empty "Latest" release next to a draft holding the files.

Change: the release job publishes the tag's release itself (draft: false). If a release already exists for the tag (made by hand, or from an earlier run), softprops/action-gh-release updates it in place and overwrite_files: true replaces its assets, so each tag only ever has one release. Prerelease tags (v*-*) stay prereleases and never get make_latest.

Already fixed by hand for v0.1.0: I uploaded the six assets from the draft to the published release, after checking each against SHA256SUMS and gh attestation verify. I copied the full notes over and deleted the duplicate draft.

Not run yet: the next tag build is the first real run of this path.

v0.1.0 ended up as two releases: the job's draft (only reachable via an
untagged-* URL, with all assets) and a second one published by hand from
the tag, with none. Publish on the tag's release instead, updating it in
place (assets overwritten) when one already exists; prereleases are never
marked latest.
@df49b9cd
df49b9cd merged commit eff0591 into main Nov 4, 2026
6 checks passed
@df49b9cd
df49b9cd deleted the ci/publish-release branch November 4, 2026 13:45
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