fix: reduce GoReleaser memory usage to prevent OOM on GitHub runners

bindercli pulls in 923 packages (~1.2M lines of generated code).
On the free GitHub runner (2 cores, 7GB RAM), parallel package
compilation during arm64 cross-compilation exhausts memory, causing
"hosted runner lost communication" crashes.

Two changes:
- Add -p 1 flag to the bindercli build so go build compiles one
  package at a time, reducing peak memory.
- Pass --parallelism=1 to GoReleaser so builds run sequentially,
  preventing two large compilations from overlapping.

Author: xaionaro@dx.center

.github/workflows/ci.yml

@@ -70,7 +70,7 @@ jobs:
         uses: goreleaser/goreleaser-action@v6
         with:
           version: '~> v2'
-          args: release --clean
+          args: release --clean --parallelism=1
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 

.goreleaser.yml

@@ -28,6 +28,12 @@ builds:
     goarch:
       - amd64
       - arm64
+    # bindercli pulls in 923 packages (~1.2M lines of generated code).
+    # Compiling packages in parallel exhausts the 7GB GitHub runner RAM
+    # during cross-compilation. Limit to 1 concurrent package compilation.
+    flags:
+      - -p
+      - '1'
     ldflags:
       - -s -w