Upload RNs

Author: ConnorLand

content/en/docs/releasenotes/studio-pro/10/10.24.md

@@ -10,6 +10,40 @@ weight: 76
 This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for apps in production.
 {{% /alert %}}
 
+## 10.24.12 {#102412}
+
+**Release date: November ___, 2025**
+
+{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/10.24.12" text="Go to Marketplace" title="Download version 10.24.12 from the Marketplace" %}}
+
+### Improvements
+    
+- We implemented a feature that allows filtering out spans by their name. More details can be found in the documentation: https://docs.mendix.com/refguide/tracing-in-runtime/#testing
+-  The logout API in the new client `mx-api` now supports an optional params object with `reloadOnSuccess` flag. By default, `mx-api/logout` automatically reloads the page after a successful logout if you call it with no params object. If you pass a params object `{reloadOnSuccess: false}`, the automatic reload is disabled so you can implement your own custom logout flow and trigger reload yourself when needed.
+- We now log a warning when runtime operation parameters are missing during a database retrieval with an XPath constraint.
+
+This can happen, for example, when a nanoflow retrieve activity uses an XPath constraint that references an associated object that is not yet available in the nanoflow scope. In such cases, that would lead to unresolvable XPath. (Ticket 260339)
+
+### Fixes
+    
+* We upgraded the JDBC driver for Microsoft SQL Server to version 12.8.2, because of [CVE-2025-59250](https://www.cve.org/CVERecord?id=CVE-2025-59250).
+    * If you connect to SQL Server using integrated security in a module such as [Database Connector](https://marketplace.mendix.com/link/component/2888), you may need to update the JDBC driver in `userlib` as well.
+- Fixed an issue where XPath access rules on a view entity could lead to an "Object hash is invalid!" error. (Ticket 255889)
+- Fixed an issue that caused the microflow execution to abort when the “Sync to Device” action failed in offline apps due to missing files. (Ticket 261053)
+
+- We fixed an issue where undoing a widget update could lead to an inconsistent model, causing an error when attempting to reopen the project. We now prevent undo actions for widget updates to safeguard against similar issues. (Tickets 256004, 260822)  
+-  We fixed an issue where conditional editability expressions in snippet calls incorrectly references variables when nested snippets were involved. (Tickets 257120, 262408)
+- We now allow first time users to use Studio Pro without loggin in when opening Studio Pro for the first time.
+- We fixed memory leaks related to the style document editor.
+- We fixed an issue where OQL query parsing would fail if the query included a numeric WHEN clause without an accompanying ELSE condition. Ticket(#255719).
+- We fixed an issue for the Message Definitions editor where custom values for editable fields like 'External Name' disappeared. (Ticket 263144, 263609, 263817, 264535, 264805, 264850)
+- We fixed an issue in consumed OData services in Studio Pro, where importing a metadata file with incorrect XML namespaces would show and "Importing..." progress dialog without ever completing the import.
+- We fixed an issue where `Core.getLicenseInformation().products()` did not return a numeric value if the value was larger than 2147483647.
+- We fixed an issue that prevented the dialog from closing when pressing the Escape key while editing an access rule (ticket 257016).
+- We fixed an issue where source maps for pluggable widgets were not included correctly in the React client bundle when "Optimize bundle" is set to "No". (Ticket 261353)
+- Fixed an issue where widgets with unbounded dynamic imports (e.g. `await import(path);`) would result in a bundling error when using the React client. They are now marked as external which means they will be resolved when the widget is loaded in the browser. (Ticket 261630)
+- We fixed a bug where nanoflows would not be exported when re-added to a page after a full deployment cycle. The issue occurred when a nanoflow was removed from a page during hot-reload, followed by a full deployment, and then re-added during another hot-reload.
+
 ## 10.24.11 {#102411}
 
 **Release date: November 4, 2025**