139 old CI artifacts cleared, about 5.35 GB, across two repositories
Every change pushed to Satsuma's repositories triggers CI, automated checks that build and test the code, and those runs can save their output on GitHub as artifacts. All 139 old artifacts were deleted, about 5.35 GB in total: 137 in satsuma-engineering, the repository behind this site, which came to 5.3 GB of dist build output at about 40 MB each and had been kept since July, and 2 small ones in satsuma-explorer, the repository behind the public block explorer. None remain in either repository. The work was done with Claude in Claude Code.
Nothing depended on the deleted files, since no workflow reads them back.
The session also named the cause: "This will fill up again. The engineering CI uploads a 40 MB build on every push to main, including the nightly pipeline pushes, and keeps each for GitHub's default 90 days." A commit changes CI to keep the build artifact for 3 days instead of 90. Whether to keep that upload at all, or drop it, stayed open.
The explorer's CI is not yet confirmed green. GitHub recalculates storage usage every 6 to 12 hours, and a re-run before then may still hit the old quota.
- ci: keep the build artifact for 3 days instead of 90The explorer
- Deleting all old CI artifacts in both satsuma-engineering and satsuma-explorer
- Nothing depended on the deleted artifacts, since no workflow reads them back
- Whether to keep the build upload with a short retention or drop the upload entirely
- Explorer CI is expected to go green on the first run after GitHub recalculates storage, every 6 to 12 hours; a re-run before then may still hit the old quota