Skip to content

Immuta Release Lifecycle

Release Lifecycle Schedule

Version General availability date End of support date End of extended support date
2024.2 LTS March 2024 April 2025 June 2025
2024.1 January 2024 April 2024 October 2024
2023.4 November 2023 March 2024 October 2024
2023.3 September 2023 December 2023 September 2024
2023.2 July 2023 December 2023 June 2024
2023.1 March 2023 September 2023 March 2024
2022.5 LTS December 2022 March 2024 July 2024

Release Lifecycle Terms

  • General availability date: The date the software version is available to all customers.
  • Support period: The period of time between the general availability date and the end of support date. During this period, Immuta will keep the version up-to-date with important bug fixes and security updates.
  • End of support date: The date when Immuta will stop backporting critical bug fixes to the release. For LTS releases, this is one year after the general availability date. For all other major releases, this is typically one month after the next release (four months after the general availability date).
  • Extended support period: The period of time between the end of support date and the extended support date. During this period, Immuta will no longer provide bug fix updates to the version, but will investigate and troubleshoot issues. Immuta recommends to upgrade before this period.
  • End of extended support date: The date when Immuta is no longer obligated to investigate issues raised against the release. The end of extended support date will occur three months after the next major release.

Long Term Support (LTS) Policy

Immuta releases one long-term support (LTS) version each year that is kept up-to-date with important bug fixes and security updates for one year. Our customers who prefer to remain on an Immuta version for an extended period of time can install the LTS versions and be confident that their implementation is stable and supported.

Major releases that are not designated “LTS” will be updated with important bug fixes until one month after the next major release.

FAQ

Why should I choose the LTS version?

Immuta recognizes that frequent upgrades are not feasible for many of our customers and wants to ensure that customers can remain on versions of the product that are well-supported. The LTS model ensures that customers who choose to stay on an Immuta version for a longer time will benefit from stability and security updates without being exposed to the risk of functionality changes.

I am on an older version today. Do I have to upgrade to an LTS version?

Immuta recommends that customers on older versions start planning an upgrade to the LTS or a more recent quarterly version.

Can I still use older versions?

The Customer Success team will continue to answer questions and help you troubleshoot older versions as much as possible. However, Immuta will not provide code updates to versions that have reached their end of support date.

What if I want the latest version of Immuta?

Great! Staying up-to-date with the latest Immuta release is the best way to get the latest features and improvements. The LTS model does not impact you. You will always be supported with critical bug fixes and security updates when you are using one of the two most recent major releases of Immuta. Immuta recommends to plan for quarterly upgrades to stay on a supported version when not on the LTS.

How are the non-LTS versions supported?

Major releases that are not designated LTS are supported with critical bug fixes through the next two major release dates, which is typically a four-month period, giving time for an upgrade each quarter.

What are considered critical bug fixes?

  • Cybersecurity vulnerabilities (CVEs) that are categorized as critical or high and have a possible impact within the Immuta solution.

  • Bugs that cause a severe and ongoing disruption to our customers' ability to conduct business in production, including critical performance impacts.