Skip to content

0.3.74 — DO NOT DEPLOY (bricks an existing corpus; use 0.3.75)

Choose a tag to compare

@github-actions github-actions released this 11 Sep 01:22
· 1 commit to main since this release
fe1dde6

Caution

Do not deploy this release. It pins ciris-server v0.5.205 / persist v44.0.0, which cannot open a database that has history (CIRISPersist#840): a one-word edit inside a SQL comment in migration V070 changed its refinery checksum, so any node that applied V070 before 2026-09-09 fails validation inside Engine::with_* before anything binds. Upstream saw ~7 minutes of downtime and 16 crash-loops on the canonical.

A fresh data dir is unaffected — which is why every gate on this release was green. An existing one crash-loops.

Use v0.3.75 instead (ciris-server v0.5.206 / persist v44.1.1, which reverts V070 to its v42.1.0 bytes). Coverage gap tracked as #86.


ciris-status v0.3.74

ciris-status = ciris-server (the whole fabric node) + a StatusAdapter.

Container image (GHCR):

  • ghcr.io/cirisai/cirisstatus:v0.3.74 (and :latest) — the status node (multi-arch).

Deploy with docker-compose.yml; see DEPLOY.md for the cutover runbook.

What's Changed

  • 0.3.74: adopt ciris-server v0.5.205 — the read pool, and the SHA pin becomes a tag by @emooreatx in #85

Full Changelog: v0.3.73...v0.3.74