Releases

This section tracks platform release notes and rollout guidance.

Available Versions

• v2026.1.89

Recent Feature Internals

The latest Platform and frontend releases moved several features from release-note bullets into internal architecture pages. These pages are tenant-gated and intended for platform engineers and operators:

• Portal Runtime Architecture — shared portal API client, runtime proxy, auth bootstrap, notification history, and unauthorized routes.
• SMS Message History, Campaign Dispatch, Traffic Shaping, and SMPP Ingress — projection-backed SMS history, campaign performance path, traffic shaping, and inbound SMPP.
• USSD Switch Routing and Remote Auth Internals — switch actions, visual routing, simulator raw output, handoff redirects, and secrets-backed remote-call auth.
• Billing Replay, Recovery, and Settlement Internals — usage audit, replay jobs, expired-subscription recovery, billing schedule repair, settlement, and taxes/levies.

Notes

• Each version page includes scope, highlights, and production configuration updates.
• Use the latest release page for current production upgrade instructions.

Operator Flow

1. Merge approved pull requests to master.
2. Let the Platform workflow build changed images and deploy them to staging with CI/pre-release image tags.
3. Review the automatically maintained draft GitHub Release notes.
4. When staging is ready for production, publish the draft GitHub Release with the next calendar SemVer tag, for example v2026.6.17.
5. The published GitHub Release is the production gate. Production deployments should only run from that release event and should use the stable release version tag.

Normal CI and staging builds must not create v* Git tags. Stable vYYYY.MM.PATCH tags belong to reviewed GitHub Releases only.