Release channels

Open-FDD publishes three GHCR channels. Only stable is intended for production edge sites without an explicit pin.

Channels

Channel GHCR tag Moves when Audience
Nightly :nightly (+ :sha-abc1234) Every green master push Developers, bench agents, CI
Beta :beta (+ immutable semver e.g. 3.3.0-beta.1) Maintainer promotion after bench milestone Pilot integrators, early OT sites
Stable :latest (+ immutable semver e.g. 3.3.0) Maintainer promotion after beta sign-off Production-ish edge deployments 
ghcr.io/bbartling/openfdd-edge-rust:nightly
ghcr.io/bbartling/openfdd-edge-rust:beta
ghcr.io/bbartling/openfdd-edge-rust:latest
ghcr.io/bbartling/openfdd-edge-rust:3.3.0-beta.1   # immutable pin

MCP uses the same channel tags on ghcr.io/bbartling/openfdd-mcp. The openfdd-mcp binary is also bundled in the edge image.

What to pull

Situation Set
Local dev / WSL / bench iteration OPENFDD_IMAGE_TAG=nightly
Reproduce a specific CI build OPENFDD_IMAGE_TAG=sha-abc1234
Friendly pilot after a beta cut OPENFDD_IMAGE_TAG=beta or pin 3.3.0-beta.1
Production edge (post stable sign-off) OPENFDD_IMAGE_TAG=latest or pin 3.3.0

Pin semver on OT benches — use 3.3.0-beta.1 or sha-*, not floating :nightly, when filing a bench report.

Promotion gates

→ Channel Requirement
Nightly Rust Edge CI green on master
Beta Bench closeout on a pinned tag (REV_326 rigorous report), GitHub pre-release
Stable Beta soak + no open P0s in milestone + explicit maintainer sign-off

Open-FDD has not published a stable release under this model yet. Current line is alpha / pre-beta until the first :beta promotion.

Maintainer workflows

Nightly (automatic)

Push to master → workflow Publish Rust edge to GHCR → :nightly + :sha-*.

No semver bump on master. The VERSION file tracks the next beta/stable candidate only.

Beta promotion

  1. Bump VERSION to e.g. 3.3.0-beta.2 on master.
  2. GitHub Actions → Rust Release (GHCR + GitHub Release).
  3. version: 3.3.0-beta.2, channel: beta.
  4. Creates GitHub Pre-release, moves :beta, publishes immutable semver tags.

Stable promotion

  1. Bump VERSION to e.g. 3.3.0 (no prerelease suffix).
  2. Rust Release → version: 3.3.0, channel: stable.
  3. Creates GitHub Release, moves :latest.

Site lifecycle 

# Dev / bench
export OPENFDD_IMAGE_TAG=nightly
./scripts/openfdd_rust_edge_bootstrap.sh --start

# Upgrade to a promoted beta
NEW_TAG=3.3.0-beta.1 ./scripts/openfdd_rust_site_update.sh

# Upgrade to stable
NEW_TAG=latest ./scripts/openfdd_rust_site_update.sh

See GHCR images for retention, multi-arch, and diagnostics.