How a lightweight Go tool and companion package eliminated the fragile bash gymnastics we'd been writing for years. The Problem With .env Files in Pipelines Every team has the same archaeology story. Someone wrote a deployment script three years ago that does something like this: grep "^DB_HOST=" .env | cut -d= -f2 Enter fullscreen mode Exit fullscreen mode Then someone else needed to handle quoted values, so it became: grep "^DB_HOST=" .env | cut -d= -f2 | tr -d '"' Enter fullscreen mode Exit fullscreen mode Then a third person needed to check whether a variable existed before deploying, and now you have forty lines of bash doing something that should take one. The file accumulates. Nobody touches it. It works until it doesn't. goenv by Andrei Merlescu solves this with two things: a compiled CLI binary you can drop into any pipeline, and a typed Go package for applications that need to read env vars with real type safety and validation.…