Versioning and releases
RestaPro is a SaaS on continuous deployment: every commit on main can reach production after review. There are no discrete versions you have to download and install - you're always on the latest.
Build ID
Every deploy generates a unique identifier (Git hash). Visible in:
- Meta tag in the HTML:
<meta name="restapro:build-id" content="abc1234def56"> - Backoffice footer (in some places).
- Browser inspector (F12 → Elements tab).
If support asks "which version do you have?", just look at the meta tag.
Why there's no semantic versioning
Traditional software: v1.0 → v1.1 → v2.0, you download, install, wait for the next release.
Continuous SaaS: small, frequent changes that arrive automatically. Semantic versioning adds no value when you don't decide when to update.
How you find out about changes
Public changelog
Each major release is posted at /changelog with:
- What changed
- Why
- Whether it affects your flow
Email to workspaces
Highlighted changes that affect your day-to-day are announced by email to the account. No spam - only what's relevant for managing your restaurant.
Breaking changes
Policy:
- Notification 30 days in advance if something changes and could affect your integration or public flows.
- Clear message: what changes, why, what to do (if anything).
- Transition period: in critical changes, we keep the old version running in parallel while you migrate.
Most changes are additive and transparent - they start working without you doing anything.
Rollback on Vercel
The frontend is published on Vercel. Before promoting a deployment, verify its SHA, required CI checks, version.json, assets and browser behavior.
HTTP smoke verifies delivery and version; HTML 200 does not establish a loaded menu or successful login. The candidate workflow adds browser tests with synthetic data and no external network access. Authentication/MFA, Admin and operational tests with a real backend need isolated staging.
If a deployment fails, the owner can select a compatible previous deployment on Vercel and check its domains. This does not revert migrations or data. Neither automatic rollback nor recovery within five minutes has been demonstrated. Snapshots under /opt/backups on the former server are not part of the current flow.
Incidents and communication
- Errors are captured in Sentry with context (userId, restaurantId, breadcrumb).
- If there's a service incident, communication via
soporte@restapro.esand proactive email. - Service status: a public status page is coming.
Summary
| RestaPro | Traditional software | |
|---|---|---|
| Versions | Continuous, build ID = git SHA | v1.0, v1.1, v2.0 |
| Update | Automatic, no intervention | Download, install |
| Cadence | Daily / weekly | Quarterly / annual |
| Breaking changes | 30-day notice, rare | New major versions |
| Rollback | Previous Vercel deployment after checking compatibility | Reinstall previous version |