Skip to content

v0.2.0

v0.2.0: rahi 0.2.0
@bartekus bartekus tagged this 21 Sep 00:20 
The recovery release. All nine chassis crates move together at 0.2.0.

Tested main revision: 8d686bdf7b10d4ee24357a31b4de25ae87cc5b2a, whose ci
and image runs both passed and whose tree the live suite ran against as
pull request #71. This tag names the commit that records that revision and
differs from it by one CHANGELOG paragraph.

Carried, in the order they landed:

  037  identity recovery and the live proof against the pinned rauthy
  036  manifest and schema evolution, with the four fail-open repairs and
       the one-snapshot manifest read
  042  lifetime identity for decisions, with the coverage, recovery,
       single-snapshot and resident-verification corrections
  026  the open-stream gauge pairs with the attachment, not the global
  033  the boot budget measures the boot, not the build before it
  039  the reconciled release documentation, the published hello-cell
       image, and digest verification of every published image

Compatibility: the minor bump follows 039 B-1. New key sets carry an
origin-bound backup passkey and old sets are not automatically upgraded;
backups refuse without it. Chains sealed before 042 need a stop-the-world
reindex, and each decision now costs one permanent resident row.

Not carried, and not fixed by this release:

  - hiqlite 0.14.0's stale lease release after TTL takeover. rahi patches
    the dependency in its own workspace root; a consumer does not inherit
    the patch, so every published crate still resolves 0.14.0 without it.
  - Full-node restart followed by a second lease acquisition. A separate
    property that no approved spec carries; a future hiqlite publication
    closing the lease-release defect does not close this one.
  - Kubernetes N=3. The operational proof is N=1.
  - Spec 038, native clients and bearer revocation: approved and pending.
    Only a later release carries it.
Assets 2
Loading