Release notes and upgrade
Which CID222 versions exist, how they are numbered, what changed in each, and what an upgrade requires of you.
- Version: 0.4
- Role: admin_user, viewer
CID222 releases are numbered MAJOR.MINOR.PATCH. Documentation is versioned with the product: the
pages you are reading describe the version stated in each page's metadata, and an appliance carries
the documentation of the build it is running.
Versions
| Version | What it is |
|---|---|
| 0.4.0 | The current release. The LLM Risk Analyst, the MITRE ATLAS and OWASP reference corpora, hallucination detection, the compliance and governance modules, the auditor role, and host-side repair of an installed appliance. |
| 0.3.x | The previous line, up to 0.3.49. Superseded; upgrade in one step. |
How versions are numbered
- Patch releases (
0.4.0→0.4.1) are the normal cadence. They are published automatically when a change alters the shipped images or the compose wiring, and they carry fixes and small additions. - Minor releases (
0.3.x→0.4.0) are cut deliberately. They carry the changes that need a decision from you before you upgrade — a changed default, a removed service, a control that starts enforcing. - A change that touches only documentation or the Claude Code plugin publishes no release at all; the plugin has its own channel and its own version.
Note
There is no published support or end-of-life policy for a CID222 version. Ask your CID222 contact how long the release you are running will be maintained rather than inferring it from the numbering.
What an upgrade requires of you
Each release note carries an Upgrade impact table with one row per affected area. A row exists only when the upgrade requires something of you — a backup, a configuration value to re-enter, a user population to warn, a monitor to repoint. An area not listed needs nothing.
An appliance and a Docker Compose installation are affected differently by the same release. An appliance's schema, service set and host configuration are all carried by the signed release; a Compose installation carries its own environment file, so a changed default arrives unannounced there and nowhere else. Both cases are covered in Upgrade to 0.4.0.
Warning
Upgrades apply database migrations on first boot. Take a backup before you start, and confirm afterwards that no migrations are left pending — a pending migration means every reader of the new schema will fail, not that the upgrade partly worked.
Deprecations
Deprecations are listed in the release note that introduces them, with the replacement and, where one has been set, the release the behaviour is removed in. Nothing has been removed without a release note announcing it first.
Related
- Upgrade to 0.4.0 — the procedure for both installation types.
- Update the appliance — the online and offline update paths in detail.
- Backup and restore — what to take before an upgrade.
Last updated on