Current launch baseline
The public baseline reflects implemented restaurant workflows, production gates, security checks, public API boundaries and trust materials.
Release Notes.
Public release-note policy and current launch baseline for Limvero.
Release communication
Release notes are intentionally factual and tied to implemented product behavior.
Release notes format
Future release notes should include date, affected modules, operator impact, API/webhook changes, migration needs and rollback notes.
No fake history
Limvero does not publish invented version history, invented uptime, invented customer metrics or unsupported provider/certification claims.
Breaking changes
Breaking changes to public API, webhooks, roles, offline behavior or data exports require clear notice and customer migration guidance.
Security updates
Security-relevant changes should reference affected surfaces, required customer action and whether credentials or API keys need rotation.
Operational updates
Deploy, rollback, backup, restore, worker and status changes should stay aligned with production operations documentation.
The first public version history should be published after the production launch process and customer communication workflow are finalized.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.