• v1.8.7 f645e6654f

    smoke: fix the snapshot canary that blocked v1.8.7, and make it bidirectional
    Lint / hadolint (push) Successful in 15s
    Lint / actionlint (push) Successful in 27s
    Publish Docker Image / resolve-versions (push) Successful in 1m5s
    Publish Docker Image / base-decide (push) Successful in 12s
    Publish Docker Image / build-base (push) Successful in 41m8s
    Publish Docker Image / smoke (push) Successful in 4m49s
    Publish Docker Image / smoke-studio (push) Successful in 18m28s
    Publish Docker Image / build-variant (push) Successful in 15m46s
    Publish Docker Image / promote-base-latest (push) Successful in 11s
    Publish Docker Image / update-description (push) Successful in 20s
    Publish Docker Image / build-variant-studio (push) Successful in 16m52s

    joakimp released this 2026-08-26 08:09:09 +02:00 | 75 commits to main since this release

    Run 589 built the base cleanly and then failed both smoke jobs 81-passed/1-failed
    on 'mempalace skill snapshot is current'. That canary greps a phrase from the
    vendored mempalace skill to detect a stale snapshot, and the phrase it pinned was
    'Attribute what you file yourself' — the heading of the hand-stamping instruction
    that THIS release withdraws. So it fired correctly: the snapshot changed and the
    expectation did not. Every publish job was skipped, so nothing reached the
    registry and v1.8.7 was never consumed.

    Rather than bump the string:

    • the assertion is now BIDIRECTIONAL — the new phrase must be present AND the
      withdrawn one absent. A one-way canary only catches half the drift: it cannot
      notice a re-vendored stale snapshot that happens to contain the pinned phrase.
      Verified against v1.8.6's snapshot, which now correctly fails.
    • the comment records the structural limit rather than just the fix: a phrase
      canary can only ever detect 'older than what I remembered to pin', never
      'older than skillset main'. Only a diff against the skillset repo can do that,
      which is now a Still-open item — it needs a CI clone credential for a private
      repo, i.e. a policy decision, not a code change.

    Changelog consolidated: the SSH sidecar multiplexing default moves from
    Unreleased into v1.8.7, since the retag will sit on a commit that contains it,
    and the v1.8.7 summary now records the failed first attempt rather than quietly
    presenting the second one as the whole story.

    Downloads