Changelogs
Below you will find a chronological timeline and summary of our major milestones, feature releases, and critical bug fixes. Click on any version number to view its comprehensive release notes, breaking changes, and migration guides.
Release Timeline
| Version | Milestone | Release | Key Focus & Summary |
|---|---|---|---|
| 26.05.28.01 | Minor | May 28, 2026 | Multi-region automated backup config & API optimization |
| 26.04.12.01 | Minor | April 12, 2026 | Advanced webhook filtering, retry logic, and UI enhancements |
| 26.02.19.01 | Minor | February 19, 2026 | New granular team permissions, roles system, and audit logs |
| 26.01.05.01 | Minor | January 05, 2026 | Dark mode native overhaul and workspace dashboard lazy-loading |
| 25.11.15.01 | Major | November 15, 2025 | Next-Gen core architecture, REST API v2 launch, breaking changes |
| 25.09.22.01 | Minor | September 22, 2025 | Legacy workspace optimization, CSV export tool, and memory leak patch |
| 25.06.01.01 | Major | June 01, 2025 | Official Production Release: Standard features & stability baseline |
💡 Note
- This log features active and forward-facing releases only. Legacy versions deployed before the launch of this documentation hub have been deprecated and are not archived here.
- S-Launch operates on a unified Software-as-a-Service (SaaS) model. All updates, enhancements, and patches are deployed globally across the entire platform simultaneously. Because of this architecture, users do not need to manually manage, request, or defer updates - ensuring everyone always has immediate access to the most secure and up-to-date version of the application.
Understanding Our Versioning
S-Launch uses a calendar-based versioning identifier for all builds. Rather than parsing traditional version digits, our version numbers tell you exactly when a release occurred.
📐 Version Format: YY.MM.DD.Index
YY(Year): The last two digits of the release year (e.g.,26for 2026).MM(Month): The two-digit month of the release (e.g.,05for May).DD(Day): The two-digit calendar day of the release (e.g.,28for the 28th).Index(Sequence): The build order for that specific day.01represents the first deployment of the day,02would be a subsequent hotfix on that same day, etc.
Milestone Classifications
While every release follows the calendar structure above, we categorize the scope of the release into two types:
- Major Major Releases: Represent significant platform upgrades, architectural changes, infrastructure shifts, or breaking API endpoints. These typically require checking migration notes.
- Minor Minor Releases: Backward-compatible feature updates, routine optimizations, UI adjustments, and day-to-day bug fixes.
💡 Note
Bug Tracking: If a recent version introduced a regression or an active glitch in your workflow, jump straight to our Bug Report Portal to log it with our engineering squad.
