Overview

Release Policy

The intended shared release contract across the Cascade platform repos.

On this page

Release Policy

Cascade services are intended to converge on one release contract.

Shared expectations

  • Tagged releases produce GitHub Release assets.
  • Checksums are published alongside binary assets.
  • Production container images are published to GHCR where the repo ships containers.
  • CI enforces formatting, clippy, tests, and dependency audit before release.

Current reality

  • Most core Rust services already have release automation.
  • Breakwater and Weir were brought onto that pattern later and are still converging.
  • Cascadia still needs final GHCR production-image normalization.

Operator expectation

Until the platform reaches GA, treat releases as coordinated early-access platform releases rather than assuming every repo is independently production-stable.