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!

That doesn't mean, however, that every Learnosity version is ready for full production use - features may be still in development, still a technical MVP (Minimum Viable Product), or out for early release to get client feedback. As a result, we have three types of releases:


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

  • New in-development projects, 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:

  • All In-Production platforms
  • In-development projects, 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.

When do LTS versions go end of life (EOL)?


As mentioned in the table on this page, LTS versions have a 16 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 first release.

What is the LTS version naming convention?

LTS release naming will follow the following convention - vYYYY.X.LTS

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

How do I move to Long Term Support (LTS) versions?

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

Eg: <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, while we’ll be spending more time communicating the significant changes every four months rather than a three-weekly deluge.

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.


When can I move to Long Term Support (LTS) versions?

For any core API, when upgrading, you will need to use the new LTS naming convention.

How do the support arrangements differ between legacy versions and Long Term Support?

Legacy (pre-June 2018) API versions are currently supported for critical or security issues. We always recommended upgrading as often as practical, but contact Learnosity support if you have any questions.

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

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