Migrations · aiboxhttps://projectious-work.github.io/aibox/v0.x/v0.34.2/docs/migrations/Reproducible AI workspaces from one aibox.toml.enMon, 01 Jan 0001 00:00:00 +0000<link>https://projectious-work.github.io/aibox/v0.x/v0.34.2/docs/migrations/lockfile-v0-25-6/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://projectious-work.github.io/aibox/v0.x/v0.34.2/docs/migrations/lockfile-v0-25-6/</guid><description>Lockfile schema bump v0.25.6 — what’s automatic, what to verify#aibox v0.25.6 extends aibox.lock with two new optional sections. The bump is fully automatic — aibox apply backfills the new fields on first run. No manual editing is required, and existing lockfiles remain valid (the new fields use #[serde(default)], so they are absent from old locks without causing parse errors). What …</description></item><item><title/><link>https://projectious-work.github.io/aibox/v0.x/v0.34.2/docs/migrations/zellij-eol/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://projectious-work.github.io/aibox/v0.x/v0.34.2/docs/migrations/zellij-eol/</guid><description>Zellij end-of-life migration (v0.25.5 → v0.25.6)#TL;DR#aibox v0.25.6 removes Zellij entirely. tmux is now the only supported terminal multiplexer. Any [customization.zellij_status] section in your aibox.toml causes schema validation to hard-reject aibox apply — you must remove it before upgrading. Stale Zellij directories and binaries are purged automatically on the first aibox apply that runs …</description></item></channel></rss>