> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/connected-insights/resources-and-references/release-policy.md).

# Release Policy

## Introduction

Illumina Connected Insights is upgraded regularly via major, minor, patch releases as well as configuration and content updates.

Release notes can be accessed via the [Release Notes](/connected-insights/overview/readme/rar-release-notes.md) page.

## Release Process

Illumina Connected Insights versions follow the MAJOR.MINOR.PATCH convention. Each new major, minor and patch release is associated with a new version. The version is not updated for configuration and content updates.

**Major Release** includes significant changes to functionality, often impacting product architecture and main functions. Major releases incorporate the latest minor releases and include additional enhancements. Major releases are rare.

**Minor Release** is tied to the preceding major release and covers routine functionality enhancements. This is the most common type of releases. Every minor release incorporates all previous patches since the prior patch release. Illumina supports each minor release on market for 2 years and sends a notification about the End of Life of a minor release at least 12 months prior to the End-of-Life date.

**Patch Release** is a new release that incorporates only bug fixes. Patches are released as needed.

**Configuration Update** includes minor compatibility expansions that are optional to use and do not impact existing functions. Examples are the addition of a new report template or compatibility with a new pipeline without impacting existing templates and pipelines. Configuration updates can be released at the same time as patches or content releases.

**Content Update** includes updates to select knowledge sources: Cancer Knowledgebase by Genomenon, OncoKB by MSKCC, and the Clinical Interpretation of Variants in Cancer (CIViC) database.

## Summary

<table><thead><tr><th width="132.88671875">Release Type</th><th width="135.8515625">Content</th><th width="105.66015625">Frequency</th><th width="114.48828125">On-Market Support</th><th>Customer Notifications</th></tr></thead><tbody><tr><td>Major Release</td><td>Architectural and major functionality changes</td><td>Rarely</td><td>2-years for the initial minor version<sup>1</sup></td><td><ul><li>Product Change Notification via email</li><li>In-app announcement<sup>2</sup></li><li>Customer Release Notes</li></ul></td></tr><tr><td>Minor Release</td><td>Routine feature enhancements</td><td>2 - 3 times per year</td><td>2-years <sup>1</sup></td><td><ul><li>Product Change Notification via email</li><li>In-app announcement<sup>2</sup></li><li>Customer Release Notes</li></ul></td></tr><tr><td>Patch Release</td><td>Bug fixes</td><td>As needed</td><td>Retired with associated minor release</td><td><ul><li>Product Change Notification via email</li><li>In-app announcement<sup>2</sup></li><li>Customer Release Notes</li></ul></td></tr><tr><td>Configuration Update<sup>2</sup></td><td>Minor compatibility expansions</td><td>As needed</td><td>Not applicable</td><td><ul><li>In-app announcement<sup>2</sup></li><li>Customer Release Notes Revision</li></ul></td></tr><tr><td>Content Update</td><td>Content updates of select sources</td><td>Monthly (cloud), quarterly (on-premises)<sup>3</sup></td><td>Not applicable</td><td>In-app announcement<sup>2</sup></td></tr></tbody></table>

<sup>1</sup> End of Life notification is sent at least 12 months prior to the End-of-Life date

<sup>2</sup> Cloud only

<sup>3</sup> The schedule for periodic content updates may have changes around major, minor and patch release date to minimize number of releases.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/connected-insights/resources-and-references/release-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.