Released on March 11, 2026, gogitup v0.1.5 brings a targeted but powerful improvement to how you manage your Go toolchain. This update focuses on providing developers with more precise control over their build environments, ensuring that the tools you install are exactly as you need them.

What’s new

The headline feature of v0.1.5 is the introduction of the cgo_enabled configuration parameter.

Previously, gogitup relied on the CGO_ENABLED environment variable of your current process. Now, you can explicitly define this behavior in your configuration file. By setting cgo_enabled to true or false, gogitup will override the system’s environment variable during both install and update operations.

Why it matters

For many Go developers, the choice between using CGO and producing a purely static binary is critical.

Whether you are deploying tools to minimal containers (like Alpine or Scratch) where CGO dependencies can cause “file not found” errors, or you’re working in a restricted environment where CGO is unsupported, having this control built directly into your tool manager simplifies your workflow. You no longer need to manually set environment variables before running gogitup; your preference is now codified in your configuration.

Upgrade and Installation

Updating to v0.1.5 is straightforward. You can pull the latest version directly using the Go toolchain:

go install github.com/UnitVectorY-Labs/gogitup@latest

Once updated, you can add cgo_enabled: false (or true) to your config file to start managing your CGO preferences. If you choose not to use this new setting, gogitup will continue to function exactly as before, inheriting your system’s default CGO_ENABLED value.

This post was AI-generated using the model unsloth/gemma-4-31B-it-GGUF:UD-Q5_K_XL. Generated on April 11, 2026, based on the gogitup repository and v0.1.5 release. Author: release-storyteller