Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
75 changes: 75 additions & 0 deletions content/en/docs/releasenotes/studio-pro/11/11.12.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,71 @@ weight: 88

{{% alert color="info" %}}For highlights of this release, see the [Mendix Release 11.12](https://www.mendix.com/blog/mendix-release-11-12/) blog post.{{% /alert %}}

## 11.12.2 {#11122}

**Release date: July 24, 2026**

{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.12.2" text="Go to Marketplace" title="Download version 11.12.2 from the Marketplace" %}}

### New Features

- We added a **Location** setting to the **General** tab of the **Module Settings** dialog. It lets you choose whether a module is listed in the regular module list, or under the **Marketplace modules** node in the App Explorer.
- We added a **Copy Path** button to the notification that shows when the *App* folder fails to be excluded by an antivirus.
- We added a new setting to enable or disable OQL generation with Maia. OQL generation always uses the Mendix Platform regardless of the provider.
* This setting takes effect immediately, with one exception: if you are using the Studio Pro MCP Server a restart of Studio Pro is required for the changes to take effect. OQL generation with Studio Pro MCP Server is only possible with both the Enable Maia and Enable oql tool settings enabled.

### Improvements

#### Performance

- We improved build performance and reduced memory usage of the React client when bundling with Rspack. (Ticket 282716, 282165, 282605)
- We improved the performance logging infrastructure by integrating OpenTelemetry tracing, enabling correlated trace data for better diagnostics and profiling of Studio Pro operations.
- We made local deployment faster by improving the performance of microflows model export.

#### Other Improvements

- We improved the security of the module import process by validating the file paths declared in an MPK package before extraction. Packages containing paths that traverse outside the app directory or target protected directories (such as `.git`, `deployment`, or `releases`) are now rejected with an error.
- We fixed a bypass in the extraction-time path filter where non-canonical ZIP entry names (for example paths containing `..` segments) could evade the protected-subtree check. Entry names are now canonicalized before filtering.
- We now close the app selector before the **Open App** progress dialog when the Studio Pro main window is shown.
- We now delete the log files generated by Studio Pro that are older than 7 days.
- We now support the environment variables `MENDIX_TRACING_FILTER`, `MENDIX_TRACING_MAX_LOOP_ITERATION`, `MENDIX_TRACING_MAX_MICROFLOW_DEPTH` in addition to system properties for the Mendix OpenTelemetry Java agent extension.

### Fixes

- We resolved the issue that mxbuild would fail when compiling a project on macOS. (Ticket 278610)
- We fixed an issue that could cause an app to fail to bundle with Rspack enabled when a pluggable widget used certain Mendix modules, such as `mendix/parser` and `mendix/session`. (Ticket 282224)
- We fixed an issue in the microflow editor where clearing the selection did not update the **Properties** pane, so it kept showing the previously selected element instead of the microflow's own properties. (Tickets 282855, 283242)
- We fixed an issue where the content of the microflow editor and domain model editor (beta) canvas could appear blurry after scrolling or zooming. (Ticket 283927)
- We fixed an issue where the **History** pane would lose commit details (model changes and file changes) for unsynced local commits after a background Git refresh.
- We fixed an issue where using **Undo All** on multiple files created by Maia could show an unexpected error dialog in apps with online services enabled.
- We fixed an issue where using **Undo all** after deleting a file that was modified or created by Maia would cause an error.
- We fixed an issue where Change Data Capture AsyncAPI schemas were missing the `id` field in generated entity definitions.
- We fixed the Title widget to update its displayed text when navigating between pages in a native app.
- We fixed an issue where renaming a document would not update its name in the Maia changes list.
- We fixed an issue where the Change Data Capture service was allowing the addition of inherited attributes and associations when this is not supported.
- We fixed an issue where Studio Pro appeared to freeze briefly when opening an app. The progress dialog now covers the full loading process.
- We fixed an orientation issue in the native Date Picker widget for iOS.
- We changed the consistency check for offline Create and Change actions involving entities with AutoNumber or Calculated attributes from a hard error to a warning. The warning reminds you that AutoNumber values will default to `0` until the next synchronization, and Calculated attribute values will not be evaluated offline.
- We fixed an issue where local file storage did not use optimal directory structure.
- We fixed an issue where downloading a Marketplace module with Maia resulted in the name of the module being displayed in the version field. This is now resolved.
- We fixed an issue where the Mendix Marketplace MCP server connection would repeatedly disconnect and reconnect every few seconds.
- We fixed an issue where MCP connections could briefly disconnect and reconnect right after Studio Pro started up.
- We fixed an issue where requests sent to MCP servers identified themselves with a generic browser user agent instead of Studio Pro.
- We fixed an issue where Studio Pro could show a `No user is signed in` error while using an MCP server that requires Mendix Platform sign-in, while signed out.
- We fixed a bug where the Extensions Overview page would not open if the user was not signed in.
- We fixed a bug where reloading a Dev extension would cause a crash if extension tabs were still open.
- We fixed an issue where progress dialogs did not behave like their C# counterpart. Canceling a step now waits for it to finish and return its result. To exit the step and return its result immediately on cancel, pass `resolveImmediatelyOnCancel` to `IDialogApi.showProgressDialog`.

### Known Issues

* When using an Oracle database, invalid SQL is generated by the task queue subsystem, causing application startup to fail. (Ticket 275597)
* The Maia Chat panel may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**.
* Workaround: Manually close the panel when it appears.
* When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning.
* Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty.
* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat.
* Workaround: Click **New Chat** to make the Skills button appear without requiring a full restart. Note that **New Chat** is only available when the chat is not empty.

## 11.12.1 {#11121}

**Release date: July 15, 2026**
Expand Down Expand Up @@ -57,6 +122,16 @@ weight: 88
* PostgreSQL 13
* MariaDB 10.6

### Known Issues

* When using an Oracle database, invalid SQL is generated by the task queue subsystem, causing application startup to fail. (Ticket 275597)
* The Maia Chat panel may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**.
* Workaround: Manually close the panel when it appears.
* When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning.
* Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty.
* The **Skills** button in Maia Chat is not visible after adding skills via Maia. It becomes visible only after restarting the app, closing the project, or starting a new chat.
* Workaround: Click **New Chat** to make the Skills button appear without requiring a full restart. Note that **New Chat** is only available when the chat is not empty.

## 11.12.0 {#1112}

**Release date: June 30, 2026**
Expand Down