build: clear Go cache between platform builds in release script
What changed, and why it matters
This commit changes the release build script to clear Go's temporary build cache after compiling for each platform. It is a routine build-hygiene fix to prevent disk space from running out during long release builds. There is no security vulnerability here.
No security action needed. Treat as normal build/maintenance improvement.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch adds go clean -cache after each cross-compilation step in scripts/release.sh. This removes per-platform intermediate build artifacts while keeping the module cache intact. It addresses disk-space growth during the 15-platform release process and has no effect on runtime behavior, cryptographic operations, or produced binaries.
Changed components
scripts/release.shInspect captured patch +3 / −0
diff --git a/scripts/release.sh b/scripts/release.sh
index 3ae8c1e..56b7c3c 100755
--- a/scripts/release.sh
+++ b/scripts/release.sh
@@ -193,6 +193,9 @@ required Go version ($goversion)."
env CGO_ENABLED=0 GOOS=$os GOARCH=$arch GOARM=$arm go build -v -trimpath -ldflags="${ldflags}" -tags="${buildtags}" ${PKG}/cmd/lncli
popd
+ # Clear Go build cache to prevent disk space issues during multi-platform builds.
+ go clean -cache
+
# Add the hashes for the individual binaries as well for easy verification
# of a single installed binary.
shasum -a 256 "${dir}/"* >> "manifest-$tag.txt"
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.