Long term support policy
This page explains the support plans for major versions of Clerk's SDKs. When a new major version of an official Clerk SDK is released, the previous version is placed into long term support (LTS) mode for a period of one year. During this period, new features and bugfixes will not be actively backported, however, any critical patches will be actively backported.
After the LTS period ends, there will be no further changes to the code for that version in any form, and we will strongly recommend upgrading to a new version for product and security improvements. While we strongly recommend upgrading to keep your application secure, all previous versions of SDKs will continue to function indefinitely even if not upgraded.
Schedule
| Version | Status | As Of | Until |
|---|---|---|---|
| Core 2 | Active | April 19, 2024 | TBD |
| Core 1 | Long term support | April 19, 2024 | Q1 2025 |
| Legacy (v3) | Unsupported | - | - |
Library compatibility
Clerk's SDKs run in the browser, in Node.js (+ other compatible runtimes), or in both. Below you can find out which Node.js and browser versions Clerk's SDKs support.
| Version | Node.js | Browsers |
|---|---|---|
| Core 2 | >=18.17.0 | Evergreen, iOS 16 |
| Core 1 | >=14.0.0 | Evergreen, iOS 16 |
Terminology
-
Critical Patch - A critical patch addresses an issue that prevents an SDK from delivering intended user value under typical conditions. Other items, such as minor bug fixes and new features are not considered "critical patches".
-
Active - Receives priority attention from the core maintainers of Clerk. New features to Clerk are only available in the Active version.
-
Long term support - Receives critical patches, but does not receive new features.
-
Unsupported - This version of Clerk no longer receives official support of any kind.
-
Evergreen browser - Includes these browsers: Google Chrome, Mozilla Firefox, Microsoft Edge (Chromium), Safari, Opera. No support for Internet Explorer (IE).
Feedback
Last updated on