Avocado 1.0 is a statement about stability, not a feature dump. It marks the point where the declarative format that describes how you build, provision, and update a device (the avocado.yaml contract that everything else is built on) is stable and safe to depend on in production. Everything below rolls up under that milestone, but each part of the ecosystem keeps its own version and its own pace: the CLI, the desktop app, the MCP server, and the hardware and package feeds all move independently.

What 1.0 means

• The declarative format is stable. The runtime, extension, and source schema in avocado.yaml is stable across the 1.x line. Configs you write today keep working as it evolves.
• It is a release candidate. 1.0.0-rc.1 exists so you can build against the frozen format and report anything that should block the final tag. Treat it as the shape of 1.0, not the last word.
• It is not a list of shiny new features. Most of what makes 1.0 possible landed across the 0.x line. 1.0 draws the line under that work and says the foundation is ready to sell, ship, and support.

Avocado CLI: 1.0.0-rc.1

The CLI is the heart of the system, and its 1.0 is about the contract it owns: the declarative build format. The capabilities that format now covers matured over the 0.x series:

• Declarative runtimes and extensions. Describe a device's software set once, then build, image, and install extensions against a runtime sysroot.
• avocado vm on macOS. The CLI owns the QEMU lifecycle end to end, with VM hibernation (wake-on-connect, PSCI idle states) and streaming downloads.
• Reproducible builds. Channel snapshot pinning lets a build resolve the same package set later, so a release is reproducible rather than "whatever was on the feed that day."
• Private package feeds. Custom CA / TLS support for pulling from your own feeds.
• A top-level permissions: block and per-step build caching keyed on input hashes.
• --output json across the lifecycle, which is what lets Avocado Desktop drive the CLI programmatically.

Install and upgrade via the Homebrew tap. Linux and Windows builds are in progress.

Avocado Desktop: 1.0

Avocado Desktop is the biggest new surface in this release: a native macOS app (Apple Silicon) that puts the whole build-and-deploy loop behind a UI and an AI agent.

• Built-in AI agent. Describe a project in plain English and the agent scaffolds the extension, cross-compiles it, flashes media, boots the device, and surfaces the result, with no hand-written config to start.
• Uses your CLI, or brings its own. Desktop prefers a host-installed Avocado CLI when one is present and falls back to a bundled sidecar CLI when it is not.
• Install via Homebrew (brew install --cask avocado-linux/tap/avocado-desktop); the DMG is published to the Avocado repo CDN.

Avocado MCP

The Model Context Protocol server that powers the Desktop agent (and any MCP-aware client) now has Connect awareness, so an agent can reason about Avocado Connect resources alongside local build state. It installs today as a one-shot command from GitHub; a package-registry distribution is planned.

Hardware and package feeds

Avocado's target coverage spans 11 hardware vendors, from silicon vendors like NXP, NVIDIA, and Qualcomm to board and module makers like Advantech, OnLogic, and SolidRun, with more under evaluation. See the hardware support matrix for the current list.

New boards and packages land on channel feeds continuously rather than on a fixed release train. A future changelog structure will surface what became available on which feed and when; for now, 1.0 marks the platform those feeds build on as stable.