Repository navigation
fix: revert releases to draft (immutable releases conflict) - #6
Merged
Merged
Conversation
Repo has immutable releases enabled: a release created as already- published rejects asset uploads (422 Cannot upload assets to an immutable release). Back to electron-builder's default draft flow, same as tyvox: CI uploads assets to a draft, publish manually.
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
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.
v0.0.8 build failed:
422 Cannot upload assets to an immutable release. The repo has GitHub immutable releases enabled, which is incompatible withreleaseType: "release"(release is published before assets upload).Revert to default draft flow (tyvox parity): CI builds + uploads assets into a draft release → publish with one click.