Sambee 0.9

Release Checklist

Candidate Loop

  1. Update VERSION to the next plain numeric X.Y.Z build sequence and run ./scripts/sync-version.
  2. Commit the synchronized metadata on main.
  3. Build only the affected component. Candidate workflows reserve or select the immutable build-vX.Y.Z source tag; they never accept a source or version override.
  4. Test the exact Docker digest through test, or test the Companion draft assets and promote them to the Companion test feed.
  5. Repeat the loop with a new Z value when a new candidate is required. Never rebuild or replace a published artifact under the same version.

Docker and Companion candidates may be built independently. Select an existing canonical build version when the second component must use a source commit that main has already advanced past.

Production Cutover Freeze

The release cutover is active as of 2026-07-20. Until the cutover is announced complete, permit only explicitly identified controlled test candidates through the current canonical-candidate workflows.

  • Do not use legacy Docker or Companion publishing entry points.
  • Do not promote stable or beta through a legacy workflow.
  • Do not mix legacy publication with the canonical candidate, immutable-artifact, and pointer-only promotion workflows.
  • End the freeze only after the cutover announcement and the first production publication and recovery paths have been monitored.

Documentation

  1. Review the homepage content and update it where necessary.
  2. Docs:
    • Verify Supported File Formats and update as necessary.
    • Finalize the target release’s What’s New page.
    • Mark the target version as current in website/data/docs-versions.toml.
    • Run the VS Code task Website: Refresh Docs Derived Artifacts.
    • Review the Docs Structure Report this creates in /workspace/website-meta/docs-reports/docs-structure-report.html.
  3. Git merge all changes.

Create The Public Release

See Overview .

  1. Run Release: Create Public Sambee Release with the approved canonical build version and the intended docker, companion, or both scope.
  2. Review the generated draft and its required sambee-release.json identity asset.
  3. Publish the draft only after the approved immutable artifacts exist. For both, both artifact verifiers must agree on the version, build tag, and source SHA.
  4. Publishing a Docker-authorized release triggers Release: Publish Docker Image , which moves only verified aliases. It never rebuilds the image.

Publish the Companion

See Overview

  1. Run Release: Build Companion Artifact from main or select an existing canonical build version.
  2. Test and publish its immutable external draft release.
  3. Run Release: Promote Companion Release to move test, beta, stable, and/or Sambee download metadata feeds without rebuilding binaries.