Repository navigation
fix(release): one draft release per tag, published by the notes job - #121
Merged
Merged
Conversation
The 0.1.0-alpha run created two releases for the same tag: electron-builder uploads the x64 and arm64 builds in parallel and each created its own release when none existed, so the notes job failed with HTTP 422. The tag job now creates a draft that both uploads find; notes publishes it. Co-Authored-By: Claude Opus 5.5 <[email protected]>
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.
Na 0.1.0-alpha o electron-builder publicou x64 e arm64 em paralelo e, sem uma release existente, cada upload criou a sua. A tag ficou com duas releases e o job
notesfalhou comHTTP 422 Release.tag_name already exists. Consertei à mão naquela vez.Mudança: o job
tagcria a release como draft (gh release create --draft --verify-tag). O electron-builder sempre envia para um draft existente da mesma tag (gitHubPublisher.js:if (release.draft) return release). O jobnotesescreve as notas e publica com--draft=false, mantendo--prerelease --latest=falseabaixo da 1.0.Só a próxima release prova a correção.
🤖 Generated with Claude Code