Repository navigation
fix(build): default build version to dev instead of a stale date - #58
Conversation
The static default (2026.3.3) had drifted four releases behind by the time anyone built from source (#31). Release builds are unaffected: the release flow injects -Dversion from the tag, exactly as before. Dev builds now self-report as vdev — matching NullHub's convention — so a stale date can never masquerade as a version again. Fixes #31
There was a problem hiding this comment.
Checked #31 and traced the version through build_options, src/version.zig, the CLI/startup banner and /health. They already share one source, so changing the build fallback fixes all runtime reporting paths. Docker already defaults VERSION to dev; both the Docker release job and the reusable nullbuilder v1 release workflow explicitly pass -Dversion, so release stamping is preserved. The other 2026.3.3 occurrences are documentation examples, not competing runtime defaults.
Validation on da0008e with Zig 0.16.0: all 356 unit tests passed; a normal build prints nullboiler vdev; rebuilding with -Dversion=2026.5.29 prints nullboiler v2026.5.29. The change merges cleanly with main. No blocking findings.
Additional integration validation: merged current main (a7b7605) into the PR in an isolated local worktree; all 370 tests passed, and both default and explicitly stamped version outputs remained correct.
Fixes #31.
-Dversionfrom the tag (v2026.5.29 binaries already report correctly).dev(NullHub's convention) instead of a hard-coded date that had drifted four releases behind.zig build testgreen;zig-out/bin/nullboiler --version→vdevon this branch; tagged release build (-Dversion=v2026.5.29) still stamps correctly.Fixes #31