SansanandClaude Sonnet 5
5492dd8cf1
CI / go (push) Successful in 43s
CI / sqlc (push) Successful in 7s
CI / web (push) Successful in 18s
Release / build-tui (amd64, linux) (push) Successful in 25s
Release / build-tui (amd64, darwin) (push) Successful in 26s
CI / docker (push) Successful in 1m0s
Release / build-tui (arm64, darwin) (push) Successful in 21s
Release / build-tui (amd64, windows) (push) Successful in 21s
Release / build-tui (arm64, linux) (push) Successful in 43s
Release / build-web (push) Successful in 38s
Release / build-gui (amd64, windows, gcc-mingw-w64-x86-64) (push) Successful in 57s
Release / build-gui (amd64, linux, libgl1-mesa-dev xorg-dev libwayland-dev libxkbcommon-dev) (push) Successful in 1m4s
Release / build-docker (push) Successful in 47s
Release / release (push) Successful in 24s
The Docker image (build-docker) is the real distribution path for the server; a raw completed-api binary alongside it was a redundant artifact nobody was going to run directly. Renamed build-go -> build-tui since it now only builds the tui, which is a real CLI people do run on their own machine. Updated the release job's `needs:` and stale comments that still said build-go. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>