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.

Automatic rollback

The deploy is failure-proof:

1. After deploying, HTTP smoke tests verify critical routes (/, /login, /app, /c/demo-restaurant, etc.).
2. If they fail, the script aborts and returns an error message.
3. Snapshots of the last 10 builds in /opt/backups/restapro-dist/ allow fast manual rollback if needed.
4. For emergencies, we restore in under 5 minutes.

Incidents and communication

• Errors are captured in Sentry with context (userId, restaurantId, breadcrumb).
• If there's a service incident, communication via support@restapro.es and 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	Automatic in seconds	Reinstall previous version