DocsUpdated: February 20265 min read

Versioning and Changelog Policy

How Quilon versions desktop releases and how backend compatibility is managed.

Versioning Model

  • Desktop app uses semantic versioning-like patch cadence for hotfixes
  • Backend exposes current release metadata through /api/version
  • Download endpoints resolve latest release binaries for supported platforms

Compatibility Expectations

  • Patch releases should remain protocol-compatible with current backend
  • Breaking protocol changes require coordinated backend + client rollout
  • Security fixes should be released as patch versions as soon as validated

Release Checklist

  • Run desktop, backend, mobile, and iOS tests
  • Verify TypeScript builds across all targets
  • Create GitHub release with artifacts and notes
  • Validate /api/version and installer download links in production