ci: use enhanced cleanup action in release workflow
What changed, and why it matters
This commit changes the release build pipeline to use a more thorough disk cleanup step before compiling. It is purely a reliability improvement for GitHub Actions builds and has no security relevance.
No security action needed. Treat as a normal CI/maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit replaces an inline shell command (rm -rf /opt/hostedtoolcache && mkdir -p /opt/hostedtoolcache/go) in .github/workflows/release.yaml with a reusable local action (./.github/actions/cleanup-space). The stated purpose is to free more disk space (20–25 GB) so multi-platform release builds, especially Windows ARM, no longer fail due to disk exhaustion. The diff shows only this workflow change; no application code, secrets, permissions, or network behavior are modified.
Changed components
.github/workflows/release.yamlInspect captured patch +1 / −1
diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
index 974ff84..0e450de 100644
--- a/.github/workflows/release.yaml
+++ b/.github/workflows/release.yaml
@@ -28,7 +28,7 @@ jobs:
fetch-depth: 0
- name: cleanup space
- run: rm -rf /opt/hostedtoolcache && mkdir -p /opt/hostedtoolcache/go
+ uses: ./.github/actions/cleanup-space
- name: setup go ${{ env.GO_VERSION }}
uses: actions/setup-go@v5
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.