Semaphore 5.12.1

Semaphore 5.12.1 is a maintenance update to Semaphore 5.12.0.

Refer to semaphore-v5.12.1-23.october.2026.txt for the bill of materials.

Important: Starting with Semaphore 5.12.0, the minimum supported Java version is Java 21.

Before installing or upgrading to this version of Semaphore, review the following:

For general information:

• Third-party software requirements (Linux)
• Third-party software requirements (Windows)

For installation server requirements:

• Plan your Semaphore Installation (Linux)
• Plan your Semaphore Installation (Windows)

Generative AI notice

Starting with Semaphore 5.10.0, if you have access to an Azure OpenAI Service, it is possible to use the AI Model Builder incorporated into the Knowledge Model Manager (KMM) tool.

Important: When using the AI Model Builder, you must use your own Azure OpenAI Service. Progress is not a party to any agreement between you and Azure. Progress has no control over the Azure OpenAI Service or its availability and cannot be held liable for any output, errors, damages, losses, or other results of your use of the third-party generative AI integrated into the KMM tool. The cost of using the Azure OpenAI Service is charged by Azure to your Azure account.

Semaphore Cloud navigation

New functionality

• 26692—To help you move between Semaphore Cloud applications more easily, a shared navigation menu was added to provide a consistent header across supported applications. These changes do not apply to on-premises installations.

Docker images

Issues resolved

• 38150—The Knowledge Model Manager Docker image used a hardcoded alerting-service URL, preventing connections to a non-default alerting endpoint. The alerting URL is now configurable, and you can use JVM_OPTS_APPEND to append additional JVM options without replacing the image's default options.

  For deployment and configuration guidance, see Using Progress-supplied Docker images.

Model Management

Issues resolved

• 38194—The SpaceMissions example model produced constraint violations when running the Constraint Violations report.

• 38595—Model backups incorrectly included the internal _Data directory, containing Jena database files. New backups no longer include this directory, and the directory is excluded when restoring backups that contain it.

• 39714—After restoring a model from a backup, some context menu actions were missing despite the user having the required permissions.

• 39876—Saving exposed SKOS external mapping relationships failed when their range was set to a workspace model, with or without a selected class..

CMIS Widget

Issues resolved

• 39585, 39586, 39587, 39589—The CMIS widget failed to classify uploaded files or create new concepts when using the supplied example configuration. Request errors sometimes left the widget blank instead of displaying an error message. The toolkit also had incomplete setup guidance, an expired example access token, a potentially conflicting example port, and missing stylesheet assets.

Reconciliation Service

Issues resolved

• 29741—The Reconciliation Service did not respect the skosGraph setting for entity suggestions used in Knowledge Model Manager, allowing suggestions to include resources other than concepts.

• 38140—Reconciliation queries to Virtuoso-backed SPARQL endpoints could fail or time out. Generated queries unconditionally used the transitive rdfs:subPropertyOf* path and ORDER BY ?label, including for endpoints without subproperty hierarchies.

Concepts Server

Issues resolved

• 36441—Publishing to the Concepts Server sometimes failed with an XDMP-NOTXN transaction-not-found error when requests to a multi-node MarkLogic cluster passed through a load balancer.

• 38672, 39670—The identifier scheme API's allterms and hierarchy endpoints handled FILTER=MODIFIED_AFTER timestamps inconsistently. The hierarchy endpoint sometimes rejected timestamps accepted by the allterms endpoint.

Semantic Enhancement Service

Issues resolved

• 39588—The Windows installer accepted Java versions below the required Java 21. As a result, the service appeared to be running but returned HTTP 503 errors for all requests.

Configuration

Issues resolved

• 38146—On Linux, when a Semaphore application failed to start because of an incompatible Java version, the journalctl and systemctl output did not display a clear diagnostic message.

Vulnerabilities

Issues resolved

• 38169—Knowledge Model Manager was enhanced to resolve a potential security vulnerability.

• 38931—The MarkLogic connector was enhanced to resolve a potential security vulnerability.

List of all fixed vulnerabilities