Repository navigation
Release-assets policy: the three prune guards and the May 2026 delete-and-recreate history - #54
Merged
Merged
Conversation
…-and-recreate history The snapshot prune step refuses an empty upload, treats an asset that is already gone as removed and fails only after trying every deletion. The section records where those guards come from: the first snapshot job of 2026-05-07 deleted and recreated the whole release, the bursts of main pushes of 2026-05-10 deleted it under each other (all but the last job of every burst failed with the artifacts present), the Central migration dropped the job the next morning and it came back without any cleanup -- with no commit naming the failures, which is why the reason was lost once. The cross-repo status bullet follows. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AytmJF9faEiQEVt6eetQS2
This was referenced Oct 12, 2026
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.
Summary
policies/fat-jar-release-assets.md, section "Thesnapshotpre-release holds exactly the current upload", gets a subsection on the three guards of the prune step (an empty upload is refused, an asset that is already gone counts as removed, a failed deletion is reported and the rest still tried) and the history they come from, dug up from the four repos'git logand the Actions API: the first snapshot job of 2026-05-07 deleted and recreated the whole release with its tag (and for GitHub Packagesdelete-package-versions, replaced the same evening because it cannot remove the last version); on 2026-05-10 bursts of dependabot merges put several main-push runs minutes apart on each sibling and their snapshot jobs deleted the release under each other (BAF 4 of 5, srcmorph 4 of 6, streambuffer 5 of 6 failed with the artifact download green); the Central migration of 2026-05-11 dropped the job and it came back as view-or-create plusupload --clobberwithout any cleanup, with no commit naming the failures. It also names the case remembered as "no artifacts, so no cleanup" (BAF 2026-07-12, the attach job dying atdownload-artifact, the intended fail-loud path) and thatgithub-snapshotruns only on a manual dispatch since 2026-06-18.crossrepostatus.md: the release-assets bullet follows.The workflow change itself is bernardladenthin/java-llama.cpp#531, bernardladenthin/BitcoinAddressFinder#386, bernardladenthin/srcmorph#224 and bernardladenthin/streambuffer#178.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AytmJF9faEiQEVt6eetQS2
Generated by Claude Code