[tailscale] .github/workflows: fix release creation for immutable releases - #177
Merged
Merged
Conversation
…eases GitHub releases are now immutable: once a release is published, assets can no longer be added, so the old create-then-upload flow fails with "Cannot upload assets to an immutable release". Create the release as a draft instead, upload the per-platform tarballs to the draft, and publish it in a new final publish_release job once all uploads succeed. This also replaces the long-archived actions/create-release and actions/upload-release-asset actions with the gh CLI preinstalled on the runners. Updates #47 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com> Change-Id: Ib2c50f81d9e4a7302cf9e60dd41908ae7c73f9c4
adrianosela
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub releases are now immutable: once a release is published, assets can no longer be added, so the old create-then-upload flow fails with "Cannot upload assets to an immutable release". Create the release as a draft instead, upload the per-platform tarballs to the draft, and publish it in a new final publish_release job once all uploads succeed.
This also replaces the long-archived actions/create-release and actions/upload-release-asset actions with the gh CLI preinstalled on the runners.
Updates #47
Change-Id: Ib2c50f81d9e4a7302cf9e60dd41908ae7c73f9c4