• AGENTS: add 'Upstream sources' section pointing at anomalyco/opencode
    Validate / base-change-warning (push) Successful in 14s
    Validate / docs-check (push) Successful in 16s
    Validate / validate-base (push) Successful in 3m39s
    Validate / validate-with-pi (push) Successful in 4m8s
    Validate / validate-omos (push) Successful in 6m46s
    Validate / validate-omos-with-pi (push) Successful in 13m35s
    Publish Docker Image / build-base (push) Has been cancelled
    Publish Docker Image / smoke-base (push) Has been cancelled
    Publish Docker Image / smoke-omos (push) Has been cancelled
    Publish Docker Image / smoke-with-pi (push) Has been cancelled
    Publish Docker Image / smoke-omos-with-pi (push) Has been cancelled
    Publish Docker Image / build-variant-base (push) Has been cancelled
    Publish Docker Image / build-variant-omos (push) Has been cancelled
    Publish Docker Image / build-variant-with-pi (push) Has been cancelled
    Publish Docker Image / build-variant-omos-with-pi (push) Has been cancelled
    Publish Docker Image / promote-base-latest (push) Has been cancelled
    Publish Docker Image / update-description (push) Has been cancelled
    Publish Docker Image / base-decide (push) Failing after 14m23s

    joakimp released this 2026-05-23 19:26:46 +02:00 | 27 commits to main since this release

    Tonight's v1.15.10 release surfaced a documentation drift footgun: I
    checked github.com/sst/opencode (a fork) for release notes instead of
    the canonical github.com/anomalyco/opencode. Empty bodies on sst led
    me to write 'upstream releases ship empty bodies and no CHANGELOG'
    in the v1.15.10 CHANGELOG, which was wrong — anomalyco's release
    pages have rich Core/TUI/Desktop/SDK sections.

    Added a new 'Upstream sources — where to look up release notes'
    section between 'Versioning scheme' and 'Critical conventions',
    documenting:

    • Canonical upstream for opencode-ai (anomalyco/opencode), pi
      (npm tarball CHANGELOG.md), other floated tools.
    • The sst/opencode trap explicitly named so future-pi doesn't
      repeat the mistake.
    • Working fetch commands as muscle memory: 'npm view ... time'
      for latest stable filtering, 'curl /releases/tags/' for body,
      'npm pack' for pi's changelog.

    No CI implications, doc-only.

    Downloads