Grant Whitmer c60bfb2b89 I-12: fail the build when COMMIT_SHA is empty ...

/version went null after a deploy — the exact "service cannot name its own
commit" defect this project was built to prevent, caught by its own honesty
check.

Cause: the sed replaced "" with "" (a no-op when COMMIT_SHA is empty) and the
grep then matched that same empty string, so the guard verified nothing. A build
with no COMMIT_SHA passed and shipped a container reporting commit_sha: null.

Now the build fails loudly instead.

Second cause of the stale deploy, and it was mine: an earlier `git commit
--amend` + force-push rewrote history the Veron deploy checkout was already
sitting on, leaving it divergent so `git pull -q` failed SILENTLY (-q hid
"Need to specify how to reconcile divergent branches"). Two lessons: do not
force-push a branch a deploy checkout tracks, and do not pull with -q in a
deploy script.

Co-Authored-By: Claude (Fable 5) <noreply@anthropic.com>

2026-08-13 23:27:38 -04:00

..

app

SECURITY: make EPT routing independent of signature well-formedness

2026-08-13 23:23:50 -04:00

tests

I-12: fail the build when COMMIT_SHA is empty

2026-08-13 23:27:38 -04:00