fix: getenv treats an explicitly-empty value as unset #85

Merged
benvin merged 1 commits from benvin/getenv-lookupenv into master 2026-07-02 22:09:09 +10:00

1 Commits

Author SHA1 Message Date
unkinben 1bed296c35 fix: let getenv honour an explicitly-empty env var
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/test Pipeline was successful
ci/woodpecker/pr/build Pipeline was successful
getenv fell back to the default whenever os.Getenv returned empty, so an
intentionally-empty override was impossible. Use os.LookupEnv to
distinguish unset from empty.

Refs #69
2026-07-02 00:28:40 +10:00