SENTIENT v4.2.x upgrade instructions for Docker Compose

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every SENTIENT upgrade. This ensures your SENTIENT service runs with the latest best-practice parameters and configurations, while also guarantees that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of SENTIENT - be aware that the manifests in master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target SENTIENT version while merging deployment files.

If you are upgrading from 4.2, you must run the script below. However, if you are upgrading from version 4.2.1+, DO NOT run the upgrade script; proceed directly to starting the service.

This version has known security vulnerabilities that are fixed in newer releases. We recommend upgrading to the latest patch version instead.

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every SENTIENT upgrade. This ensures your SENTIENT service runs with the latest best-practice parameters and configurations, while also guarantees that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of SENTIENT - be aware that the manifests in master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target SENTIENT version while merging deployment files.

If you are upgrading from 4.2, you must run the script below. However, if you are upgrading from version 4.2.1.x, DO NOT run the upgrade script; proceed directly to starting the service.

We strongly recommend that you also update your Docker Compose deployment manifests to the corresponding version from GitHub repository with every SENTIENT upgrade. This ensures your SENTIENT service runs with the latest best-practice parameters and configurations, while also guarantees that all required services are correctly deployed to support the newest features introduced in the release.

If you are running older releases of SENTIENT - be aware that the manifests in master branch of the repository may contain configurations for features that are not available in your specific version. Always ensure that manifests are compatible with your target SENTIENT version while merging deployment files.

If you are upgrading from version 4.1, you must run the script below