wharfy 0.6.1 — config now tells you what went wrong

Jul 6, 2026

What was wrong

When wharfy config failed it returned only internal error and exit status 1, with no detail — while wharfy status in the same directory worked. The internal go list call could fail, and wharfy surfaced it as an internal error while throwing away the message (stderr) that said why.

Before

$ wharfy config
✗ internal error
  ! internal: exit status 1
$ echo $?
0

After

$ wharfy config
✗ cannot resolve 'main'
  ! main_ambiguous: go list ./...: exit status 1: directory prefix . does not
    contain main module or its selected dependencies
    set 'main' in wharfy.yaml to the build target package (e.g. ./cmd/…)
$ echo $?
1

The real cause (go list’s stderr) comes through. Even when main can’t be resolved, the effective config still lands in data under --json. And ok:false now means a non-zero exit code.

Getting it

brew upgrade wharfy / scoop update wharfy / go install github.com/ShiroDoromoto/wharfy/cmd/wharfy@latest. On Linux, from the apt / yum repo.