• v1.15.4b: omos-with-pi threshold bump + update-description partial-publish fix
    Validate / docs-check (push) Successful in 7s
    Validate / base-change-warning (push) Successful in 20s
    Validate / validate-base (push) Successful in 3m36s
    Publish Docker Image / base-decide (push) Successful in 13s
    Publish Docker Image / build-base (push) Has been skipped
    Validate / validate-with-pi (push) Successful in 4m14s
    Validate / validate-omos (push) Successful in 7m1s
    Publish Docker Image / smoke-base (push) Successful in 3m37s
    Publish Docker Image / smoke-omos (push) Successful in 4m39s
    Publish Docker Image / smoke-omos-with-pi (push) Successful in 5m7s
    Publish Docker Image / smoke-with-pi (push) Successful in 6m24s
    Validate / validate-omos-with-pi (push) Successful in 15m59s
    Publish Docker Image / build-variant-base (push) Successful in 14m12s
    Publish Docker Image / build-variant-omos (push) Successful in 19m29s
    Publish Docker Image / build-variant-with-pi (push) Successful in 23m7s
    Publish Docker Image / build-variant-omos-with-pi (push) Successful in 26m16s
    Publish Docker Image / promote-base-latest (push) Has been skipped
    Publish Docker Image / update-description (push) Successful in 8s

    joakimp released this 2026-05-18 22:30:59 +02:00 | 33 commits to main since this release

    Recovery for v1.15.4's partial publish (omos-with-pi exceeded 3500 MB
    smoke threshold; other 3 variants published cleanly). Two changes:

    1. omos-with-pi threshold 3500 -> 3700 MB. Compounded growth from
      opencode 1.15.0 -> 1.15.4 (4 patch versions) plus pi 0.74.0 -> 0.75.3
      (minor + 3 patches) summed in the omos-with-pi variant, just over
      the existing limit. Same pattern as prior threshold bumps (v1.14.31c,
      v1.15.0b). Restores ~150 MB headroom for routine apt-upgrade drift.

    2. update-description workflow bug fix. Pre-existing latent bug exposed
      by v1.15.4's partial publish: update-description.needs includes all 4
      build-variant-* jobs, and gitea Actions' default behavior is
      'skipped need => skip dependent' \u2014 even when the job's own if:
      condition is satisfied. So when build-variant-omos-with-pi was
      skipped (because its smoke failed), update-description cascaded into
      a skip too, and Hub description didn't refresh on v1.15.4 despite
      3 variants publishing.

      Fix: wrap if: in always() + explicit success check on the base
      variant. Same fix applied to promote-base-latest preemptively (it
      has the same latent bug, currently masked by the cache-hit gate).

    No image-side changes \u2014 cache hit on base-35ee5fe7861a.

    Downloads