Release and Versioning

This section covers version changes and the main-only release process that binds every publishable X.Y.Z candidate to one immutable source commit.

For a complete Sambee product release, start here:

• Release Checklist
• Product Versioning

For dependency changes, use:

• Dependency Update Workflow

For Sambee Docker image releases, read these pages in order:

• Docker Release Overview
• Publish Test Docker Candidate
• Promote Docker Candidate
• Docker Backfill And Cleanup

Build candidates from main, test the immutable artifact, then promote only verified pointers. Never rebuild or replace a published candidate under the same version.

For Companion release distribution, read these pages in order:

• Companion Release Overview
• Build Companion Release
• Promote Companion Release
• Companion Channels, Feeds, And Downloads

Docker and Companion may be built independently, but a coordinated both release requires the same version, canonical build tag, and source SHA before either stable pointer moves.