Submit a request
Submit a request

Release Cadence and Version Lifecycle

As an agile company, Learnosity releases new versions of our products extremely regularly - in fact, in most cases, we're pushing out new features and functionality on a three-weekly basis!

While we maintain full backwards compatibility with every new release - for production systems we strongly recommend using a supported, stable, Long Term Support (LTS) version.


Every three weeks, for our APIs, we release new code to latest. This can be new features, in-development features, and bug fixes since the last 'latest' release, etc. These releases are bleeding edge, and should be used for:

  • New projects in-development, targeting our next Long Term Support releases (see below).
  • Proof of Concept code, taking advantage of forthcoming major releases.


Long Term Support (LTS)

Every four months, we release a major milestone release, to better match our customers’ development cadence. Every FebruaryJune and October we release production ready versions of our APIs that will be supported for two years. This applies across all of our core APIs.

Long Term Support releases are strong, complete, stable and should be used for:

  • Platforms in-production.
  • Projects in-development, going live before our next Long Term Support release.


View all our Long Term Support releases

Here's what you can expect from each of the release types above:

  latest Long Term Support (LTS) *
Provides code stability No Yes
Receives security, performance and bug patches automatically Yes Yes
Receives new features or feature enhancements after initial release Yes No
Environments recommended for Development or Proof of Concept Production or QA
Receives general security, performance and bug fixes for N/A 16 months
Receives critical security, performance and bug fixes for N/A 24 months
Start of End of Life (EOL) N/A 24 months
Sunset date and removal N/A 30 months
* Denotes the Learnosity advised option.

LTS versions have a sixteen month lifespan for general security updates, performance updates and bug fixes. After that, they will receive critical security updates, performance updates and bug fixes until their end of life date, at 24 months from the first release.

After that, they transition into an End of Life (EOL) phase.


Figure 1: chart of Learnosity LTS versions lifecycle


2021 LTS Versions Lifecycle

LTS version

Promotional release date

Critical patches only



13th October 2021

March 2023

November 2023


30th June 2021

October 2022

July 2023


24th February 2021

June 2022

February 2023


2020 LTS Versions Lifecycle

LTS version

Promotional release date

Critical patches only



4th November 2020

4th March 2022

16th November 2022


1st July 2020

27th October 2021

13th July 2022


26th February 2020

23rd June 2021

16th February 2022


2019 LTS Versions Lifecycle

LTS version

Promotional release date

Critical patches only



6th November 2019

10th March 2021

17th November 2021


3rd July 2019

7th October 2020

14th July 2021


27th February 2019

24th June 2020

17th February 2021


2018 LTS Versions Lifecycle

LTS version

Actual release date

Critical patches only



3rd Oct 2018

29th Jan 2020

7th Oct 2020


1st Aug 2018


1st Nov 2018


6th Jun 2018

9th Oct 2019

3rd Jun 2020

What is the LTS version naming convention?

LTS release naming follows this convention - vYYYY.X.LTS

  • YYYY is the year the version was released,
  • X is an incremental number starting at 1 each year, and
  • LTS is a suffix to identify these versions.

How do I select a Long Term Support (LTS) version?

Simply choose the LTS version you want to use and pass that in the <script> tag.

E.g. <script src=""></script>

For Data API, pass it in the URL of the endpoint you wish to send a request to.



Can I still access the latest API (non-LTS) releases and product features?

Latest releases will still be available every three weeks, but these will contain in-development, less stable features (compared to the stable LTS releases). 

To access the latest release for any API, simply pass latest as the version in the script tag.

Eg: <script src=""></script>

For the Data API only, pass v1 in the URL of the endpoint you wish to send a request to.




Was this article helpful?
2 out of 2 found this helpful

Did you arrive here by accident? If so, learn more about Learnosity by clicking here.