Version 15.0.0 Release Notes
Jul 23rd, 2026
Suite Home
The new Suite Home page provides a centralized entry point for accessing Mia-Platform Suite products and managing tenant-related settings.
Available capabilities include:
- Access to all tenants and products available for the current user.
- Recently used items for faster navigation.
- Tenant switching through the project switcher.
- Administration features for managing tenants, groups, and roles.
- Integrated AI assistant support for navigation and common user requests.
- Quick access to Suite products, including Console, Flow, Data Fabric, and P4SaMD, while preserving the selected tenant context.
Platform Administration
Platform Administration is the new area of the Mia-Platform Suite where administrators govern access across all products from a single place. It brings together RBAC (Role-Based Access Control) and User Management on top of a unified, centralized authorization model.
Through Platform Administration you can manage:
- Organizations.
- Tenants.
- Users and groups.
- Roles and permissions.
With User Management, admins handle the people and groups that make up a tenant; with RBAC, they define roles and permissions and assign them to individual users or groups, shaping access rules according to their organization structure. Because the authorization model is centralized, Suite components rely on a single source of truth for permissions instead of maintaining independent access configurations.
For more information, go to the Platform Administration documentation.
Catalog
We are introducing Catalog, a brand-new component of Mia-Platform that lets teams centralize, govern, and connect any entity that lives in their organization — services, infrastructure resources, datasets, AI assets, processes — and make them discoverable across the platform.
Catalog ships with a REST API, a web Backoffice, a typed relationship graph, a compliance layer (rules, scorecards, campaigns), a growing set of connectors that keep the catalog in sync with GitHub, GitLab, Bitbucket, Azure, Azure DevOps, Google Cloud, the Mia-Platform Console, Sonatype Nexus, and Sysdig Secure, and an MCP server that exposes the catalog to AI agents.
This release also adds automated notifications for compliance campaigns (start, completion, and progress updates) and a dedicated MCP server that lets AI assistants like Claude Desktop, VS Code, Cursor, or Windsurf query and update the Catalog through natural language.
For more information, go to the Catalog documentation and visit Mia-Platform v15 Overview.
AI Foundry
We are introducing AI Foundry, a new component of Mia-Platform for building, deploying, and governing AI-powered experiences. AI Foundry provides a unified environment to configure agents, manage LLM models, prompts, tools, and skills, compose multi-step agentic workflows through the Playbook Builder, and test everything in a live AI Playground — all governed as first-class catalog resources.
For more information, go to the AI Foundry documentation and visit Mia-Platform v15 Overview.
Flow
Flow is in beta. We are actively shaping the product, so things may change as we iterate. Your feedback is welcome.
We are introducing Flow, a new component of Mia-Platform that brings visual workflow orchestration to the platform. Flow lets business and technical stakeholders design, execute, and monitor end-to-end processes that span microservices, data pipelines, and human-in-the-loop steps on a single canvas.
For more information, go to the Flow documentation and visit Mia-Platform v15 Overview.
Design Helm Charts and Deploy with Kustomize
This feature is only available for projects using the Enhanced Workflow.
Console now provides a dedicated Charts section in the Design Area, allowing teams to create, manage, and configure Helm chart configurations directly within their Console Projects.
The integrated editor provides rich Helm-specific language support, making it easier to work on complex chart configurations with confidence.
The entire chart lifecycle — from editing to saving, versioning, and deploying — is fully integrated with the existing Console Design and Deploy workflows.
The integrated editor provides rich Helm-specific language support, making it easier to work on complex chart configurations with confidence.
To learn more about the features available in the new Charts section of the Design Area, and to understand how Git commits of chart configuration files and their deployment are handled via Kustomize, CI/CD pipelines, and MLP, please refer to the Configure Helm Charts documentation.
Infrastructure Projects Deprecation
Infrastructure Projects are deprecated as of v15.0.0 and can no longer be used. The feature never left its BETA stage and has now been discontinued. Starting from v15.0.0 it is no longer possible to create new Infrastructure Projects.
This deprecation only affects the Infrastructure Project type. Infrastructure Resources in the Software Catalog and the infrastructure management capabilities of Application Projects are not impacted.
Other New Features, Improvements and Bug Fixes
Improvements
Stream Processor v0.8.0
The new version v0.8.0 of the Stream Processor is available!
Starting from v0.8.0, the Stream Processor is published as four distinct Docker images to reduce image size and avoid bundling unnecessary database drivers:
- 0.8.0 - supported caches: MongoDB, FarmData, HTTP REST
- 0.8.0-mongodb - supported caches: MongoDB, FarmData, HTTP REST
- 0.8.0-postgres - supported caches: PostgreSQL, FarmData, HTTP REST
- 0.8.0-no-db - supported caches: FarmData, HTTP REST
The 0.8.0 and 0.8.0-mongodb tags are functionally equivalent and point to the same build.
This minor release adds PostgreSQL as a cache option (when using the new 0.8.0-postgres image) and SSL mode support for cache connections.
Check the service changelog for the full list of changes.
Stream Processor v0.7.2
The new versions v0.7.2, v0.7.1 and v0.7.0 of the Stream Processor are available!
v0.7.2 moves cache key string validation exclusively to the MongoDB cache layer.
v0.7.1 adds support for shared/dedicated DLQ producer and fixes a partition revoke leak. The same fix has also been backported to v0.6.4.
v0.7.0 introduces a breaking change in cache key handling: cache index keys are now enforced to be strings only. If a non-conforming value (object, array, number, etc.) is provided as a cache key, the Stream Processor will either crash or terminate the operation to the DLQ (if configured). Users relying on Kafka keys as-is or already using plain strings are not affected by this change.
Check the service changelog for the full list of changes.
Farm Data v0.6.3
The new version v0.6.3 of Farm Data is available!
This patch release fixes the handling of MergeStageNoMatchingDocument errors (error code 13113) in the read-write pipeline, improving resiliency in scenarios where no matching document is found during a merge stage.
Check the service changelog for the full list of changes.
Single View Trigger Generator v3.5.2
The new version v3.5.2 of Single View Trigger Generator is available!
This patch release updates the heartbeat timer to survive rebalances across batches.
Check the service changelog for the full list of changes.
Improvements
Diffing support for Fast Data v1 ER-Schema
It is now possible to diff ER-Schema Fast Data v1 resources in the merge, compare, and unsaved local changes views.
Console SSO for extensions now backed by Keycloak
Starting from this release, enabling Console SSO for an extension registers it as a client within the extensibility Keycloak realm, and the *Console SSO* card in the extension detail page now shows additional fields, such as the client's clientId.
If you already configured Console SSO for an extension on a Console version prior to v15, after upgrading you need to disable and re-enable the Console SSO toggle, and re-save the Callback URL. See the Console SSO documentation for the full list of migration steps.
Bug fixes
- Fixed an issue where the Redeploy action from Deploy History was incorrectly sending the most recent configuration payload instead of the one associated with the selected historical deployment.
- Fixed an issue where the Deploy section could display information related to an environment different from the one shown in the Environment dropdown. The Deploy section now always reflects the environment currently selected in the dropdown.
- Fixed an issue where clicking on an extension added at the Runtime Area level incorrectly redirected users to the Pods section instead of opening the extension.
- Fixed an issue where Azure DevOps pipeline statuses were incorrectly reported as
succeededwhile the pipeline was still running. - Fixed an issue where navigating to any Runtime Area section other than Pods caused the area selector to incorrectly switch to the Overview area. The selector now correctly remains on Runtime regardless of which Runtime section is selected.
- Fixed an issue where the External Orchestrator Generator activation card was incorrectly displayed in the Settings of Standard Workflow projects. The card is now only shown for Enhanced Workflow projects, where the feature is supported.
- Fixed an issue in the Deploy History where switching the status filter back to All Status after selecting a specific status triggered a 400 error and caused the history list to disappear.
- Fixed an issue where updating a service version from the new Microservices page did not correctly propagate the Docker image update.
Improvements
CSV Import supports both `,` and `;` delimiters in Column Lineage
When importing column lineage relations via CSV for a Virtual Job, the frontend now supports whether the file uses , or ; as delimiter.
This feature is supported starting from v0.5.2 of data-catalog-frontend service.
For more information about the Data Catalog Application and the latest service versions, check out the compatibility matrix.
Bug fixes
- Fixed an issue where patching
columnLineageof jobs was not correctly escaping.and$characters. This fix is included in versionv0.5.1of the Open Lineage service.
How to update
To run Mia-Platform v15.0.0, the following Helm chart versions must be installed on your cluster. For the complete installation sequence and per-product upgrade guides, see the Installation Guidelines.
Helm chart versions
| Product | Helm Chart | Version | Upgrade guide |
|---|---|---|---|
| Auth — Keycloak | keycloak-operator | 0.5.4 | How to upgrade |
| Auth — Realm Management | keycloak-realm-management | 0.1.28 | How to upgrade |
| Homepage & RBAC | services | 0.2.65 | How to upgrade |
| Catalog | catalog | 0.3.28 | How to upgrade |
| AI Foundry | ai-foundry | 0.4.79 | How to upgrade |
| Console | console | 15.0.15-0 | How to upgrade |
Bill of materials
Click on each chart to expand its full image list.
keycloak-operator v0.5.4
| Image repository | Version |
|---|---|
| nexus.mia-platform.eu/platform/auth/keycloak | 0.3.2-26.6.4-postgres |
| quay.io/keycloak/keycloak-operator | 26.6.4 |
keycloak-realm-management v0.1.28
| Image repository | Version |
|---|---|
| docker.io/adorsys/keycloak-config-cli | latest-26.5.4 |
services v0.2.65
| Image repository | Version |
|---|---|
| docker.io/redis | 8.4.0 |
| nexus.mia-platform.eu/ai-foundry/adk-be-app | 0.7.2 |
| nexus.mia-platform.eu/cache/envoyproxy/envoy | v1.36.2 |
| nexus.mia-platform.eu/core/swagger-aggregator | 3.9.4 |
| nexus.mia-platform.eu/platform/auth/access-control/ext-authz | 0.2.2-nocache |
| nexus.mia-platform.eu/platform/auth/authtool/authtool-bff | 0.5.2 |
| nexus.mia-platform.eu/platform/services/homepage | 0.3.4 |
| nexus.mia-platform.eu/platform/services/rbac-management | 0.1.5 |
| quay.io/docling-project/docling-serve-cpu | v1.24.0 |
catalog v0.3.28
| Image repository | Version |
|---|---|
| docker.io/redis | 8.4.0 |
| nexus.mia-platform.eu/ai-foundry/adk-be-app | 0.7.2 |
| nexus.mia-platform.eu/cache/envoyproxy/envoy | v1.36.2 |
| nexus.mia-platform.eu/catalog/catalog-engine | 0.7.3 |
| nexus.mia-platform.eu/catalog/catalog-mcp-server | 0.2.3 |
| nexus.mia-platform.eu/catalog/catalog-website | 0.3.4 |
| nexus.mia-platform.eu/catalog/items-consumer | 0.1.0 |
| nexus.mia-platform.eu/catalog/items-producer | 0.1.0 |
| nexus.mia-platform.eu/core/swagger-aggregator | 3.9.4 |
| nexus.mia-platform.eu/data-fabric/stream-processor | 0.8.1-postgres |
| nexus.mia-platform.eu/p4samd/core/policy-engine | v0.9.0 |
| nexus.mia-platform.eu/platform/auth/access-control/ext-authz | 0.2.2-nocache |
| nexus.mia-platform.eu/platform/auth/authtool/authtool-bff | 0.5.2 |
| nexus.mia-platform.eu/plugins/smtp-mail-notification-service | 3.5.1 |
| quay.io/docling-project/docling-serve-cpu | v1.24.0 |
ai-foundry v0.4.79
| Image repository | Version |
|---|---|
| docker.io/redis | 8.4.0 |
| nexus.mia-platform.eu/ai-foundry/adk-be-app | 0.7.2 |
| nexus.mia-platform.eu/ai-foundry/ai-foundry-bff | 0.3.3 |
| nexus.mia-platform.eu/ai-foundry/ai-foundry-website | 0.7.3 |
| nexus.mia-platform.eu/cache/envoyproxy/envoy | v1.36.2 |
| nexus.mia-platform.eu/platform/auth/access-control/ext-authz | 0.2.2-nocache |
| nexus.mia-platform.eu/platform/auth/authtool/authtool-bff | 0.5.2 |
| quay.io/docling-project/docling-serve-cpu | v1.24.0 |
console v15.0.15-0
| Image repository | Version |
|---|---|
| docker.io/envoyproxy/ratelimit | 19f2079f |
| nexus.mia-platform.eu/back-kit/mfe-toolkit-on-prem | 1.3.13 |
| nexus.mia-platform.eu/cache/envoyproxy/envoy | v1.32.1 |
| nexus.mia-platform.eu/console/aggregated-website | 1.6.1 |
| nexus.mia-platform.eu/console/backend | 33.2.1 |
| nexus.mia-platform.eu/console/catalog-service | 1.7.2 |
| nexus.mia-platform.eu/console/deploy-service | 8.4.0 |
| nexus.mia-platform.eu/console/environments-variables | 3.6.1 |
| nexus.mia-platform.eu/console/events-manager | 1.5.0 |
| nexus.mia-platform.eu/console/extensibility-manager | 3.0.0 |
| nexus.mia-platform.eu/console/favorites-service | 2.3.1 |
| nexus.mia-platform.eu/console/feature-toggle-service | 1.3.7 |
| nexus.mia-platform.eu/console/kubernetes-service | 8.4.6 |
| nexus.mia-platform.eu/console/mcp-server | 1.2.1 |
| nexus.mia-platform.eu/console/mia-assistant | 1.4.0 |
| nexus.mia-platform.eu/console/mia-craft-bff | 1.2.5 |
| nexus.mia-platform.eu/console/notification-provider | 2.2.5 |
| nexus.mia-platform.eu/console/project-service | 2.1.0 |
| nexus.mia-platform.eu/console/rbac-manager-bff | 2.1.2 |
| nexus.mia-platform.eu/console/scripts/bindings-cleaner | 1.2.2 |
| nexus.mia-platform.eu/console/scripts/configuration-history-cleaner | 0.4.1 |
| nexus.mia-platform.eu/console/scripts/marketplace-sync | 10.11.0 |
| nexus.mia-platform.eu/console/scripts/mia-assistant-embeddings-importer | latest |
| nexus.mia-platform.eu/console/scripts/software-catalog-sync | 0.7.25 |
| nexus.mia-platform.eu/console/scripts/version-upgrader | 11.1.7 |
| nexus.mia-platform.eu/console/tenant-overview | 4.2.1 |
| nexus.mia-platform.eu/core/authorization-service | 2.4.3 |
| nexus.mia-platform.eu/core/client-credentials | 3.4.1 |
| nexus.mia-platform.eu/core/crud-service | 6.10.3 |
| nexus.mia-platform.eu/core/proxy-manager | 3.5.0 |
| nexus.mia-platform.eu/core/swagger-aggregator | 3.9.6 |
| nexus.mia-platform.eu/microlc/middleware | 3.4.0 |
| nexus.mia-platform.eu/plugins/files-service | 2.10.5 |
| nexus.mia-platform.eu/plugins/ses-mail-notification-service | 3.5.0 |
| nexus.mia-platform.eu/platform/auth/authtool/authtool-bff | 0.5.2 |
| nexus.mia-platform.eu/rond-authz/rond | 1.14.2 |