Skip to content

build: move the provisioning tail out of build and into provision #251

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mobileoverlord wants to merge 3 commits into
base: main
Choose a base branch
from
Open

build: move the provisioning tail out of build and into provision #251

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1b2175d
feat(build): split the tail by consumer — OTA payload in build, var i…
mobileoverlord Sep 5, 2026
7b6173e
fix(build): stone writes into the tree the SDK reads, not $OUTPUT_DIR
mobileoverlord Sep 8, 2026
f7a8331
docs(changelog): one heading per section under Unreleased
mobileoverlord Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,35 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
declared it — and names the directory when it exists one level off, e.g.
`extensions/foo` for a top-level `foo`.

### Added
- **`avocado build` produces the deployable set *and* the OTA payload;
`avocado provision` builds the var image.** *(Breaking: `build` no longer
produces the var image.)* The split is by consumer: anything an OTA requires
is at the tail of `runtime build`, anything only provisioning consumes is at
the start of `provision`.

So the build tail keeps the `avocado-build-<target>` hook, `stone bundle`, the
`os_bundle` manifest patch and the re-sign after it. On UKI platforms that hook
*is* the kernel and initramfs, and `os-bundle.aos` is the OTA payload — not a
provisioning artifact. Verified that no provisioning script reads the bundle:
`avocado-provision-<target>` and the UFS flow both inject raw images.

`provision` builds the var image and primes Docker into it, which is all that
is genuinely provisioning-only. A pipeline that runs `avocado build` and then
flashes will find no var image; run `avocado provision`, which produces it.

`stone bundle` needs a var partition size because platform manifests declare
`var` as `expand: "true"` with no size, and it fails hard without the
`--partition-size` override. The var image does not exist at build time, so the
size is declared from the staged tree with headroom. That number reaches only
the bundle, an OTA never repartitions, and the partition expands at provision
time — but if a provision-from-bundle path is ever added it becomes real and
must come from the image.

The two halves live in `commands/runtime/var_image.rs` behind one context,
which is the set of things a portable provisioning bundle has to carry — what a
later `avocado provision --bundle <path>` would source from a bundle.

## [1.0.0-rc.3] - 2026-09-01

### Added
Expand Down
Loading
Loading