Skip to content

ci(release): never rebuild an artifact that is already published - #13

Merged
principalwater merged 1 commit into
mainfrom
ci/immutable-release-assets
Aug 17, 2026
Merged

principalwater merged 1 commit into
mainfrom
ci/immutable-release-assets

Conversation

@principalwater

Copy link
Copy Markdown
Collaborator

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.11 was 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: false sits 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.

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 elementary-flow-bot left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI passed: auto-approved by bot.

@principalwater
principalwater merged commit a24f986 into main Aug 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants