Repository navigation
ci(release): never rebuild an artifact that is already published - #13
Merged
Merged
Conversation
Re-running the release workflow on an existing tag rebuilt every target and replaced the uploaded tarballs. The build is not byte-reproducible, so the bytes behind an already-published version changed silently: v0.5.11 was re-dispatched to exercise the new tap job and both checksums moved, which the tap job then dutifully committed as a second formula bump. Anyone who had downloaded and pinned the first build would have found the published artifact no longer matching. The build now checks the release for its own target first and skips compiling and uploading when that asset exists, with overwrite_files: false behind it. Re-running becomes what it was assumed to be: a way to re-run the tap job, or to fill in a target whose upload failed, without touching what is already out. Signed-off-by: principalwater <kuzmin.vv@yahoo.com>
elementary-flow-bot
approved these changes
Aug 17, 2026
elementary-flow-bot
left a comment
Collaborator
There was a problem hiding this comment.
CI passed: auto-approved by bot.
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.
Re-running the release workflow on an existing tag rebuilt every target and replaced the uploaded tarballs. The build is not byte-reproducible, so the bytes behind an already-published version changed silently.
This is not hypothetical:
v0.5.11was re-dispatched to exercise the new tap job, both checksums moved, and the tap job dutifully committed a second formula bump for the same version. Anyone who had downloaded and pinned the first build would have found the published artifact no longer matching it.The build job now asks the release whether its own target is already published and, if so, skips compiling and uploading.
overwrite_files: falsesits behind that as a second line.Re-running becomes what it was assumed to be: a way to re-run the tap job, or to fill in a target whose upload failed, without touching what is already out. A genuinely new build still needs a new tag, which is the right way to publish different bytes.