fix: untrack build/ artifacts so stale zips can never ship as release assets#170
Merged
Conversation
… assets A git-tracked build/data-machine-socials.zip (committed 2026-03-22 at v0.8.1) was restored by 'git checkout --' during release recovery on 2026-06-06 and uploaded as the v0.14.0 GitHub release asset. homeboy deploy then shipped 0.8.1 to production 3x with green status. Untracking build/ kills every link in that chain: no stale blob to restore, no dirty-tree preflight failure from a rebuilt artifact, and 'git checkout -- build/' becomes a no-op. Release zips are built fresh by the homeboy wordpress extension's release.package step and attached to the GitHub release; git never needs to carry them. Closes #169
Contributor
Homeboy Results —
|
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
1 participant
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
git rm -r --cached build/— untracksbuild/data-machine-socials.zip(the stale v0.8.1 blob from March that became the v0.14.0 release asset) plus the compiled JS/CSS artifacts.gitignorestanza with a hardbuild/ignore and an explanatory commentWhy
Closes #169. The v0.14.0 release shipped a v0.8.1 zip to production for 6 days because:
build/*.zipblob (committed 2026-03-22, containing 0.8.1) sat in the tree for 11 weekshomeboy releaserebuilt it correctly → file showedM→ re-run failedpreflight.working_treegit checkout -- build/data-machine-socials.zip→ restored the stale March blobgh release create ... build/data-machine-socials.zipuploaded it as the v0.14.0 assethomeboy deployshipped 0.8.1 with green status, 3×SHA-256 proof: uploaded asset
d278567a…== git blobv0.14.0:build/data-machine-socials.zip.Untracking breaks every link: no stale blob exists, a rebuilt artifact can't dirty the tree, and
git checkout -- build/is a no-op.Notes
release.packagebuilds the zip fresh and the GitHub release carries it.--cached); only the index entries are removed.