• v0.31.2 d2982a7a15

    v0.31.2 — preflight stops repeating itself
    All checks were successful
    CI / gate (push) Successful in 1m26s
    CI / image (push) Successful in 14s
    Stable

    joeyr released this 2026-08-22 21:19:14 -05:00 | 3 commits to main since this release

    Two small things in the Gmail tenant's preflight, both spotted by reading its
    boot log rather than by any test.
    No tool, argument or description changed, so
    no reconnect — a service image update is enough.

    Fixed

    • oauth_storage ran twice on this tenant. The shared OAuth block runs it
      for every tenant, and the Gmail branch ran it again, so the container probed
      the same directory twice and printed check=oauth_storage twice. Nothing
      broke, and that is the problem with it: an operator counting preflight lines
      against the docs finds one too many and has to work out which is real.

    • Gmail dialled out to IMAP even when a local check had already failed. The
      other three tenant branches guard on local_ok; this one did not, which was
      an oversight from when the tenant was added rather than a decision. A
      container about to report a broken timezone or a missing secret would open an
      IMAP connection first and put a second, less self-explanatory failure line in
      front of the one that actually says what is wrong.

    Notes

    • Neither was reachable from the suite, so the tests are new and are written
      as properties over every tenant
      — "no check runs twice on any tenant" and
      "a broken local config stops the network checks on every tenant" — rather than
      as two assertions about Gmail. Both defects arrived with a new tenant, and
      the next one would arrive the same way.

      Confirmed by restoring the old branch and watching both fail, per A new guard
      is not proved until it has been broken
      in CLAUDE.md.

    Downloads