Repository navigation
ci: stop persisting dev build artifacts - #37
Merged
Merged
Conversation
build.yml uploaded a compiled binary on every push and PR across a 3-OS matrix with no retention-days, so each fell back to the repo default of 90 days. That accumulated ~2.4GB of live artifacts and hit the org's 500MB Actions storage cap, blocking new uploads org-wide. The build job still compiles on all three platforms, so the matrix keeps its signal; it just stops keeping the output. Release binaries are unaffected -- release-please builds its own and attaches them to the GitHub Release. Also pin the release binary handoff to retention-days: 1. It only needs to survive between jobs in the same run. 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
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
build.ymluploaded a compiled binary on every push and PR across a 3-OS matrix with noretention-days, so each fell back to the repo default of 90 days.That accumulated ~2.4 GB of live artifacts — 99.9% of all Actions storage across the entire org — and hit the free plan's 500 MB cap:
This blocked artifact uploads org-wide, including
neon-node-flutter-app#3, which needs storage for real release builds.What changed
Upload artifactstep frombuild.yml. The build job still compiles on all three platforms, so the matrix keeps its signal — it just stops keeping the output. These were dev binaries from every push, reproducible by re-running the workflow.retention-days: 1inrelease-please.yml. It only needs to survive betweenbuild-and-uploadandupload-release-assetsin the same run; 90 days was the recurrence risk.Release binaries are unaffected
release-please.ymlbuilds its own binaries and attaches them to the GitHub Release viagh release upload, gated onrelease_created. That path is independent ofbuild.ymland untouched. The Docker digest upload was already atretention-days: 1.Also done outside this PR
Purged the 110 existing live artifacts in this repo (2474 MB → 0). Artifacts in other org repos (2.81 MB of SARIF scan uploads) were left alone.