2.8

Last modified: September 25, 2026

These release notes cover changes made to the Private Mendix Platform in version 2.8.

This is the LTS version release. Customers are encouraged to upgrade to this version. Previous MTS versions of Private Mendix Platform are no longer supported.

2.8.1

Release date: September 25, 2026

Version 2.8.1 of Private Mendix Platform introduces a number of new features, updates, and fixes.

New Features

Centralized Private Mendix Platform OCI Registry

To support fully automating the installation of Private Mendix Platform using Helm, we now provide a centralized download OCI registry. Private Mendix Platform and all its components, as well as the Helm charts required to install them, are offered from a central registry and repositories, enabling users to pull images and charts in an automated manner. For more information, see Private Mendix Platform Download Portal. (Ticket 287171)

Cluster Manager API

We have provided a new Cluster Manager API, consisting of API endpoints that allow automating the registration of new clusters, namespaces and resource plans. For more information, see Cluster Manager API.

Key Vault Integration

Private Mendix Platform can now use Azure Key Vault to automatically manage sensitive, environment-specific configuration, such as app constants, Mendix Runtime custom settings, the MxAdmin password, and the Debugger password. For more information, see Azure Key Vault Integration.

Improvements

Build and Deploy Pipeline Improvements

To allow for non-disruptive testing of pipelines, you can now create multiple Build and Deploy pipelines, and mark them as either Main or Draft. Pipelines designated as Main are used as the default, except for projects where you select a Draft pipeline as default. For more information, see Configuring the Pipeline Type.

Metrics Enhancements

We have made the following improvements to the Metrics page:

You can now filter the results by time span.
You can combine the metrics for all pods together instead of viewing them by pod.

Logs & Events Enhancements

We have made the following improvements to the Logs & Events page:

You can now filter the results by time span and by keywords.
You can search and download consolidated app logs.

Software Composition Enhancements

The Overview tab of the Software Composition page now shows a warning if an app uses an unsupported version of the Mendix Runtime.

API Enhancements

To support the new features of Private Mendix Platform, we have updated the following APIs:

Build - revisionId and branchName can now be used as filters in retrieving a package.
Deploy - We have added a new isKvValue flag to support Azure Key Vault integration.

For more information, refer to APIs for Private Mendix Platform.

UI and UX Improvements

We have improved the UI and UX for the following functionalities:

Commit history
Package Detail page
Constants
PAT creation

Updates

Studio Pro Updates

Studio Pro 9.24 LTS latest patch version updated to 9.24.44
Studio Pro 10.24 LTS latest patch version updated to 10.24.26
Studio Pro 11.6 MTS latest patch version updated to 11.6.10
Studio Pro 11.12 MTS latest patch version updated to 11.12.4

Other Platform Components

Mendix Operator version 2.28.1
Private Cloud License Manager (PCLM) version 0.11.2
Interactor v1.25.6
Interactor Bridge v1.24.7
Collector v1.23.9
Authenticator v1.19.5
Maia Appgen 0.39.4
Maia LLM Gateway 0.13.4
PDF Docgen v1.0.5

Fixes

(Marketplace Bundles) We have fixed an issue where the Supported Mendix versions filter does not work correctly when trying to create Marketplace bundles. (Tickets 286143, 286137)
(Marketplace Bundles) We have fixed an issue where there was no option to add multiple versions of a widget or module when trying to create Marketplace bundles. (Ticket 286140)
(Marketplace Bundles) We have fixed an issue where the required contents would not show in search when trying to create Marketplace bundles. (Ticket 286142)
(API) We have fixed an issue where the Group API did not correctly persist or return parentGroup values.
(API) We have fixed an issue where GET /groups would return identical values for name and parentGroup.
(API) We have fixed an issue where the Marketplace package creation API would return an HTTP 500 error instead of validating the request payload.
(API) We have fixed an issue with updating a namespace for an existing cluster through API.
(General) We have solved a problem with user assignment, where users could not be assigned to an application if they were already a part of a group with inherited access. (Ticket 286086)
(General) We have solved an issue with restarting the app, where despite the restart, the app would still show as running on the Environment Details page. (Ticket 283607)
(General) We have solved an issue where the number of replicas was not accurately reflected in Private Mendix Platform UI when scaling. (Ticket 283664)
(General) We have solved an issue where the app owner could be removed from the application, leaving the owner in a state where they could not be invited back. (Ticket 283910)
(General) We have provided a common Helmfile chart repository variable that can be defined once and used across all templates. (Ticket 287168)
(General) We have solved an issue where failed deployments would not show as failed. (Ticket 280980)
(General) We have fixed an issue that caused errors to show in the console when the users visited specific pages. (Ticket 284975)
(General) We have added a new ingress.tls value to expose ingress configuration for ingress. (Ticket 287157)
(General) We have solved an issue where timestamps would default to the year 2000 if data was unavailable in the Metrics page.
(General) We have fixed an issue with building images after an upgrade to the Build agent.
(General) We have provided a widget to enable page lifecycle hooks.

Known Issues

No Error Shown When Saving Secret Without Key Vault Permission

If the Managed Identity used by Private Mendix Platform does not have Write or Delete permissions in the Azure Key Vault environment, the write or delete does not happens and the error is visible in the logs. However the error is not shown to the user in the UI.