Disable cgo by default (#31)

Co-authored-by: Mislav Marohnić <[email protected]>

README.md

@@ -33,6 +33,14 @@ When the `release` workflow finishes running, compiled binaries will be uploaded
 
 You can safely test out release automation by creating tags that have a `-` in them; for example: `v2.0.0-rc.1`. Such Releases will be published as _prereleases_ and will not count as a stable release of your extension.
 
+To maximize portability of built products, this action builds Go binaries with [cgo](https://pkg.go.dev/cmd/cgo) disabled. To override that, set the `CGO_ENABLED` environment variable:
+
+```yaml
+- uses: cli/gh-extension-precompile@v1
+  env:
+    CGO_ENABLED: 1
+```
+
 ## Extensions written in other compiled languages
 
 If you aren't using Go for your compiled extension, you'll need to provide your own script for compiling your extension:

build_and_release.sh

@@ -46,7 +46,7 @@ else
     if [ "$goos" = "windows" ]; then
       ext=".exe"
     fi
-    GOOS="$goos" GOARCH="$goarch" go build -trimpath -ldflags="-s -w" -o "dist/${p}${ext}"
+    GOOS="$goos" GOARCH="$goarch" CGO_ENABLED="${CGO_ENABLED:-0}" go build -trimpath -ldflags="-s -w" -o "dist/${p}${ext}"
   done
 fi