ci: document how to rebuild today's tag without a 404 window - #18
Merged
Merged
Conversation
Deleting a same-day GitHub release by hand and then dispatching build-pre-release leaves every installer without a package for the whole rebuild — a user hit a 404 for ~2 h. The workflow already replaces a same-tag pre-release at the end of the run, after the three platforms have validated, in about 50 seconds. Add the four-step runbook to the README and point the dispatch form at it: mark the existing release as a pre-release first, never delete it.
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.
Deleting a same-day release by hand and then dispatching build-pre-release leaves installers without a package for the whole rebuild (a user hit a 404 for about two hours on 2026-09-15). The workflow already swaps a same-tag
pre-release at the end of the run, in about 50 seconds. This adds the four-step runbook to the README and points the dispatch form at it: mark the release as pre-release first, never delete it. Documentation only; no job logic changes.