Announcing CradleXC 0.19.2

22 September 2026

CradleXC 0.19.2 consolidates the standalone compiler and its external backend plugin workflow. The release removes the obsolete web crate and archived repository artifacts, while keeping the production package focused on parsing, validation, compilation, inspection and target-file generation.

This release matters for operators and backend authors because backend support is no longer implied by the core compiler package. Install the backend plugin needed for a target separately, then use CradleXC to render files that remain under your control. The release also makes the repository and release process less confusing by removing dead material from the upstream project.

Highlights

• Ship CradleXC as a standalone core compiler with no in-tree deployment backends.
• Use independently distributed cxc-backend-<name> plugins for target-specific rendering.
• Remove the obsolete cradle-web surface and stale archived artifacts from the upstream repository.
• Keep cxc build and cxc rebuild focused on generating files; they do not execute or deploy infrastructure.

Changed

Backend plugins are separate from the core package

CradleXC 0.19.2 no longer builds deployment backends into the CLI. Backend implementations are standalone executables discovered as cxc-backend-<name> plugins. Install and inspect a plugin before generating target-specific files:

sudo cxc plugin install <plugin_name>
cxc plugin list
cxc build -i scenarios/HelloWorld.cradle --target <plugin_name> -o ./output

The available plugin names, supported targets and host prerequisites remain backend-specific. cxc doctor reports the dependency checks available in the current environment; a successful check does not guarantee that every scenario or target is supported.

Core workflows remain generation-only

The production CLI continues to validate and compile CRADLE source, expose Deployment IR for inspection, and ask a selected backend to render target-specific files. Generated files must be reviewed and used with the corresponding target tooling by the operator. CradleXC does not automatically execute those files or create infrastructure.

Removed

Obsolete web and repository artifacts

The upstream project removes the old cradle-web crate and associated generated database, graph exports, archaeology documents and stale planning material. These deletions do not change the CRADLE source format or the compiler's supported validation, compilation and rendering workflow, but users should rely on the CLI and external backend repositories rather than an upstream web interface.

Installation and upgrade

Install or upgrade through the CRADLE APT repository as usual:

sudo apt update
sudo apt install cxc

Confirm the installed release and inspect the local environment:

cxc --version
cxc doctor

If you need target-specific output, install a compatible backend plugin separately before running cxc build.

Documentation

The current documentation now describes plugin discovery with cxc plugin list and keeps target-file generation separate from execution. See Use a Backend for the installation and compatibility workflow.