No Dockerfile install change here — pi-devbox FROMs joakimp/opencode- devbox:base-latest which gained gitleaks (and explicit acknowledgment of git-crypt) in opencode-devbox commit adding both to the base layer. The next pi-devbox release built against a fresh base-latest digest inherits both with zero work on this side. CHANGES Dockerfile — comment block at top updated to name git-crypt + gitleaks in the 'inherited from base' toolset enumeration. Helps future readers: one less reason to think 'I need to install gitleaks here'. CHANGELOG.md — new Unreleased entry pointing at the opencode-devbox base-side change for full detail. Will be promoted whenever the next pi-devbox release ships (probably alongside the next pi npm bump past 0.75.5). Holding off on tagging — pi upstream still at 0.75.5, baseline release v0.75.5b is already current with that. Will ride along with next pi bump.
5.4 KiB
Changelog
All notable changes to the pi-devbox container image.
Tags follow the pi npm version: v{pi_version}[letter] — bare tag for the first build on a new pi release, letter suffix (b, c, …) for container-level rebuilds on the same version.
Unreleased
Inherited from opencode-devbox base: gitleaks + git-crypt
No Dockerfile change here — just a note that the next pi-devbox release built against a fresh joakimp/opencode-devbox:base-latest will include gitleaks (newly added to the base) and git-crypt (was always installed via apt; just wasn't called out). Both are useful inside the container for repos that use a gitleaks pre-commit hook or git-crypt-encrypted canonical config and don't want host-side dependencies. See opencode-devbox CHANGELOG Unreleased for the base-side details.
v0.75.5b — 2026-05-23
Recovery release fixing a silent cache-hit regression discovered in the v0.75.5 image. All four releases v0.74.0 through v0.75.5 had been shipping the same image bytes because the Dockerfile's npm install -g @earendil-works/pi-coding-agent (bare, when PI_VERSION=latest) produces an identical layer-hash across builds. Combined with the registry buildcache, Docker reused the layer from whatever pi version was current when the cache was first populated.
Verification: docker manifest inspect joakimp/pi-devbox:vX.Y.Z showed identical SHA256 digests on both linux/amd64 and linux/arm64 for v0.74.0, v0.75.3, v0.75.4, v0.75.5. Users on :latest were getting whatever pi version was baked into the v0.74.0 build (probably 0.74.0 itself).
- Workflow fix: Both
smokeandpublishjobs now derivePI_VERSIONfromgithub.ref_name(e.g.v0.75.5b→0.75.5) and pass it as a build-arg. The Dockerfile's existingif PI_VERSION=latestbranch never fires in CI now — always takes the@${PI_VERSION}branch — so the layer-hash includes the version and cache invalidates correctly. - Smoke test: New
run_expecthelper assertspi --versionoutput containsEXPECTED_PI_VERSION(passed from the resolve step). Would have caught this regression on v0.75.3 if it had existed. - Dockerfile: Comment added above
ARG PI_VERSION=latestdocumenting the cache-hit footgun and pointing at the workflow's resolve step + AGENTS.md gotcha. - AGENTS.md: New convention bullet explaining the cache-hit class of bug and noting the latent same-bug in opencode-devbox's
with-pivariants (currently masked by OPENCODE_VERSION bumps).
No image-side changes vs v0.75.5 intent — this build will produce the actual pi 0.75.5 image content that v0.75.5 was supposed to ship.
v0.75.5 — 2026-05-23
pi 0.75.4 → 0.75.5 bump (one upstream patch release, two days after v0.75.4).
Notable upstream changes (from pi's CHANGELOG):
- Cleaner read tool output (collapsed cards show only the read line; Ctrl+O expands).
- Faster file tools on Windows (async fs ops during streaming, image resize off the main TUI thread).
- More reliable package updates (
pi updatereconciles git-pinned refs without losing settings). - Custom Anthropic-compatible adaptive thinking via
compat.forceAdaptiveThinking. - Several bash/read tool card display fixes; macOS Bun clipboard sidecar resolution; per-session OpenCode-Zen routing headers; Amazon Bedrock token cap fix.
Plus a new pi 0.74.2 rescue release advising Node 20 users to upgrade Node before going to newer Pi versions — the devbox base image runs newer Node so this doesn't affect us, but worth noting for users running pi outside the devbox.
- Bump: pi
@earendil-works/pi-coding-agent@0.75.5baked at/usr/bin/pi(viaPI_VERSION=latestresolving to 0.75.5 at build time — no Dockerfile change needed). - No image-side changes from v0.75.4 beyond the pi npm version. Built on
joakimp/opencode-devbox:base-latestwhich itself is unchanged (cache-hit onbase-35ee5fe7861asince v1.14.50b).
v0.75.4 — 2026-05-21
pi 0.75.3 → 0.75.4 bump (one upstream patch release). Plus the AGENTS.md documentation-drift sweep clause that landed on main between v0.75.3 and now.
- Bump: pi
@earendil-works/pi-coding-agent@0.75.4baked at/usr/bin/pi(viaPI_VERSION=latestresolving to 0.75.4 at build time — no Dockerfile change needed). - AGENTS.md: documentation drift sweep as explicit pre-commit workflow step (commit
ae6253a). Companion clause added across the wider repo set the same day. - No image-side changes beyond the pi npm version. Built on
joakimp/opencode-devbox:base-latestwhich itself is unchanged (cache-hit onbase-35ee5fe7861asince v1.14.50b).
v0.75.3 — 2026-05-18
pi 0.74.0 → 0.75.3 bump (one upstream minor + three patch releases since the initial pi-devbox release on 2026-05-14).
- Bump: pi
@earendil-works/pi-coding-agent@0.75.3baked at/usr/bin/pi(viaPI_VERSION=latestresolving to 0.75.3 at build time). - No image-side changes from the v0.74.0 baseline beyond the pi npm version. The pi-toolkit + pi-extensions clones, mempalace bridge symlink, and
NPM_CONFIG_PREFIXnamed-volume setup all unchanged.
v0.74.0 — 2026-05-14
Initial release.
- pi
@earendil-works/pi-coding-agent@0.74.0baked at/usr/bin/pi - pi-toolkit and pi-extensions cloned at build time; deployed to
~/.pi/agent/by entrypoint on container start - mempalace bridge (
mempalace.ts) symlinked from/opt/mempalace-toolkit/ - Built on
joakimp/opencode-devbox:base-latest