Add breaking change documentation for .NET runtime SIGTERM signal handler removal

docs/core/compatibility/10.0.md

@@ -32,6 +32,7 @@ If you're migrating an app to .NET 10, the breaking changes listed here might af
 | [Default trace context propagator updated to W3C standard](core-libraries/10.0/default-trace-context-propagator.md) | Behavioral change | Preview 4 |
 | [LDAP DirectoryControl parsing is now more stringent](core-libraries/10.0/ldap-directorycontrol-parsing.md) | Behavioral change | Preview 1 |
 | [MacCatalyst version normalization](core-libraries/10.0/maccatalyst-version-normalization.md) | Behavioral change | Preview 1 |
+| [.NET runtime no longer provides default SIGTERM signal handler](core-libraries/10.0/sigterm-signal-handler.md) | Behavioral change | Preview 5 |
 | [System.Linq.AsyncEnumerable included in core libraries](core-libraries/10.0/asyncenumerable.md) | Source incompatible | Preview 1 |
 
 ## Extensions

docs/core/compatibility/core-libraries/10.0/sigterm-signal-handler.md

@@ -0,0 +1,55 @@
+---
+title: "Breaking change: .NET runtime no longer provides default SIGTERM signal handler"
+description: "Learn about the breaking change in .NET 10 where the runtime no longer provides a default SIGTERM signal handler."
+ms.date: 06/06/2025
+ai-usage: ai-assisted
+ms.custom: https://github.com/dotnet/docs/issues/46226
+---
+# .NET runtime no longer provides default SIGTERM signal handler
+
+On Unix systems, the .NET runtime no longer provides a default SIGTERM signal handler. On Windows, the .NET runtime no longer provides default handlers for the [`CTRL_CLOSE_EVENT` and `CTRL_SHUTDOWN_EVENT` signals](/windows/console/handlerroutine), which are equivalents of Unix `SIGTERM` signal.
+
+This change reverts the SIGTERM signal handling behavior to what it used to be in .NET Framework and classic Mono runtime.
+
+## Version introduced
+
+.NET 10 Preview 5
+
+## Previous behavior
+
+Previously, a SIGTERM signal handler registered by the .NET runtime by default triggered graceful application exit. <xref:System.AppDomain.ProcessExit?displayProperty=nameWithType> and <xref:System.Runtime.Loader.AssemblyLoadContext.Unloading?displayProperty=nameWithType> events were raised before the application exited.
+
+## New behavior
+
+Starting in .NET 10, the .NET runtime does not override SIGTERM signal handling provided by the operating system. The typical default SIGTERM signal handler provided by the operating system terminates the application immediately. <xref:System.AppDomain.ProcessExit?displayProperty=nameWithType> and <xref:System.Runtime.Loader.AssemblyLoadContext.Unloading?displayProperty=nameWithType> events aren't raised.
+
+## Type of breaking change
+
+This is a [behavioral change](../../categories.md#behavioral-change).
+
+## Reason for change
+
+The SIGTERM signal handler registered by the .NET runtime by default was both insufficient for some app models (for example, console and containerized applications) and incompatible with other app models (for example, Windows services). It's better to leave it to higher-level libraries or application code to register signal handlers appropriate for the given app model.
+
+## Recommended action
+
+- No action is necessary for typical ASP.NET applications or applications that use higher-level APIs such as <xref:Microsoft.Extensions.Hosting.HostingHostBuilderExtensions.UseConsoleLifetime*?displayProperty=nameWithType> to handle app-model specific concerns. These higher-level APIs register handlers for SIGTERM and other signals as appropriate.
+
+- If you want to handle SIGTERM signal without taking a dependency on higher-level libraries, you can replicate the previous behavior by creating a SIGTERM signal handler in your `Main` method using the <xref:System.Runtime.InteropServices.PosixSignalRegistration.Create%2A?displayProperty=nameWithType> API:
+
+```csharp
+static void Main()
+{
+    using var termSignalRegistration =
+        PosixSignalRegistration.Create(
+            PosixSignal.SIGTERM,
+            (_) => Environment.Exit(0));
+
+    // Your application code here
+}
+```
+
+## Affected APIs
+
+- <xref:System.AppDomain.ProcessExit?displayProperty=fullName>
+- <xref:System.Runtime.Loader.AssemblyLoadContext.Unloading?displayProperty=fullName>

docs/core/compatibility/toc.yml

@@ -28,6 +28,8 @@ items:
                 href: core-libraries/10.0/ldap-directorycontrol-parsing.md
               - name: MacCatalyst version normalization
                 href: core-libraries/10.0/maccatalyst-version-normalization.md
+              - name: No default SIGTERM signal handler
+                href: core-libraries/10.0/sigterm-signal-handler.md
               - name: System.Linq.AsyncEnumerable included in core libraries
                 href: core-libraries/10.0/asyncenumerable.md
           - name: Cryptography
@@ -1412,6 +1414,8 @@ items:
                 href: core-libraries/10.0/ldap-directorycontrol-parsing.md
               - name: MacCatalyst version normalization
                 href: core-libraries/10.0/maccatalyst-version-normalization.md
+              - name: No default SIGTERM signal handler
+                href: core-libraries/10.0/sigterm-signal-handler.md
               - name: System.Linq.AsyncEnumerable included in core libraries
                 href: core-libraries/10.0/asyncenumerable.md
           - name: .NET 9