Migrations on aiboxhttps://projectious-work.github.io/aibox/docs/migrations/Recent content in Migrations on aiboxHugoen<link>https://projectious-work.github.io/aibox/docs/migrations/lockfile-v0-25-6/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://projectious-work.github.io/aibox/docs/migrations/lockfile-v0-25-6/</guid><description><h1 id="lockfile-schema-bump-v0256--whats-automatic-what-to-verify">Lockfile schema bump v0.25.6 — what&rsquo;s automatic, what to verify</h1> <p>aibox v0.25.6 extends <code>aibox.lock</code> with two new optional sections. The bump is fully automatic — <code>aibox apply</code> backfills the new fields on first run. No manual editing is required, and existing lockfiles remain valid (the new fields use <code>#[serde(default)]</code>, so they are absent from old locks without causing parse errors).</p> <h2 id="what-changed">What changed</h2> <p><code>cli/src/lock.rs</code> adds:</p> <ul> <li> <p><strong><code>AddonsLockSection::previous_selection</code></strong> (<code>BTreeMap&lt;String, BTreeSet&lt;String&gt;&gt;</code>) — records which tool names were enabled under each addon family at the time of the last apply. Written under <code>[addons.previous_selection]</code> in <code>aibox.lock</code>. Used on the next apply to compute a removal diff when a tool is disabled, so stale addon binaries baked into an earlier image layer can be purged cleanly.</p></description></item><item><title/><link>https://projectious-work.github.io/aibox/docs/migrations/zellij-eol/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://projectious-work.github.io/aibox/docs/migrations/zellij-eol/</guid><description><h1 id="zellij-end-of-life-migration-v0255--v0256">Zellij end-of-life migration (v0.25.5 → v0.25.6)</h1> <h2 id="tldr">TL;DR</h2> <p>aibox v0.25.6 removes Zellij entirely. tmux is now the only supported terminal multiplexer. Any <code>[customization.zellij_status]</code> section in your <code>aibox.toml</code> causes schema validation to hard-reject <code>aibox apply</code> — you must remove it before upgrading. Stale Zellij directories and binaries are purged automatically on the first <code>aibox apply</code> that runs against a v0.25.6+ host CLI. No data from active work sessions is touched; only Zellij runtime artifacts are removed.</p></description></item></channel></rss>