This table shows each major version’s key lifecycle milestones. It helps you track when a version becomes available, when support ends, and when the version stops working, so you can plan migrations and avoid service interruptions.
| Major version | Phase | Release date | End of support (latest minor/patch only) | End of functionality |
|---|---|---|---|---|
| v3 | Upcoming | October 27, 2025 | To be determined | To be determined |
| v2 | Deprecated | August 19, 2024 | October 27, 2025 | January 31, 2026 |
| v1 | Decommissioned | April 17, 2024 | August 19, 2024 | November 30, 2024 |
Maintenance timelines define how long a version continues to receive updates and remain functional:
-
End of support
The version still functions, but is no longer maintained. It doesn’t receive any updates, bug fixes, or security patches.
This date is set to match the release date of the next major version.
-
End of functionality
The version is no longer guaranteed to be compatible with the runtime environment. The underlying API functionality might fail.
This date is usually 3 months after the end of support.
The full lifecycle of each major version:
- Upcoming: A future version that’s under development and isn’t yet released.
- Active: The current, fully supported, and recommended version.
- Deprecated: A version that is still functional but scheduled for replacement by an upcoming version.
- Decommissioned: A discontinued version that is no longer supported.