From aee7e1f237602d152a5d097e0e7c694683af7003 Mon Sep 17 00:00:00 2001 From: "MENDIXDOMAIN\\Maria.Shaposhnikova" Date: Wed, 10 Jun 2026 13:35:41 +0200 Subject: [PATCH 1/2] Add 11.6.7 Studio Pro release notes --- .../docs/releasenotes/studio-pro/11/11.6.md | 63 +++++++++++++++++-- 1 file changed, 59 insertions(+), 4 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.6.md b/content/en/docs/releasenotes/studio-pro/11/11.6.md index df1cc3b7d1a..6b8a31ec63b 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.6.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.6.md @@ -8,6 +8,61 @@ mts: true {{% alert color="info" %}}For highlights of this release, see the [Mendix Release 11.6](https://www.mendix.com/blog/release-11-6-zero-downtime-deployments-workflow-advances/) blog post.{{% /alert %}} +## 11.6.7 {#1167} + +**Release date: June ___, 2026** + +{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.6.7" text="Go to Marketplace" title="Download version 11.6.7 from the Marketplace" %}} + +### New Features + +#### Rspack (beta) + +- We now support **Rspack** as a new bundler for React client applications, delivering faster bundling and lower memory usage. Rspack is currently in public beta and aims to be the future replacement for Rollup. While Rollup remains fully supported as the default bundler, we recommend trying Rspack by selecting it via the new `App bundler` setting under Project → Settings → Runtime. The bundler setting is stored in a file named `app-bundler` in the project root. +- Rspack is now generally available for React client applications. It delivers faster bundling and lower memory usage. Rollup remains the default bundler for now, but we recommend switching to Rspack. + +### Improvements + +- We updated the .NET Runtime to version 10.0.7. +- We added a confirmation dialog when enabling anonymous user access in App Security, warning that unrestricted anonymous roles may expose data unintentionally. +- We now automatically stop Gradle daemons when you exit Studio Pro, so unnecessary background processes no longer continue running. (Ticket 258422) +- We improved default values for the SessionKeepAliveUpdatesInterval (now 100 seconds) and ClusterManagerActionInterval (now 5 minutes) runtime settings. If these defaults are incompatible with the configured SessionTimeout, they will be automatically derived as before. +- Runtime nodes now automatically shut down when heartbeat updates fail or when the node's database entry is missing, improving cluster reliability and preventing orphaned nodes. +- We improved observability for retrieve and other runtime operations by including XPath constraints, entity paths, object types, and microflow names in OpenTelemetry span names. +- We clean up duplicate cluster management tasks during startup. +- We improved cleanup of queued tasks that are owned by missing nodes. +- We clarified the error message when upgrading solutions with files that have paths that are too long. +- We added themecache.css files to .gitignore to reduce conflicts when edited by multiple users. +- We added temporary java files to .gitignore to reduce conflicts when edited by multiple users. + +### Fixes + +- We fixed an issue where an Oops pop-up window appeared when a microflow or nanoflow was configured with a return value mapping which was referring to an attribute but was not enclosed within a data view. (Ticket 278235) +- We fixed an issue where Studio Pro erroneously showed a security consistency error when a microflow or nanoflow's return value mapping referred to an attribute that was not within its direct enclosing data view. +- We fixed an issue where commit notes and metadata were empty after a rebase when there were no MPR changes and no conflicts detected by git. +- We fixed SQLite Error 5: 'database is locked' error. +- We fixed an issue when studio pro wasn’t able to find git after fresh installation if it was run from installer. (Ticket 232343,232540,232452,234800,231989) +- We added a small delay between retries of saving conflicting project files due to rare occurrences of race conditions. +- Fixed an issue where the Microsoft Defender exclusion utility would fail to run +- We have fixed an issue where constants from protected modules were not exported when creating a portable app deployment package using MxBuild. +- We have fixed an issue where exporting a Portable App Package could fail because file copy operations were performed outside the default file-system scope. +- We fixed an issue where import and export mappings incorrectly showed consistency errors for microflows with unmapped optional parameters. Optional parameters now use their default values when not provided in the payload. Converter microflows must have exactly one required parameter which receives the value to be converted and may have additional optional parameters. (Ticket 250969) +- We fixed an issue where an Import Mapping would not read JSON attribute values when a JSON attribute was preceded by another attribute with an attribute name that is a prefix. For example `StatusId` and `Status`. We also improved how JSON objects were read when one object name was a prefix of another object name. (Ticket 266571, 277780) +- We fixed an issue in the **Select Elements** dialog of an XML import or export mapping where reopening the dialog with previously checked elements that contained inheritance or choice-type children caused a validation error "Element '…' cannot be checked without a checked child element." when clicking OK. This happened because those elements were not expanded, so their children were not loaded and could not be validated. Studio Pro now automatically expands such elements before clicking OK in the **Select Elements** dialog, ensuring all required child elements are properly loaded and resolved. (Ticket 268403) +- We fixed an issue when an older offline client (from a Mendix version before 11.6.5) would fail to synchronize with a HTTP 560 (Invalid JSONRequest) error, preventing the offline app from loading. (Ticket 274811) +- We fixed an issue where a native mobile app crashed with a synchronization error on startup when a user role did not have access to a module whose entity was included in the app's offline synchronization profile. The app now completes synchronization and returns no objects for that entity, matching the behavior of the previous XPath-based synchronization. (Ticket 241791) +- We have added Microsoft related MIME types. (Tickets 276471, 276598, 276604, 276958) +- We have upgraded Netty dependencies to fix CVE-2026-42578, CVE-2026-42583, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-42577, CVE-2026-42579. (Tickets 278202, 278290, 277691, 278290) +- Resolved an OS command injection vulnerability in the Git process runner reported by Veracode. +- Fixed an issue that could cause the History pane to unexpectedly crash. +- We fixed conversion of Partial clone to Full clone. Now Mendix Version is displayed in new history panel after converting Partial clone to Full. +- In the React client, we now copy files from a pluggable widget's `assets` subdirectory into the widget's directory under `dist/` during bundling, even when they are not directly imported by the widget. (Ticket 274514) +- We fixed an issue where projects located in a folder whose name contained special characters (for example an '&') would fail to run locally. (ticket 275109) +- Fixed an issue when using the Rollup bundler with the React client. +- Fixed a rare race condition related to authtokens. +- We fixed an issue with the client where passing an empty string as a parameter to a microflow triggered an error. For example, when filtering options of a combo box with a microflow, clearing the search string would trigger the error. This would occur for apps with the [new string behavior](https://docs.mendix.com/refguide/runtime-tab/#new-string-behavior) disabled. (Ticket 271819) +- We fixed a visual bug affecting **Call a nanoflow** action properties of widgets. Depending on the order in which the actions were configured, nanoflow settings of a different property would get displayed. + ## 11.6.6 {#1166} **Release date: May 1, 2026** @@ -62,7 +117,7 @@ Additionally, some Marketplace modules could have an incorrect version string in * We fixed `TabContainer` not updating the active tab attribute or firing the **onChange** nanoflow on tab switch when the TabContainer entity is passed as a nanoflow argument. ### Deprecations - + * From July 6, 2026, we will drop support for the following database versions that are no longer supported by the vendors: * PostgreSQL 13 * MariaDB 10.6 @@ -213,7 +268,7 @@ For more information, see [Portable App Distribution](/developerportal/deploy/po {{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.6.1" text="Go to Marketplace" title="Download version 11.6.1 from the Marketplace" %}} ### Improvements - + * We introduced a new log node named **SystemTask** for logging system management actions. * We improved the performance of runtime statistics collection. * We improved the performance of the **Best Practice Recommender**. It now runs faster while using less memory. @@ -278,7 +333,7 @@ In general, logic that has primitive parameters can be more easily reused as it Additionally, page parameters can now be marked as **Optional** and be given a **Default value** expression. When a parameter is optional, it is not necessary to assign it an [argument value](/refguide/page-parameter/#argument) when opening a page from a button, action, microflow, or nanoflow. Unassigned optional parameters will be set to their default value when the page is opened. Optional parameters make it easy to extend pages, allowing you to add new parameters without the need to update all existing usages. ### Improvements - + * We made an improvement to the scheduling of cluster node management actions. * The experimental Java API `OqlStatement` to run OQL statements now also supports **INSERT INTO SELECT** statements to create new objects. * We added extra validations for **OQL UPDATE** statements. For more information, see the [UPDATE Statement](/refguide/oql-statements/#oql-update) section of *OQL Statements* for details. @@ -336,7 +391,7 @@ Additionally, page parameters can now be marked as **Optional** and be given a * * We fixed a bug where the File Uploader was not clickable when nested in a container. ### Breaking Changes - + * We upgraded the AWS S3 library used for S3 file storage backend from version 1 to 2. This new version of the library has stricter configuration handling and only supports AES for client side encryption. More information can be found in [Upgrading from Mendix Studio Pro 10 to 11](/refguide/upgrading-from-10-to-11/#amazon-s3-sdk-upgrade) and [S3 Storage Service Settings](/refguide/custom-settings/#amazon-s3-storage-service-settings). * We added a consistency check for code actions that have a filename that does not match the casing of the document name, which could cause issues on certain operating systems, and when deploying to the cloud environment. From 8528e6475410c2a6a197b439514bab928f13e8dd Mon Sep 17 00:00:00 2001 From: MarkvanMents Date: Thu, 11 Jun 2026 15:47:14 +0200 Subject: [PATCH 2/2] Apply Vale and linter suggestions --- .../docs/releasenotes/studio-pro/11/11.6.md | 82 +++++++++---------- 1 file changed, 41 insertions(+), 41 deletions(-) diff --git a/content/en/docs/releasenotes/studio-pro/11/11.6.md b/content/en/docs/releasenotes/studio-pro/11/11.6.md index 6b8a31ec63b..e5fa8b75ca0 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.6.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.6.md @@ -16,52 +16,52 @@ mts: true ### New Features -#### Rspack (beta) +#### Rspack (Beta) -- We now support **Rspack** as a new bundler for React client applications, delivering faster bundling and lower memory usage. Rspack is currently in public beta and aims to be the future replacement for Rollup. While Rollup remains fully supported as the default bundler, we recommend trying Rspack by selecting it via the new `App bundler` setting under Project → Settings → Runtime. The bundler setting is stored in a file named `app-bundler` in the project root. -- Rspack is now generally available for React client applications. It delivers faster bundling and lower memory usage. Rollup remains the default bundler for now, but we recommend switching to Rspack. +* We now support **Rspack** as a new bundler for React client applications, delivering faster bundling and lower memory usage. Rspack is currently in public beta and aims to be the future replacement for Rollup. While Rollup remains fully supported as the default bundler, we recommend trying Rspack by selecting it via the new `App bundler` setting under Project → Settings → Runtime. The bundler setting is stored in a file named `app-bundler` in the project root. +* Rspack is now generally available for React client applications. It delivers faster bundling and lower memory usage. Rollup remains the default bundler for now, but we recommend switching to Rspack. ### Improvements -- We updated the .NET Runtime to version 10.0.7. -- We added a confirmation dialog when enabling anonymous user access in App Security, warning that unrestricted anonymous roles may expose data unintentionally. -- We now automatically stop Gradle daemons when you exit Studio Pro, so unnecessary background processes no longer continue running. (Ticket 258422) -- We improved default values for the SessionKeepAliveUpdatesInterval (now 100 seconds) and ClusterManagerActionInterval (now 5 minutes) runtime settings. If these defaults are incompatible with the configured SessionTimeout, they will be automatically derived as before. -- Runtime nodes now automatically shut down when heartbeat updates fail or when the node's database entry is missing, improving cluster reliability and preventing orphaned nodes. -- We improved observability for retrieve and other runtime operations by including XPath constraints, entity paths, object types, and microflow names in OpenTelemetry span names. -- We clean up duplicate cluster management tasks during startup. -- We improved cleanup of queued tasks that are owned by missing nodes. -- We clarified the error message when upgrading solutions with files that have paths that are too long. -- We added themecache.css files to .gitignore to reduce conflicts when edited by multiple users. -- We added temporary java files to .gitignore to reduce conflicts when edited by multiple users. +* We updated the .NET Runtime to version 10.0.7. +* We added a confirmation dialog when enabling anonymous user access in App Security, warning that unrestricted anonymous roles may expose data unintentionally. +* We now automatically stop Gradle daemons when you exit Studio Pro, so unnecessary background processes no longer continue running. (Ticket 258422) +* We improved default values for the SessionKeepAliveUpdatesInterval (now 100 seconds) and ClusterManagerActionInterval (now 5 minutes) runtime settings. If these defaults are incompatible with the configured SessionTimeout, they will be automatically derived as before. +* Runtime nodes now automatically shut down when heartbeat updates fail or when the node's database entry is missing, improving cluster reliability and preventing orphaned nodes. +* We improved observability for retrieve and other runtime operations by including XPath constraints, entity paths, object types, and microflow names in OpenTelemetry span names. +* We clean up duplicate cluster management tasks during startup. +* We improved cleanup of queued tasks that are owned by missing nodes. +* We clarified the error message when upgrading solutions with files that have paths that are too long. +* We added themecache.css files to .gitignore to reduce conflicts when edited by multiple users. +* We added temporary Java files to .gitignore to reduce conflicts when edited by multiple users. ### Fixes -- We fixed an issue where an Oops pop-up window appeared when a microflow or nanoflow was configured with a return value mapping which was referring to an attribute but was not enclosed within a data view. (Ticket 278235) -- We fixed an issue where Studio Pro erroneously showed a security consistency error when a microflow or nanoflow's return value mapping referred to an attribute that was not within its direct enclosing data view. -- We fixed an issue where commit notes and metadata were empty after a rebase when there were no MPR changes and no conflicts detected by git. -- We fixed SQLite Error 5: 'database is locked' error. -- We fixed an issue when studio pro wasn’t able to find git after fresh installation if it was run from installer. (Ticket 232343,232540,232452,234800,231989) -- We added a small delay between retries of saving conflicting project files due to rare occurrences of race conditions. -- Fixed an issue where the Microsoft Defender exclusion utility would fail to run -- We have fixed an issue where constants from protected modules were not exported when creating a portable app deployment package using MxBuild. -- We have fixed an issue where exporting a Portable App Package could fail because file copy operations were performed outside the default file-system scope. -- We fixed an issue where import and export mappings incorrectly showed consistency errors for microflows with unmapped optional parameters. Optional parameters now use their default values when not provided in the payload. Converter microflows must have exactly one required parameter which receives the value to be converted and may have additional optional parameters. (Ticket 250969) -- We fixed an issue where an Import Mapping would not read JSON attribute values when a JSON attribute was preceded by another attribute with an attribute name that is a prefix. For example `StatusId` and `Status`. We also improved how JSON objects were read when one object name was a prefix of another object name. (Ticket 266571, 277780) -- We fixed an issue in the **Select Elements** dialog of an XML import or export mapping where reopening the dialog with previously checked elements that contained inheritance or choice-type children caused a validation error "Element '…' cannot be checked without a checked child element." when clicking OK. This happened because those elements were not expanded, so their children were not loaded and could not be validated. Studio Pro now automatically expands such elements before clicking OK in the **Select Elements** dialog, ensuring all required child elements are properly loaded and resolved. (Ticket 268403) -- We fixed an issue when an older offline client (from a Mendix version before 11.6.5) would fail to synchronize with a HTTP 560 (Invalid JSONRequest) error, preventing the offline app from loading. (Ticket 274811) -- We fixed an issue where a native mobile app crashed with a synchronization error on startup when a user role did not have access to a module whose entity was included in the app's offline synchronization profile. The app now completes synchronization and returns no objects for that entity, matching the behavior of the previous XPath-based synchronization. (Ticket 241791) -- We have added Microsoft related MIME types. (Tickets 276471, 276598, 276604, 276958) -- We have upgraded Netty dependencies to fix CVE-2026-42578, CVE-2026-42583, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-42577, CVE-2026-42579. (Tickets 278202, 278290, 277691, 278290) -- Resolved an OS command injection vulnerability in the Git process runner reported by Veracode. -- Fixed an issue that could cause the History pane to unexpectedly crash. -- We fixed conversion of Partial clone to Full clone. Now Mendix Version is displayed in new history panel after converting Partial clone to Full. -- In the React client, we now copy files from a pluggable widget's `assets` subdirectory into the widget's directory under `dist/` during bundling, even when they are not directly imported by the widget. (Ticket 274514) -- We fixed an issue where projects located in a folder whose name contained special characters (for example an '&') would fail to run locally. (ticket 275109) -- Fixed an issue when using the Rollup bundler with the React client. -- Fixed a rare race condition related to authtokens. -- We fixed an issue with the client where passing an empty string as a parameter to a microflow triggered an error. For example, when filtering options of a combo box with a microflow, clearing the search string would trigger the error. This would occur for apps with the [new string behavior](https://docs.mendix.com/refguide/runtime-tab/#new-string-behavior) disabled. (Ticket 271819) -- We fixed a visual bug affecting **Call a nanoflow** action properties of widgets. Depending on the order in which the actions were configured, nanoflow settings of a different property would get displayed. +* We fixed an issue where an Oops pop-up window appeared when a microflow or nanoflow was configured with a return value mapping which was referring to an attribute but was not enclosed within a data view. (Ticket 278235) +* We fixed an issue where Studio Pro erroneously showed a security consistency error when a microflow or nanoflow's return value mapping referred to an attribute that was not within its direct enclosing data view. +* We fixed an issue where commit notes and metadata were empty after a rebase when there were no MPR changes and no conflicts detected by Git. +* We fixed SQLite Error 5: 'database is locked' error. +* We fixed an issue when Studio Pro wasn’t able to find Git after fresh installation if it was run from installer. (Ticket 232343,232540,232452,234800,231989) +* We added a small delay between retries of saving conflicting project files due to rare occurrences of race conditions. +* Fixed an issue where the Microsoft Defender exclusion utility failed to run +* We have fixed an issue where constants from protected modules were not exported when creating a portable app deployment package using MxBuild. +* We have fixed an issue where exporting a Portable App Package failed because file copy operations were performed outside the default file-system scope. +* We fixed an issue where import and export mappings incorrectly showed consistency errors for microflows with unmapped optional parameters. Optional parameters now use their default values when not provided in the payload. Converter microflows must have exactly one required parameter which receives the value to be converted and may have additional optional parameters. (Ticket 250969) +* We fixed an issue where an Import Mapping did not read JSON attribute values when a JSON attribute was preceded by another attribute with an attribute name that is a prefix. For example `StatusId` and `Status`. We also improved how JSON objects were read when one object name was a prefix of another object name. (Ticket 266571, 277780) +* We fixed an issue in the **Select Elements** dialog of an XML import or export mapping where reopening the dialog with previously checked elements that contained inheritance or choice-type children caused a validation error "Element '…' cannot be checked without a checked child element." when clicking OK. This happened because those elements were not expanded, so their children were not loaded and nor validated. Studio Pro now automatically expands such elements before clicking OK in the **Select Elements** dialog, ensuring all required child elements are fully loaded and resolved. (Ticket 268403) +* We fixed an issue when an older offline client (from a Mendix version before 11.6.5) failed to synchronize with a HTTP 560 (Invalid JSONRequest) error, preventing the offline app from loading. (Ticket 274811) +* We fixed an issue where a native mobile app crashed with a synchronization error on startup when a user role did not have access to a module whose entity was included in the app's offline synchronization profile. The app now completes synchronization and returns no objects for that entity, matching the behavior of the previous XPath-based synchronization. (Ticket 241791) +* We have added Microsoft related MIME types. (Tickets 276471, 276598, 276604, 276958) +* We have upgraded Netty dependencies to fix CVE-2026-42578, CVE-2026-42583, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-42577, CVE-2026-42579. (Tickets 278202, 278290, 277691, 278290) +* Resolved an OS command injection vulnerability in the Git process runner reported by Veracode. +* Fixed an issue that caused the History pane to crash. +* We fixed conversion of Partial clone to Full clone. Now Mendix Version is displayed in new history panel after converting Partial clone to Full. +* In the React client, we now copy files from a pluggable widget's `assets` subdirectory into the widget's directory under `dist/` during bundling, even when they are not directly imported by the widget. (Ticket 274514) +* We fixed an issue where projects located in a folder whose name contained special characters (for example an '&') failed to run locally. (ticket 275109) +* Fixed an issue when using the Rollup bundler with the React client. +* Fixed a rare race condition related to authtokens. +* We fixed an issue with the client where passing an empty string as a parameter to a microflow triggered an error. For example, when filtering options of a combo box with a microflow, clearing the search string would trigger the error. This occurred for apps with the [new string behavior](https://docs.mendix.com/refguide/runtime-tab/#new-string-behavior) disabled. (Ticket 271819) +* We fixed a visual bug affecting **Call a nanoflow** action properties of widgets. Depending on the order in which the actions were configured, nanoflow settings of a different property werfe displayed. ## 11.6.6 {#1166} @@ -298,7 +298,7 @@ For more information, see [Portable App Distribution](/developerportal/deploy/po ## 11.6.0 {#1160} {{% alert color="warning" %}} -Owing to an unforeseen issue, if you downloaded Mendix version 11.6.0 between 23 December 2025 and 6 January 2026, you may have received the wrong build. +Owing to an unforeseen issue, if you downloaded Mendix version 11.6.0 between December 23, 2025 and January 6, 2026, you may have received the wrong build. To ensure you have the correct build, download version 11.6.0 again. @@ -311,7 +311,7 @@ Mendix apologizes for the inconvenience. ### New Features -* We have redesigned the way the menus work in our Extensibility APIs (browse our API docs by Studio Pro version [here](/apidocs-mxsdk/apidocs/)). They no longer require the `commandId` property or listening to the `menuItemActivated` event. They now contain an `action` property which will be invoked directly when the menu is clicked. +* We have redesigned the way the menus work in our Extensibility APIs (browse our [API docs by Studio Pro version](/apidocs-mxsdk/apidocs/)). They no longer require the `commandId` property or listening to the `menuItemActivated` event. They now contain an `action` property which will be invoked directly when the menu is clicked. * Please note that this is a breaking change. Your extension needs to update its usages of the menus to the new structure. * The modernized (web) runtime console is now available through a preference in the **New Features** tab. * For custom and pluggable widget we introduced the `` element for pluggable widgets, allowing you to enhance their definitions so Maia can provide smarter development assistance by understanding your widget's purpose and properties.