joakimp/opencode-devbox
Public Access
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

0 Releases 64 Tags

RSS Feed
  • v1.14.44 a3ff601bf0
    Compare

    Bump opencode 1.14.42 -> 1.14.44; close v1.14.42 omos-with-pi gap
    Validate / docs-check (push) Successful in 18s
    Details
    Validate / validate-base (push) Successful in 11m46s
    Details
    Validate / validate-omos (push) Successful in 13m32s
    Details
    Validate / validate-with-pi (push) Successful in 13m20s
    Details
    Validate / validate-omos-with-pi (push) Successful in 19m23s
    Details
    Publish Docker Image / smoke-base (push) Successful in 11m46s
    Details
    Publish Docker Image / smoke-omos (push) Successful in 13m45s
    Details
    Publish Docker Image / smoke-with-pi (push) Successful in 13m13s
    Details
    Publish Docker Image / smoke-omos-with-pi (push) Successful in 15m47s
    Details
    Publish Docker Image / build-base (push) Successful in 42m18s
    Details
    Publish Docker Image / build-omos (push) Successful in 52m1s
    Details
    Publish Docker Image / build-with-pi (push) Successful in 46m28s
    Details
    Publish Docker Image / build-omos-with-pi (push) Successful in 54m36s
    Details
    Publish Docker Image / update-description (push) Successful in 14s
    Details

    joakimp released this 2026-05-09 22:33:16 +02:00 | 47 commits to main since this release

    opencode-ai 1.14.44 published 20:26 UTC (1.14.43 skipped upstream).
    Bumping to 1.14.44 instead of re-running the failed v1.14.42 build
    gives us the same 3h CI cost and picks up upstream bug fixes.

    Closes the v1.14.42 omos-with-pi gap. The v1.14.42 tag's
    build-omos-with-pi job failed during publish: oh-my-opencode-slim@1.0.7
    had been published with a dependency on @opencode-ai/sdk@1.14.44, and
    our build hit the npm registry within ~2 minutes of that SDK version
    landing -- before the tarball had propagated across npm's CDN. The
    manifest's dist-tags.latest pointed at 1.14.44 but a tarball fetch on
    /-/sdk-1.14.44.tgz returned 404. Tarball is now fully fetchable.

    Result on Docker Hub once v1.14.44 publishes:
    v1.14.42 / latest -> stable (3 of 4 variants)
    v1.14.42-omos / latest-omos -> stable
    v1.14.42-with-pi / latest-with-pi -> stable
    v1.14.42-omos-with-pi -> NEVER PUBLISHED (404 if pulled)
    latest-omos-with-pi -> still v1.14.41b until v1.14.44
    v1.14.44 / latest -> NEW (replaces latest)
    v1.14.44-omos / latest-omos -> NEW
    v1.14.44-with-pi / latest-with-pi -> NEW
    v1.14.44-omos-with-pi / latest-omos-with-pi -> NEW (closes the gap)

    CHANGELOG: v1.14.44 entry added with the propagation-race rationale,
    v1.14.42 entry annotated with the known gap. Reverse-chrono preserved.

    Downloads