Single release truth

GrowthSystem Release Center

One place to identify the current software baseline, deployment variants, validation status and compatibility notes. A version label is not proof that every internal workflow has passed live owner/admin testing.

Current source baseline V8.13.0
SurfaceVersionMeaning
Web application8.13.0Current public and authenticated Next.js application release
Hosted backend8.13.0Node backend release used by the hosted GrowthSystem deployment
Windows desktop8.13.0Offline, Hybrid, Clean Hybrid, Client-Server and Store build source baseline
Android8.13.0Android builder source baseline; APK/AAB release should be verified against the published artifact before promotion
Documentation8.13.0This release center and V8.13.0 product documentation baseline

Deployment compatibility

  • Online: hosted UI + hosted backend/data.
  • Offline: embedded local backend; no central server required for core local operation.
  • Hybrid: embedded local backend plus central synchronization; conflicts and failed sync must remain visible.
  • Client-server: desktop UI with data stored on the remote server.

Release gates

  • Preserve customer data and provide migrations/rollback for schema changes.
  • Run source validation before server deployment and desktop packaging.
  • Verify permission, tenant isolation, record reconciliation, backup/restore and sync behavior.
  • Authenticated owner/admin live-tab coverage remains a release evidence task where runtime access was not available during the public audit.

Known evidence boundary

Public routes and source validators can establish many facts, but they do not replace authenticated end-to-end testing. Any capability that has not passed its real role, branch, language, deployment, error and reconciliation scenario should remain marked as requiring live verification rather than being advertised as proven.