joakimp/pi-devbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

0 Releases 60 Tags

RSS Feed
  • v1.8.4 2ebf00d6d4
    Compare

    v1.8.4: the om fix lands upstream, pi-atelier v0.8.2, todo edit
    Lint / hadolint (push) Successful in 9s
    Details
    Lint / actionlint (push) Successful in 22s
    Details
    Publish Docker Image / resolve-versions (push) Successful in 19s
    Details
    Publish Docker Image / base-decide (push) Successful in 11s
    Details
    Publish Docker Image / build-base (push) Successful in 42m16s
    Details
    Publish Docker Image / smoke-studio (push) Successful in 5m0s
    Details
    Publish Docker Image / smoke (push) Successful in 19m0s
    Details
    Publish Docker Image / build-variant-studio (push) Successful in 17m38s
    Details
    Publish Docker Image / build-variant (push) Successful in 28m36s
    Details
    Publish Docker Image / update-description (push) Successful in 8s
    Details
    Publish Docker Image / promote-base-latest (push) Successful in 10s
    Details

    joakimp released this 2026-08-22 21:19:48 +02:00 | 88 commits to main since this release

    Headline: pi-observational-memory 37986b6 -> ce9fc98. The ambient-credential
    gate fix (6f694e6 + 699ccc7) was merged upstream as PR #52 on 2026-08-22,
    closing issue #51, so this release picks it up through the ordinary
    PI_OBSMEM_REF=master path with nothing carried locally. Every image up to
    and including v1.8.3 silently recorded zero observations on a Bedrock host
    using ambient AWS credentials; from this one on, /opt is the fix and the
    settings.json packages[] workaround should be deleted (verify against
    /etc/pi-devbox/build-manifest.json first). npm still ships the broken 3.0.4,
    which does not matter here because the image clones the ref instead.

    Pin bump: PI_ATELIER_REF / PI_ATELIER_VERSION v0.8.1 -> v0.8.2, audited per
    the floor note above the ARG. The only version in between is 0.8.2 itself and
    both its entries are Workspace-Pulse-internal (inspection coalescing and
    serialization; fresh inspection guaranteed at Turn end, retired sessions can
    no longer publish stale results). Nothing touches pi's private TUI renderer,
    which is the coupling behind the 0.6.0/0.7.0-under-pi-0.84 startup hang, and
    pi is unchanged at 0.84.2 - so the bump stays outside that risk class.

    Also baked by this build, no pin needed: pi-extensions 98eb07b -> 2022887
    (the todo edit action), pi-fork 4a09af4 -> f1ff808, pi-studio 0.9.44 ->
    v0.9.48, mempalace-toolkit b609cf5 -> fd8b15f (docs only - the pi-session
    false-success guard was already baked in v1.8.3, confirmed by ancestry),
    aws-cli 2.36.24 -> 2.36.29 and the other *_VERSION=latest tools.

    README: the pin table also said mempalace 3.6.0, stale since v1.8.3 bumped it
    to 3.7.1. Fixed in passing.

    Unchanged and verified current: pi 0.84.2 (npm latest, published 2026-08-14),
    MEMPALACE_VERSION 3.7.1 (PyPI latest), pi-toolkit 0e1369e.

    Downloads