• v1.13.3 41a5d032f0

    v1.13.3 — put the running build on the first line, by itself
    All checks were successful
    CI / build-and-test (push) Successful in 1m44s
    CI / docker-build (push) Successful in 24s
    Stable

    joeyr released this 2026-08-25 21:13:00 -05:00 | 64 commits to main since this release

    Added

    • The running build is now the first line of the boot log, on its own.

      2026-08-25 21:09:59 INF bot/version > aufhocker v1.13.3
      

      The version was previously one field among three on the sixth line
      (Starting Aufhocker Discord Bot... | environment=… nodeVersion=… version=…),
      below five lines emitted by import side effects — unfindable by a human
      scrolling container output. That cost real time during the 1.13.x rollout: a
      deploy that had genuinely rolled forward was read as one that had not.

      Emitted from a new src/utils/bootBanner.ts at import time, not from
      main(). Everything appearing above main()'s first line does so from its own
      import side effects (the database pool, the shutdown handler, the admin
      services), and ES module imports evaluate in source order — so importing the
      banner first in index.ts is the only thing that puts it at the top. There is
      no import-order lint rule, so that import carries a comment saying it must
      stay first.

      Deliberately field-free, since a bare message is what makes it scannable. New
      bot/version phase so it can be grepped on its own. The structured version
      fields on the startup and config/runtime lines are unchanged for anything
      parsing the logs.

    Downloads