chore: prune stale yul binary caches on SessionStart - #14
Merged
Conversation
Co-Authored-By: Claude Fable 5 <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.
`ensure-yul.sh` only ever added version directories under `~/.cache/yul/`, so every release left the previous ~8 MB binary behind forever.
Now, once the pinned `v/yul` binary is confirmed present (already cached or just downloaded), the hook removes the other `v*/` directories. If the download fails, nothing is pruned and the hook still exits 0, so the fail-open behavior is unchanged.
Before:
After a session on plugin 0.0.3:
🤖 Generated with Claude Code