Third-Party Component Versions

Third-Party Component Versions#

Squirro installs a set of third-party components alongside the platform services. This page lists those components and the version included with each supported long-term support (LTS) series.

Versions are given as major and minor version numbers, written in the form 9.3.x. The .x stands for the patch level, which this page does not list because it changes as Squirro delivers security and stability updates. To check the exact versions on a running installation, see the Checking Installed Versions section.

For the platform requirements that must be met before installation, see the System Requirements page.

Supported LTS Releases#

Each LTS series is supported for two years. The support window starts with the date of the first LTS release in that series. The version tables in the sections below cover the LTS releases listed here. For more information about the release types and the support policy, see the Squirro Release Process page.

LTS series	First LTS release	Release date	End of support
3.15.x	3.15.5	May 13, 2026	May 13, 2028
3.14.x	3.14.4	November 5, 2025	November 5, 2027
3.13.x	3.13.6	July 29, 2025	July 29, 2027
3.12.x	3.12.1	February 26, 2025	February 26, 2027
3.11.x	3.11.6	December 11, 2024	December 11, 2026

Important

LTS patch releases deliver fixes within an existing support window and do not extend it. For example, the 3.14.x window runs from the release of 3.14.4, so the later 3.14.5 and 3.14.6 LTS patch releases end support on the same date as 3.14.4.

Squirro 3.10.6 LTS and earlier releases have passed the two-year support window and no longer receive fixes. For the release notes of each series, see the Release Notes page.

Component Versions by LTS Release#

The following components are part of a Squirro deployment. Unless a note states otherwise, they are installed and updated by the Squirro packages. Each column shows the versions in the most recent LTS release of that series.

Component	3.11.6	3.12.1	3.13.6	3.14.6	3.15.5
Elasticsearch	8.16.x	8.16.x	9.0.x	9.0.x	9.3.x
OpenSearch					3.4.x
Redis	7.2.x	7.2.x	7.2.x	7.2.x	7.2.x
Apache Tika	2.6.x	2.6.x	2.6.x	3.2.x	3.2.x
Apache ZooKeeper	3.4.x	3.4.x	3.4.x	3.4.x	3.4.x
Node.js					24.14.x
Nutrient PDF viewer					1.14.x

An empty cell means the component is not part of that release. Versions can also change between releases within the same series, including between LTS patch releases. For example, Apache Tika moved from 2.6.x to 3.2.x between the 3.14.4 and 3.14.5 LTS releases.

Apache ZooKeeper is removed as of Squirro 3.16.2. The LTS releases above still include it.
Node.js is included starting with Squirro 3.15.3.
The Nutrient PDF viewer, formerly PSPDFKit, is included starting with Squirro 3.15.4 and requires a license key. For more information, see the PDF Viewer page.
OpenSearch is a technical preview alternative to Elasticsearch, available from Squirro 3.15.1 and not recommended for production. The Squirro packages do not install an OpenSearch server. For more information, see the System Requirements page.

Document Conversion Components#

The following components support the PDF conversion and OCR processing paths. Their versions are the same in every supported LTS release listed above.

Component	Version	Notes
LibreOffice	7.4.x	Installed by the Squirro packages as a dependency of the PDF conversion service.
Tesseract OCR	4.1.x	Installed by the Squirro packages as a dependency of the OCR tooling.
Ghostscript	9.50 or later	Minimum requirement. Provided by the operating system, so the installed version is the one from the distribution.
Poppler	Not pinned by Squirro	Provided by the operating system.

Tesseract OCR and Ghostscript are installed on every node, but they are used only when the PDF OCR pipeline step runs as part of a pipeline. For more information, see the PDF OCR page.

Operating System Components#

Squirro does not build or pin the following components, so the version on a server is the one provided by the repository you install it from. For the components that come from the Red Hat Enterprise Linux or Rocky Linux repositories, the version is the one shipped with that distribution release, and security fixes come from the operating system vendor.

Component	Version
MariaDB server	The version provided by the distribution. Squirro sets no version constraint.
PostgreSQL server	Not installed by the Squirro packages and not managed by the Ansible role. Provision the server in advance. The documented on-premises procedure targets PostgreSQL 16.
Nginx	1.22.1 or later. This is a minimum requirement, not the version installed.
Java (OpenJDK)	Version 21. Install the `java-21-openjdk` package on every node before installing the Squirro packages.
Python	3.11.x only. The Squirro packages require the `python311` package at version 3.11.7 or a later patch version. Squirro builds the virtual environment that the platform services run in, but not the interpreter itself.
Container runtime	Not installed by the Squirro packages. Install an OCI-compatible runtime such as Docker or Podman before installing the GenAI package.

PostgreSQL is supported as an alternative to MariaDB. For setup instructions and for the version compatibility of a specific deployment, see the Configure PostgreSQL as the Database Backend page.

Unlisted Components#

This page covers the components that administrators manage as part of a deployment. It does not list the following:

Python package dependencies

The platform services depend on several hundred Python packages, which change with every release.
Operating system libraries

Low-level libraries that the Squirro packages declare as dependencies, such as libxml2, libxslt, openssl, and xmlsec1, are installed from the distribution repositories along with the packages that need them.
Client libraries

Libraries that the platform services link against, such as the MariaDB C connector, are installed as dependencies of the service packages. The database server version is the one that matters for compatibility planning, and it is listed in the Operating System Components section.
Machine learning models

Pretrained models are installed as separate packages and are versioned independently of the components above.
Development container images

Images used in the Squirro development environment are not part of a customer deployment.

For a complete inventory of the software included in a specific release, visit the Squirro Support website and submit a technical support request.

Checking Installed Versions#

To confirm the version of a specific component on a server, query the package manager:

rpm -q elasticsearch nginx mariadb-server java-21-openjdk python311
rpm -q squirro-redis-server squirro-libreoffice squirro-nodejs

To list every package installed on a node, sorted by name:

rpm -qa | sort

To list only the Squirro packages, including the platform services:

rpm -qa 'squirro-*' | sort

To write the full package list to a file, for example when preparing a support request:

rpm -qa | sort > /tmp/squirro-packages.txt

To check the build number of the Squirro platform itself, see the Checking Build Numbers section.