Upload SP 11.14 RNs

content/en/docs/.claude/settings.local.json

@@ -0,0 +1,7 @@
+{
+  "permissions": {
+    "allow": [
+      "Read(//c/Users/Maria.Shaposhnikova/Documents/docs/releasenotes/studio-pro/11/**)"
+    ]
+  }
+}

content/en/docs/releasenotes/studio-pro/11/11.14.md

@@ -0,0 +1,127 @@
+---
+title: "11.14"
+url: /releasenotes/studio-pro/11.14/
+description: "The release notes for Mendix Studio Pro 11.14 (including all patches) with details on new features, bug fixes, and known issues."
+weight: 86
+# KI: "Maia Chat panel issue": MID-317 (check if fixed in 11.14)
+# KI: "BYO LLM": SPAM-435 (check if fixed in 11.14)
+# KI: "Maia Skills button": (check if fixed in 11.14)
+--- 
+
+## 11.14.0 {#11140}
+
+**Release date: August ___, 2026**
+
+{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.14.0" text="Go to Marketplace" title="Download version 11.14.0 from the Marketplace" %}}
+
+### New Features
+
+#### Java 25
+
+We now support Java 25 in Studio Pro.
+- This release ships with Java Development Kit (JDK) 25 and Gradle 9.5.1.
+- You can now configure your application to use Java 25 in the project settings.
+- In the Studio Preferences you can configure a different JDK for each supported version of Java.
+- Targeting Java 25 allows the project to use language constructs and APIs that were introduced with Java 25.
+- Newly created projects will be configured to use Java 25 by default.
+- Gradle 9.5.1 supports both Java 21 and 25. Java 25 requires Gradle 9.1+.
+- Support for Java 21 is deprecated.
+
+We recommend that projects and Marketplace modules upgrade to Java 25.
+
+#### Other New Features
+
+- We added support for updating a module from a file for module packages created below Studio Pro 11.12.0. After you provide the *.mpk* files, Studio Pro attempts to map documents by name. The update then runs the merge algorithm and, if needed, conflict resolution, so you can keep any customizations made to the module.
+- Maia now supports working with **Change Data Capture** documents.
+- We now prefix versioned deployment packages with the branch name they were created with: {BranchName}-{AppName}_{Version}.mda
+- A module ID can now be passed to the element selector for the `selectedElementId` property, and the corresponding module is preselected and expanded. This allows you to directly create a new document of the desired type in that module.
+- We added a capability to the **Clear from device** nanoflow action that removes specific objects from the offline device storage. You can now select individual objects or object lists to clear, in addition to clearing all objects of an entity.
+- You can now create a branch directly from a specific commit in the **History** pane by right-clicking the commit and selecting **Create branch...**.
+- We added a **Branch line** filter to the **History** pane toolbar. You can now select any branch from a searchable dropdown to view its commit history without switching your working branch. The filter can be cleared with the **×** button or the **Reset filters** button. The **Revert Commit** option is hidden when viewing the history of a branch other than the current one.
+- Maia can now answer basic questions about your version control history and commit and push changes to the server.
+- We added the ability to filter out the on-disk changes on the **Comparison** pane.
+- We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest).
+- The `mx` command-line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (add-on and solution) modules. The System module remains excluded.
+- The `mx` command-line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the Marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy.
+
+
+### Improvements
+
+#### Performance
+
+- We improved build performance and reduced memory usage of the React client when bundling with Rspack. (Ticket 282716, 282165, 282605)
+
+#### Other Improvements
+
+- We improved the sort function in the **ListOperation** activity. We now use the ICU4J library instead of Java's built-in Collator for sorting lists in microflows. This ensures consistent sorting results in both microflows and nanoflows. (Ticket 263311)
+- Items in the **Comparison** pane are now sorted by default, first by module and then by document type.
+- We now delete the log files generated by Studio Pro that are older than seven days.
+- We added support for the following database versions:
+    - MariaDB 12.3
+    - MySQL 9.7
+- In the logic editors, we improved the way sequence flow arrows are drawn.
+- In the logic editors, Maia now enforces best practices more strictly.
+- We added a new context menu item to links in Maia Chat messages to open them in your default browser via the **Open link in browser** context menu item.
+- We improved the **Maia Skills** pane by updating the filter toggle to use a clearer label (*Show errors only*) and more appropriate icons.
+- We updated Maia Agent's visual design to align with EU AI Act compliance guidelines for improved transparency and readability.
+- We changed the **JSON Structure** document editor to open in a tab instead of a dialog. If you encounter any issues, you can revert to the previous editor by clearing **Preferences** > **New Features** > **Use the modernized editor for JSON Structure**.
+- When logging HTTP requests and responses, the Mendix Runtime now omits the value of the Authorization, Cookie, Proxy-Authorization, Set-Cookie, and X-Auth-Token headers, whereas previously it only omitted the value of the Authorization header.
+- We added new `BiConsumer<IContext, IMendixObject>` overloads to `ListenersRegistry`, `ActionListener`, and `EventActionInfo` so that event listener callbacks now receive the active `IContext` alongside the object. The existing `Consumer<IMendixObject>` methods are deprecated and will be removed in Mendix 12.
+- We upgraded the Java Migration Tool that is downloaded by the Studio Pro installer to version 1.0.2. This version adds a recipe to fix the deprecated `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the various `ListenersRegistry.register*Listener` methods.
+- You can now use <kbd>Enter</kbd> to navigate between Maia's questions and submit your answers without reaching for the mouse. {TW}
+- We updated Rspack to version 2.1, which reduces bundle times by up to 25%.
+- We improved React client bundling diagnostics with clearer reporting for memory-related bundler failures.
+- We reduced the exported bundle size for the React and Native clients when a translatable text (such as a caption or text template) contains parameters. Only the parts of the text that actually differ between languages are now translated, instead of duplicating the entire text for every language. {TW}
+
+### Fixes
+
+- We fixed an error in offline-first (PWA) apps on iOS 26.5.2 and above, where synchronizing a newly added image or file document failed because its contents were not included in the upload. (Ticket 248368)
+- We fixed an issue in the React client mode where snippets did not load properly when navigating to a page with the same snippet. (Ticket 281906)
+- We fixed an issue where Studio Pro did not update the Java proxies during deployment after renaming a module. (Ticket 282363)
+- We fixed an issue where attribute references in microflow expressions were not updated when the attribute was renamed in the domain model. (Tickets 282373, 282363)
+- We fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket 283531)
+- We fixed an issue where an editable condition set to **Never** was lost during widget conversion. (Ticket 283552)
+- We fixed an issue on Windows where pressing <kbd>Ctrl</kbd> + <kbd>F</kbd> in the CSS editor or JavaScript editor opened the global **Find** dialog instead of the editor's built-in search. (Ticket 283730)
+- We fixed an issue where JavaScript actions with npm dependencies installed in their `actions/node_modules` folder failed to bundle in the React client, for both the Rollup and Rspack bundlers. (Ticket 283840)
+- We fixed an issue where text box values filled in by a password manager were not registered. (Ticket 284395, 283505)
+- We fixed an issue where expanding a folder in a document selector (for example, when selecting a microflow, nanoflow, or JSON structure) showed it as expanded but without its contents. (Ticket 284451)
+- We fixed an issue where opening the Git preferences threw an unexpected error when Studio Pro could not load your Git configuration (for example, when Git was not installed or its location was set incorrectly). Studio Pro now shows a clear message explaining how to resolve it.
+- We fixed an issue where activities in microflows generated by Maia showed the default caption **Activity** instead of a caption describing the activity.
+- We fixed an issue where Studio Pro incorrectly went into offline mode at startup due to a transient SSL connection failure when fetching the OpenID configuration.
+- We fixed an issue where Maia did not create sufficient spacing before and after loops within microflows.
+- We fixed an issue where Studio Pro froze while a progress dialog is shown, for example, while opening an app.
+- We fixed an issue where Studio Pro froze for up to several seconds during copy operations when another process held a lock on the clipboard.
+- We fixed an issue where Studio Pro incorrectly displayed consistency errors after opening an app.
+- We fixed an issue where the active document's tab got scrolled out of view after opening many documents in a row.
+- We fixed an issue where renaming a module or an entity led to consistency errors in microflow expressions.
+- We fixed an issue where Maia named single objects returned from a **Retrieve Action** as "{entity}List".
+- We fixed custom icon visibility for an exposed microflow, Java and JavaScript actions based on icon availability and selected Studio Pro theme.
+- We fixed an issue where the in-editor Recommender dialog still appeared for empty microflows, nanoflows, and rules after all Recommender features were disabled in **Preferences** > **AI**.
+- We fixed an issue where the content of the microflow editor and domain model editor (Beta) canvas appeared blurry after scrolling or zooming.
+- We fixed an issue where the **Push your changes** notification bar was incorrectly shown after a merge or cherry-pick that produced no actual model changes. Studio Pro now detects this scenario and shows an informational message instead.
+- We fixed an issue where some grid cells in Studio Pro became empty while scrolling the grid.
+- We fixed an issue where concurrent Git operations failed with an *index is locked* error when the version control status bar polled for conflict information at the same time as write operations such as reset or checkout.
+- We resolved an issue where using **Undo All** in the **Changes** pane did not remove the overview pages generated by **Start with Maia**.
+- We fixed Maia's inability to create *While* loops.
+- We fixed an issue in the MCP settings pane where the **Enable all** and **Disable all** buttons remained clickable even when all tools were already in that state. The buttons are now disabled when they have no effect.
+- We removed the *theme.compiled.css.map* from the deployment package due to privacy and security concerns.
+- We fixed an issue where date filters sent to OData services with DateTimeOffset attributes contained the wrong date format, causing the remote service to reject the request.
+- We fixed an issue in Studio Pro where publishing a microflow in a new REST service allowed adding that service to read-only modules such as the System module.
+- We fixed an issue where opening a non-version-controlled app after a version-controlled one, the **Comparison** pane was showing old comparison data.
+- We fixed an issue where Studio Pro appeared frozen when marking or unmarking a module as a UI resources module. A progress dialog is now shown while the app is synchronized with the file system.
+- We fixed an issue in the modernized App Explorer where Studio Pro appeared unresponsive after moving documents or folders. A progress dialog is now shown until the App Explorer has finished updating.
+- We fixed an issue in the modernized **Find Results** pane where closed result sets reappeared and the displayed number of open result sets was incorrect.
+- We fixed an issue in the modernized App Explorer where actions triggered with keyboard shortcuts could apply to the previously selected node.
+- We fixed an issue where pressing <kbd>Escape</kbd> to close a modal dialog also closed the sidebar.
+- We fixed an issue in the microflow editor where sometimes the loop was selected when trying to select elements inside the loop.
+
+### Deprecations
+
+- We deprecated support for Java 21. Support for Java 21 will be removed in the future. Mendix recommends using Java 25.
+- The `Consumer<IMendixObject>` overloads of `ListenersRegistry.register*Listener`, `ActionListener.addBeforeEvent`, `ActionListener.addAfterEvent`, and the matching `EventActionInfo` constructors are deprecated as of Mendix 11.14.0 and will be removed in Mendix 12. Use the `BiConsumer<IContext, IMendixObject>` overloads instead, which also provide the active context to the callback.
+
+### Breaking Changes
+
+- Requests to servlets registered via `Core.addDevelopmentServlet` now require authentication. The M2EE admin password must be provided in the `X-M2EE-Authentication` header (Base64-encoded).
+
+### Known Issues