Hyperscience releases new versions of the Hyperscience Platform on a regular basis. Each version is supported by Hyperscience for a specific length of time, as described in this article.
Official releases
Hyperscience versions are labeled as follows:
Versions are numbered in the form x.y.z (major.minor.patch) where:
x.y are the feature version numbers, where x is a major version number and y is a minor version number.
z is the patch release version number.
Major versions
Major versions are available both on SaaS and on-prem.
Major releases (x.0.0, (x+1).0.0, etc.) occur twice a year. These releases contain new features and improvements to existing features. Upon upgrading to these versions, retraining your models and upgrading your flows may be required, depending on your flows version.
As a reminder, your current flows are compatible with your target version only if the target version is one or two versions after the current version (e.g., v35 flows work in v36 and v37 but will not work in v38).
Minor versions
At the moment, minor versions are only available on SaaS.
Minor releases occur roughly every 2 months (x.y.0, x.(y+1).0, etc.). Minor versions contain new features or feature improvements and maintain backward compatibility. Therefore, upon upgrading to these versions, no manual action is required from you. You do not need to retrain your models or upgrade your flows.
We will not release a minor version in the months where we release a new major version.
Patch versions
Patch releases (x.y.z, x.y.(z+1), etc.) are issued as needed to fix any bugs or security issues that are found.
These releases are 100% compatible with the associated major and minor versions, unless making them compatible would create potential for security vulnerabilities or data loss. In those rare situations, any incompatibilities are described in the release notes, and specific upgrade instructions are provided. Because there are no flow- or model-compatibility concerns to address in most cases, we recommend upgrading to the latest patch version.
Supported versions and support window
Hyperscience will support each major version for a total of 18 months after it becomes generally available at two different levels of support. At any given time, Hyperscience will provide patches for the current major version (x.y.z) and the two previous major versions ((x-1).y.z and (x-2).y.z).
Full Support (12 months after release): We will proactively address issues and apply patches to this version of Hyperscience. We’ll fix the following types of issues during Full Support:
Security issues
Major functionality bugs in features
Regressions from previous Hyperscience versions introduced
Extended Support (6 months after Full Support): Only security issues will be patched during Extended Support. In general, when the version you’re using hits Extended Support, you should start planning your upgrade.
As an example of these timelines, see the graph below (dates are illustrative only):
In Oct 2024, Hyperscience will:
Provide full support for 40.0.z and 39.0.z
Provide extended support for 38.0.z
For a list of versions currently supported by Hyperscience, see Supported Versions.