Release identification and release notes
Identify a running system by its authenticated deployment ID, generation, board,
kernel component ID and root component ID. mica-deploy status and the update API
expose this association. Filenames and timestamps alone do not identify content.
1. Artifact identity
Section titled “1. Artifact identity”The signed deployment envelope binds the exact kernel/root association and artifact sizes/digests. Root and support hashes have detached kernel-verifiable signatures. The kernel package carries its matching modules and boot policy. Firmware has an independent signed identity and maintenance receipt.
The image also carries /usr/share/mica/manifest.tsv and immutable build identity.
A dirty development source stamp remains visible; it is not evidence that a
clean source commit reproduces those bytes.
status: shipped — evidence:
mica-build:build/src/components.ts,mica-deploy:src/deployments.rs,mica-build:rootfs/compose/90-pack.Dockerfile
2. Release-note facts
Section titled “2. Release-note facts”Record the exact target, profile, deployment IDs, component changes, source identity and package delta from the artifacts. Name trust-anchor, boot-policy, access-default and persistence-policy changes explicitly. Keep validation results and limitations attached to the exact image tested.
A root-only release must identify the unchanged kernel/support component; a
kernel-only release must identify the unchanged root. Retained fallback uses the
same DATA filesystem. It does not revert application data. The current contract
accepts dataPolicy: unchanged and has no destructive migration path.
status: shipped — evidence:
docs/user/doc-contract.md,mica-build:build/src/components.ts,docs/design/updates.md
3. Publication status
Section titled “3. Publication status”The update server publishes authenticated component releases to a chosen channel and supports withdrawal. Its catalog expiry applies to acquisition, while an installed authenticated deployment can boot offline. A published channel is not a substitute for board qualification or a product support commitment.
status: shipped — evidence:
mica-build:update-server/src,mica-deploy:src/acquisition.rs
No public release history, support window or end-of-life commitment is asserted by this page. See obtaining an image for the current source-build route and release artifacts for delivery records.
status: unsupported