Release and Versioning

Release and Versioning

Stub. Tracked as a "still to write" page on the Home hub.

This page will codify the release engineering contract — release cadence, schema-version policy, embedded-manifest refresh, and the compatibility windows that govern dual-emit / dual-accept deprecations:

• Versioning — what bumps a patch / minor / major. The "install budi and budi-daemon from the same build" invariant, version-mismatch detection on first CLI invocation
• Schema version — schema_version semantics (the v8.5.7-rc.2 cloud-sync bump to 5 is the most recent example), migration paths in crates/budi-core/src/migration.rs
• Embedded pricing manifest refresh — the per-release scripts/pricing/sync_baseline.sh step, validation guardrails before commit
• Dual-emit / dual-accept windows — when a rename (e.g. org_id → workspace_id) crosses repos, the daemon emits both keys until ≥30 days of mixed-version operation. See the 2026-05-15 banner on Cloud Data Contract and Privacy Boundary
• Release checklist — what gets verified before a tag (CI green, e2e green, embedded manifest fresh, CHANGELOG section, release notes)
• Distribution — Homebrew tap (siropkin/homebrew-budi), the install script, the Cargo-bin fallback
• Upgrade compatibility tests — scripts/e2e/ guards that pin upgrade paths (e.g. legacy proxy residue, schema migrations)

Current source of truth

• CHANGELOG.md — full release history
• SOUL.md — Build & Test, Daemon autostart, Database sections
• scripts/ — release and pricing scripts
• scripts/e2e/ — upgrade-path regression guards