Skip to content

Publish release as draft until binaries are attached - #5

Merged
imohsenb merged 1 commit into
mainfrom
feature/tap-fix
Aug 7, 2026
Merged

imohsenb merged 1 commit into
mainfrom
feature/tap-fix

Conversation

@imohsenb

@imohsenb imohsenb commented Aug 7, 2026

Copy link
Copy Markdown
Owner

Summary

  • v1.0.2's release went live before build-binaries could attach assets; GitHub's immutable-release rule then rejected every upload (Cannot upload asset ... to an immutable release), so v1.0.2 shipped with zero binaries.
  • Create the release as a draft in tag-release, upload all 4 platform tarballs to it in build-binaries, then flip it to published in a new publish-release job once uploads finish.
  • Bump to 1.0.3 since v1.0.2's tag/release is already burned (can't reuse it -- tag-release skips already-tagged versions).

Test plan

  • cargo check with bumped version.
  • YAML validated.
  • Merge and confirm v1.0.3 release ends up published with 4 attached binaries.

softprops/action-gh-release published the release immediately, but
GitHub's immutable-release rule blocks asset uploads to a published
release -- the build-binaries job's uploads all failed against v1.0.2.
Create the release as a draft, upload binaries to it across the matrix,
then publish once everything's attached.
@imohsenb
imohsenb merged commit 79b715e into main Aug 7, 2026
2 checks passed
@imohsenb
imohsenb deleted the feature/tap-fix branch August 7, 2026 15:17
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