bring in RNs

Author: ConnorLand

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

@@ -10,6 +10,29 @@ weight: 76
 This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for apps in production.
 {{% /alert %}}
 
+## 10.24.8 {#10248}
+
+**Release date: September ____, 2025**
+
+{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/10.24.8" text="Go to Marketplace" title="Download version 10.24.8 from the Marketplace" %}}
+
+### Improvements
+    
+- When tracing is enabled, the maximum depth of microflow calls and the maximum number of loops that are reported can be configured using the `mendix.tracing.max.microflow.depth` and `mendix.tracing.max.loop.iteration` JVM properties. The default value of these properties are `10`. The microflow call depth is calculated per runtime node and does not take into account calls made into other Mendix runtimes through REST/WebServices calls.
+
+### Fixes
+
+- **10.24.7 Fix** — We fixed a critical issue in 10.24.7 (only) where application startup would fail when upgrading a database originally created with a Mendix version before 10.17 and using foreign key constraints.
+
+- We fixed an issue where changing MxAdmin user's name in Studio Pro does not result in changing MxAdmin user's name in database. (Ticket 255505) 
+- We fixed an issue where SVG images would load with incorrect dimensions. (Ticket 258901)
+- When using Oracle, we no longer use `dbms.lob_substr` in the generated SQL for enumeration attributes with values shorter than 2000 characters. (Ticket 259283)
+- We fixed an issue where database synchronization could fail on SQL Server when a specialization of `System.User` was removed and there was still an `owner` or `changedBy` reference from an instance of `System.User` or a different specialization of it to an instance of the specialization being removed. 
+- We fixed an issue when saving a file, so that the suggested name would show as untitled.
+- We fixed an issue in Create Object Activity which would fail when creating an instance of a remote non-persistable entity in a microflow.
+- We fixed an issue in consumed REST services where choosing an OpenAPI contract without any operations would result in an error.
+- We fixed an issue where a warning was logged on startup about an already registered Jetty gauge when multiple listening addresses are specified. The connection metrics for Jetty are added per listening address and they now contain a tag `port` with the port number and a tag `host` if a host is specified. This is applicable to the metrics `jetty.connections.bytes.in`, `jetty.connections.bytes.out`, `jetty.connections.current`, `jetty.connections.max`, `jetty.connections.messages.in`, `jetty.connections.messages.out`, and `jetty.connections.request`. Be aware of the fact that there are usually two listening addresses when you specify **Open to current machine** for Runtime port security, for example 127.0.0.1 and ::1.
+
 ## 10.24.7 {#10247}
 
 **Release date: September 19, 2025**