> 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/novaseq6k-api-v3.5.1-release-notes.md). # NovaSeq 6000 API-based v3.5.1 These release notes describe the key changes to software components for the Clarity LIMS NovaSeq 6000 Integration Package. ## Compatibility This version of the integration package is compatible with the following software: * Clarity LIMS v5.1 and later * NGS Extensions Package v5.22 and later * Illumina Preset Protocols (IPP) v2.5.0 and later * NovaSeq Control Software (NVCS) v1.8.0 * Illumina bcl2fastq v2.20 ## New Features Features provided with this release of the integration package are as follows. * Updates to the Validate Flowcell Barcode automation (in the Load to Flowcell step of the NovaSeq Xp protocol) to support future flow cell barcode formats. * Vulnerability fixes for Denial of Service (CVE-2022-22970) and Integer Overflow (CVE-2022-22976). ## Defects Fixed Fixed the following Calculate Volumes automation script values to sync with the NovaSeq 6000 System Denature and Dilute Libraries Guide (document # 1000000106351): * PhiX * NaOH * Tris-HCl * Bulk pool volume ## 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/novaseq6k-api-v3.5.1-release-notes.md?ask=&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.