> 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/clarity-lims-v6.3-and-lablink-v2.5/readme/release-notes-clarity-lims-v6.3.6.md).

# Release Notes Clarity LIMS v6.3.6

Published: September 2026

Last Update: November 2026

Latest Release: v6.3.6

This Release Notes describe the key changes made to software components for Clarity LIMS v6.3.6. The Clarity LIMS v6.3.6 patch release supersedes v6.3.5 and is intended for customers on or migrating to Clarity LIMS v6.3.6.

{% hint style="info" %}
Note: All customers on older versions of Clarity LIMS v6.2 and v6.3 are strongly recommended to upgrade their instance(s) to Clarity LIMS v6.3.6.
{% endhint %}

## LabLink Patch (November 2026)

LabLink v2.5.6.2 is available for Clarity LIMS v6.3.6 and replaces LabLink v2.5.6.0. This patch does not change the Clarity LIMS version.

### Bug Fixes

* Fixed an issue in LabLink where Project and User custom field configured as a text dropdown, with custom entries disabled, does not open on the Create Project and Create User page. Users cannot select an option other than the default value.

***

## Clarity LIMS v6.3.6 (September 2026)

### New Features

* A new System Settings property, `clarity.product.projectSummary.statsEnabled` (default: `true`), controls whether the Project Summary statistics panel is displayed on the Projects & Samples page. Set the property to `false` to hide the panel and improve the performance of the Projects & Samples page on systems with a large number of derived samples.

### Updates

* Elasticsearch has been updated from v8.6.2 to v9.4.4.
* RabbitMQ has been updated from v3.11.9 to v4.3.4.
* PostgreSQL has been updated from v15.18 to v15.19.
* Clarity LIMS search services via Elasticsearch have been updated to connect using a configured service account.

### Bug and Security Vulnerability Fixes

* Fixed an issue where EPP automation error messages failed to be reported back to Clarity LIMS when the API user password contained certain special characters, causing a pattern syntax error in the Automation Worker.
* Fixed security vulnerabilities.

### Known Issues

Refer to [Known Issues for Clarity LIMS v6.3](/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/known-issues-v6.3.x.md) for the list of known issues for Clarity LIMS v6.3.

### Additional Notes

Refer to [Additional Notes for Clarity LIMS v6.3](/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/additional-notes-v6.3.x.md) for the list of additional notes for Clarity LIMS v6.3.

The following are additional notes applicable to Clarity LIMS v6.3.6:

* PostgreSQL 15.19 is now qualified to run in Clarity LIMS v6.3.6.


---

# 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/clarity-lims-v6.3-and-lablink-v2.5/readme/release-notes-clarity-lims-v6.3.6.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.