Repository navigation
docs: correct the keystore history cleanup procedure - #48
Merged
Merged
Conversation
The documented command does not run: --sensitive-data-removal is not a flag in current git-filter-repo, so following the README as written fails before it rewrites anything. Replace it with the procedure actually used on 2026-08-16, and record the three things that were not obvious until it was run: refs/pull/* cannot be rewritten. GitHub rejects writes to them, so the old commits stay pinned and the leaked blob is still reachable by its SHA through the API even though a fresh clone no longer contains it. Removing it completely needs a GitHub Support request. Force pushing the tags retriggers Android Release Build for every existing tag, which would have rebuilt and promoted releases that were deliberately demoted to prereleases. Local branches in an existing clone keep pointing at the old history, so pushing one restores the leak. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Why
The README's cleanup command does not run —
--sensitive-data-removalis not a flag in currentgit-filter-repo, so following the documented procedure fails before rewriting anything.The rewrite was performed on 2026-08-16. This documents what was actually done and three consequences that only surfaced during the run.
What changed
refs/pull/*cannot be rewritten. GitHub rejects writes to those refs, so old commits stay pinned. A fresh clone is clean, but the leaked blob is still reachable by SHA through the API. Fully removing it requires a GitHub Support request.Android Release Buildfor every tag. Those runs were cancelled; left alone they would have rebuilt and promoted v1.1.1/v1.1.2, which are deliberately prereleases.Also notes that the leaked key is permanently retired and the current upload key is a separate one generated on 2026-08-16.
🤖 Generated with Claude Code