> 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/clarity-lims/instruments-and-integrations/other-release-notes/nextseq550-v2.2.0-release-notes.md).

# NextSeq 500/550 v2.2.0

These Release Notes describe the key changes to software components for the Clarity LIMS NextSeq 500/550 Integration Package since version 2.1.

This is an optional software update for customers interested in the features available with this release.

If upgrading from a version prior to version 2.1, review the release notes for v2.1 for a list of features and bug fixes introduced in that version.

## Compatibility

This version of the integration package is compatible with the following software:

* Clarity LIMS v5.1 and later
* NGS Extensions Package v5.21 and later
* Illumina Preset Protocols (IPP) v2.3.0 and later
* NextSeq Control Software (NCS) v4.0 (Standalone mode only)

## New Features

Features provided with this release of the integration package are as follows:

* Support for Clarity LIMS v6.0. Clarity LIMS v4.x and v5.0 are not supported.
* Fixes to address the following Apache log4j vulnerabilities:
  * CVE-2021-44228
  * CVE-2021-45046
  * CVE-2021-45105
  * CVE-2021-44832
* Tech refresh to upgrade third party libraries.

## Defect Repairs

* Fixed run report so that it displays footer correctly.
* Fixed NextSeq sequencing service to record interopUtil parsing in the log file.

## Known Issues

None


---

# 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/clarity-lims/instruments-and-integrations/other-release-notes/nextseq550-v2.2.0-release-notes.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.