This release will only be available through manual upgrades. Clusters set to automatic upgrades will not receive this release. For how to configure upgrades, please see [classic](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-upgrade) or [managed](https://docs.microsoft.com/en-us/azure/service-fabric/how-to-managed-cluster-configuration) documentation.
## Contents
* [Service Fabric Packages and Versions](#service-fabric-packages-and-versions)
* [Service Fabric Feature and Bug Fixes](#service-fabric-feature-and-bug-fixes)
* [Retirement and Deprecation Path Callouts](#retirement-and-deprecation-path-callouts)
* [Repositories and Download Links](#repositories-and-download-links)
## Service Fabric Packages and Versions
The following packages and versions are part of this release:
| **Windows - 9.0.1553.9590<br>Ubuntu 18 - 9.0.1489.1<br>Ubuntu 20 - 9.0.1489.1** | **Feature** | Key Value Store (KVS) | **Brief Description**: "DatabaseFilesCorrupted" is a terminal error for the replica, requiring it to be dropped. This error occurs when the Extensible Storage Engine(ESE) Write change APIs return the DatabaseFilesCorrupted error, resulting in the replica being marked for compaction and flagged as a fault replica.<br>**Solution**: When a replica experiences database corruption via KVS Write APIs (e.g., Insert, Update, Delete), it is flagged with the repair task "MarkCompactTransientFault". Upon reopening, the JET_Compact API identifies the "DatabaseFilesCorrupted" state, initiating the repair policy that ultimately results in the replica being dropped. This solution ensures proper handling and repair of replicas affected by database corruption, maintaining system integrity.
| **Windows - 9.0.1553.9590<br>Ubuntu 18 - 9.0.1489.1<br>Ubuntu 20 - 9.0.1489.1** | **Bug** | Failover Manager | **Brief Description**: During a scaling-down scenario in Service Fabric, if an application upgrade is in progress, there is a possibility of Service Fabric miscalculating the MinimumInstancePercentage for stateless services. This can result in the application upgrade getting stuck. <br>**Solution**: The issue has been resolved, ensuring that Service Fabric accurately calculates the MinimumInstancePercentage during scaling down. This fix enables the application upgrade to progress smoothly without any disruptions. <br>**Workaround**: To mitigate the issue, set the MinInstancePercentage to 0 and utilize the MinInstanceCount instead.
| **Windows - 9.0.1553.9590<br>Ubuntu 18 - 9.0.1489.1<br>Ubuntu 20 - 9.0.1489.1** | **Bug** | Service Fabric Explorer (SFX) | **Brief Description**: The repair job timeline history has been updated to fix the incorrect ordering of claimed and approved actions. This correction ensures an accurate representation of the repair job actions in the history section, providing clarity for users reviewing the timeline.
* As aligned with [Microsoft .NET and .NET Core - Microsoft Lifecycle | Microsoft Learn](https://learn.microsoft.com/en-us/lifecycle/products/microsoft-net-and-net-core), SF Runtime has dropped support for Net Core 3.1 as of December 2022. For supported versions see [Service Fabric supported Linux versions](https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-versions#current-versions-1) and migrate applications as needed.
* Ubuntu 18.04 LTS will reach its 5-year end-of-life window on June, 2023. Service Fabric runtime will drop support for 18.04 LTS after the published date, and we recommend moving your clusters and applications to supported versions listed here: [Service Fabric supported Linux versions](https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-versions#supported-linux-versions-and-support-end-date)
* Service Fabric runtime will soon stop supporting BinaryFormatter based remoting exception serialization by default and move to using Data Contract Serialization (DCS) based remoting exception serialization by default. Current applications using it will continue to work as-is, but Service Fabric strongly recommends moving to using Data Contract Serialization (DCS) based remoting exception instead.
* As called out in the previous releases, Service Fabric runtime will remove Service Fabric runtime version 6.4 packages and older, SDK version 3.3 packages and older from the package Download Center in July 2023.
* Service Fabric runtime will soon be archiving and removing Service Fabric runtime versions less than 7.2 and older, as well as the corresponding SDK version 4.2 packages and older from the package Download Center. Archiving/Removing will affect application scaling and re-imaging of virtual machines in a Service Fabric Cluster running on unsupported versions. After older versions are removed/archived, this may cause failure while rolling back when the current in-progress upgrade has errors.<br>
To prevent disruption of workloads, create a new cluster using the following steps:<ul><li>[Create a Service Fabric cluster using ARM template](https://learn.microsoft.com/en-us/azure/service-fabric/quickstart-cluster-template)</li><li>[Create a Standalone cluster](https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-creation-for-windows-server)</li></ul> Install the supported version of Service Fabric SDK based on the Runtime version installed on the cluster.
