dotnet · dotnet-policy-service · Jul 22, 2025 · Jul 21, 2025 · Jul 21, 2025 · Jul 21, 2025
diff --git a/.github/ISSUE_TEMPLATE/02-breaking-change.yml b/.github/ISSUE_TEMPLATE/02-breaking-change.yml
@@ -23,12 +23,15 @@ body:
       options:
         - .NET 8
         - .NET 9
-        - .NET 10 Preview 1
-        - .NET 10 Preview 2
-        - .NET 10 Preview 3
         - .NET 10 Preview 4
         - .NET 10 Preview 5
         - .NET 10 Preview 6
+        - .NET 10 Preview 7
+        - .NET 10 RC 1
+        - .NET 10 RC 2
+        - .NET 10 GA
+        - .NET 11 Preview 1
+        - .NEt 11 Preview 2
         - Other (please put exact version in description textbox)
     validations:
       required: true

diff --git a/.github/dependabot.yml b/.github/dependabot.yml
@@ -1361,6 +1361,17 @@ updates:
       dotnet:
         patterns:
           - "*" # Prefer a single PR per project update.
+  - package-ecosystem: "nuget"
+    directory: "/docs/core/diagnostics/snippets/resource-monitoring-with-manual-metrics" #resource-monitoring-with-manual-metrics.csproj
+    schedule:
+      interval: "weekly"
+      day: "wednesday"
+    open-pull-requests-limit: 5
+    groups:
+      # Group .NET updates together for projects.
+      dotnet:
+        patterns:
+          - "*" # Prefer a single PR per project update.
   - package-ecosystem: "nuget"
     directory: "/docs/core/diagnostics/snippets/resource-monitoring" #resource-monitoring.csproj
     schedule:
@@ -2186,14 +2197,3 @@ updates:
       dotnet:
         patterns:
           - "*" # Prefer a single PR per project update.
-  - package-ecosystem: "nuget"
-    directory: "/docs/core/resilience/snippets/resilience" #resilience.csproj
-    schedule:
-      interval: "weekly"
-      day: "wednesday"
-    open-pull-requests-limit: 5
-    groups:
-      # Group .NET updates together for projects.
-      dotnet:
-        patterns:
-          - "*" # Prefer a single PR per project update.
diff --git a/.github/prompts/whats-new-net.md b/.github/prompts/whats-new-net.md
@@ -0,0 +1,44 @@
+When you're assigned an issue where one label includes the word "Release" and you're given a link to an issue with this prompt file as context to update the what's new in .NET pages, follow these guidelines:
+
+## Task
+
+You'll update 4 articles. For .NET 10, you update these:
+
+- https://github.com/dotnet/docs/blob/main/docs/core/whats-new/dotnet-10/overview.md
+- https://github.com/dotnet/docs/blob/main/docs/core/whats-new/dotnet-10/runtime.md
+- https://github.com/dotnet/docs/blob/main/docs/core/whats-new/dotnet-10/libraries.md
+- https://github.com/dotnet/docs/blob/main/docs/core/whats-new/dotnet-10/sdk.md
+
+For other releases, replace "dotnet-10" in the preceding paths with the correct release. For example, use "dotnet-11" for the ".NET 11" releases.
+
+## Source material
+
+To learn what's new in the targeted release, use the corresponding release notes in the [dotnet core](https://github.com/dotnet/core) repository. The release notes will be in a subfolder of the "release-notes" folder.
+
+For production releases, the path is `<major-release>/<release-number>`, where:
+
+- `<major-release>` is the release number. For example, `8.0`, `9.0` or `10.0`.
+- `<minor-release>` is the three part release number. For example, `8.0.3`, `9.0.6` or `10.0.0`.
+
+For preview releases, the path is `<major-release>/preview/preview<n>` where:
+
+- `<major-release>` is the release number. For example, `8.0`, `9.0` or `10.0`.
+- `n` is the preview number. For example, `1`, `3`, or `6`.
+
+The primary release notes are in the `README.MD` file in that folder.  That file contains links to other release notes for components of .NET: libraries, runtime, SDK, languages, and so on. Use all that information for source.
+
+## Updates for each file
+
+- Each file should have its `ms.date` metadata field updated to match the date you're assigned the issue.
+- Ensure each file has the `ai-usage: ai-assisted` metadata field added.
+- Update phrasing on the latest update to reference the current release (preview, GA, or service release). Individual features shouldn't reference a given preview release, but the article should make it clear which was the last preview.
+- Search this repository for articles that have been recently updated pertaining to new features. Add links to those as you write about that feature. Or, add applicable information from the release notes into existing feature articles where it makes sense.
+- For the runtime and libraries articles, include extensive examples as well as links to recently updated articles related to the new feature. The examples should be at least as thorough as the examples from the source release notes.
+- Where applicable, the SDK article should include the samples.
+- The overview article generally doesn't include examples. Its purpose is to direct readers to more detailed information in other articles.
+- All APIs should be referenced using an `xref` style link, at least on first mention.
+- All links to article in the `dotnet/docs` repository should be file relative.
+- Spell out acronyms on first use in each file.
+- In general, don't mention specific contributors or pull requests to the product repos.
+
+Next, create a pull request. In the description, include the text "Fixes #\<issue-number>", where "issue-number" is the GitHub issue number.
diff --git a/.github/workflows/scorecards.yml b/.github/workflows/scorecards.yml
@@ -71,6 +71,6 @@ jobs:
 
       # Upload the results to GitHub's code scanning dashboard.
       - name: "Upload to code-scanning"
-        uses: github/codeql-action/upload-sarif@181d5eefc20863364f96762470ba6f862bdef56b # v3.29.2
+        uses: github/codeql-action/upload-sarif@d6bbdef45e766d081b84a2def353b0055f728d3e # v3.29.3
         with:
           sarif_file: results.sarif
diff --git a/docs/ai/how-to/snippets/content-filtering/AIContentFiltering.csproj b/docs/ai/how-to/snippets/content-filtering/AIContentFiltering.csproj
@@ -8,9 +8,9 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Azure.AI.OpenAI" />
+    <PackageReference Include="Azure.AI.OpenAI" Version="2.1.0" />
     <PackageReference Include="Azure.Identity" Version="1.14.2" />
-    <PackageReference Include="Microsoft.Extensions.AI" Version="9.7.0" />
+    <PackageReference Include="Microsoft.Extensions.AI" Version="9.7.1" />
     <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="9.4.0-preview.1.25207.5" />
   </ItemGroup>
 

diff --git a/docs/ai/quickstarts/snippets/evaluate-ai-responses/TestAI.csproj b/docs/ai/quickstarts/snippets/evaluate-ai-responses/TestAI.csproj
@@ -11,7 +11,7 @@
   <ItemGroup>
     <PackageReference Include="Azure.AI.OpenAI" Version="2.1.0" />
     <PackageReference Include="Azure.Identity" Version="1.14.2" />
-    <PackageReference Include="Microsoft.Extensions.AI.Abstractions" Version="9.7.0" />
+    <PackageReference Include="Microsoft.Extensions.AI.Abstractions" Version="9.7.1" />
     <PackageReference Include="Microsoft.Extensions.AI.Evaluation" Version="9.7.0" />
     <PackageReference Include="Microsoft.Extensions.AI.Evaluation.Quality" Version="9.7.0" />
     <PackageReference Include="Microsoft.Extensions.AI.OpenAI" Version="9.4.0-preview.1.25207.5" />

diff --git a/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.AddMessages/ConsoleAI.AddMessages.csproj b/docs/ai/snippets/microsoft-extensions-ai/ConsoleAI.AddMessages/ConsoleAI.AddMessages.csproj
@@ -8,7 +8,7 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="OllamaSharp" Version="5.2.10" />
+    <PackageReference Include="OllamaSharp" Version="5.3.1" />
   </ItemGroup>
 
   <ItemGroup>

diff --git a/...ft-extensions-ai/ConsoleAI.CustomEmbeddingsMiddle/ConsoleAI.CustomEmbeddingsMiddle.csproj b/...ft-extensions-ai/ConsoleAI.CustomEmbeddingsMiddle/ConsoleAI.CustomEmbeddingsMiddle.csproj
@@ -9,7 +9,7 @@
 
   <ItemGroup>
     <PackageReference Include="Microsoft.Extensions.Caching.Memory" Version="10.0.0-preview.6.25358.103" />
-    <PackageReference Include="OllamaSharp" Version="5.2.10" />
+    <PackageReference Include="OllamaSharp" Version="5.3.1" />
     <PackageReference Include="OpenTelemetry.Exporter.Console" Version="1.12.0" />
     <ProjectReference Include="..\AI.Shared\AI.Shared.csproj" />
   </ItemGroup>

diff --git a/...icrosoft-extensions-ai/ConsoleAI.DependencyInjection/ConsoleAI.DependencyInjection.csproj b/...icrosoft-extensions-ai/ConsoleAI.DependencyInjection/ConsoleAI.DependencyInjection.csproj
@@ -8,7 +8,7 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="OllamaSharp" Version="5.2.10" />
+    <PackageReference Include="OllamaSharp" Version="5.3.1" />
     <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.0-preview.6.25358.103" />
     <PackageReference Include="Microsoft.Extensions.Caching.Memory" Version="10.0.0-preview.6.25358.103" />
     <ProjectReference Include="..\AI.Shared\AI.Shared.csproj" />

diff --git a/docs/architecture/cloud-native/candidate-apps.md b/docs/architecture/cloud-native/candidate-apps.md
@@ -16,13 +16,9 @@ Applying cost/benefit analysis, there's a good chance some wouldn't support the
 What type of application might be a candidate for cloud native?
 
 - Strategic enterprise systems that need to constantly evolve business capabilities/features
-
 - An application that requires a high release velocity - with high confidence
-
 - A system where individual features must release *without* a full redeployment of the entire system
-
 - An application developed by teams with expertise in different technology stacks
-
 - An application with components that must scale independently
 
 Smaller, less impactful line-of-business applications might fare well with a simple monolithic architecture hosted in a Cloud PaaS environment.
@@ -70,29 +66,17 @@ With the introduction behind, we now dive into a much more detailed look at clou
 ### References
 
 - [Cloud Native Computing Foundation](https://www.cncf.io/)
-
 - [.NET Microservices: Architecture for Containerized .NET applications](https://dotnet.microsoft.com/download/thank-you/microservices-architecture-ebook)
-
 - [Microsoft Azure Well-Architected Framework](/azure/architecture/framework/)
-
 - [Modernize existing .NET applications with Azure cloud and Windows Containers](https://dotnet.microsoft.com/download/thank-you/modernizing-existing-net-apps-ebook)
-
 - [Cloud Native Patterns by Cornelia Davis](https://www.manning.com/books/cloud-native-patterns)
-
 - [Cloud native applications: Ship faster, reduce risk, and grow your business](https://tanzu.vmware.com/cloud-native)
-
 - [Dapr documents](https://dapr.io/)
-
 - [Beyond the Twelve-Factor Application](https://content.pivotal.io/blog/beyond-the-twelve-factor-app)
-
 - [What is Infrastructure as Code](/devops/deliver/what-is-infrastructure-as-code)
-
 - [Uber Engineering's Micro Deploy: Deploying Daily with Confidence](https://www.uber.com/blog/micro-deploy-code/)
-
 - [How Netflix Deploys Code](https://www.infoq.com/news/2013/06/netflix/)
 
-- [Overload Control for Scaling WeChat Microservices](https://www.cs.columbia.edu/~ruigu/papers/socc18-final100.pdf)
-
 >[!div class="step-by-step"]
 >[Previous](definition.md)
 >[Next](introduce-eshoponcontainers-reference-app.md)
diff --git a/docs/architecture/cloud-native/definition.md b/docs/architecture/cloud-native/definition.md
@@ -27,11 +27,11 @@ At the same time, business systems have also become increasingly complex with us
 
 Here are some companies who have implemented cloud-native techniques. Think about the speed, agility, and scalability they've achieved.
 
-| Company | Experience |
-| :-------- | :-------- |
-| [Netflix](https://www.infoq.com/news/2013/06/netflix/) | Has 600+ services in production. Deploys 100 times per day. |
-| [Uber](https://www.uber.com/blog/micro-deploy-code/) | Has 1,000+ services in production. Deploys several thousand times each week. |
-| [WeChat](https://www.cs.columbia.edu/~ruigu/papers/socc18-final100.pdf) | Has 3,000+ services in production. Deploys 1,000 times a day. |
+| Company                                                | Experience                                                    |
+|:-------------------------------------------------------|:--------------------------------------------------------------|
+| [Netflix](https://www.infoq.com/news/2013/06/netflix/) | Has 600+ services in production. Deploys 100 times per day.   |
+| [Uber](https://www.uber.com/blog/micro-deploy-code/)   | Has 1,000+ services in production. Deploys several thousand times each week. |
+| WeChat                                                 | Has 3,000+ services in production. Deploys 1,000 times a day. |
 
 As you can see, Netflix, Uber, and, WeChat expose cloud-native systems that consist of many independent services. This architectural style enables them to rapidly respond to market conditions. They instantaneously update small areas of a live, complex application, without a full redeployment. They individually scale services as needed.
 

diff --git a/docs/azure/migration/appmod/overview.md b/docs/azure/migration/appmod/overview.md
@@ -29,7 +29,7 @@ App Modernization for .NET is provided as a Visual Studio extension and relies o
 
 For a complete walkthrough of setting up and using GitHub Copilot app modernization for .NET, see [Quickstart: Assessing an application and applying code changes](quickstart.md).
 
-## Key Concepts
+## Key concepts
 
 GitHub Copilot app modernization for .NET supports end-to-end migration to Azure, including assessment, planning, code remediation, build fixes, and unit test fixes. It uses GitHub Copilot AI capabilities to help you migrate and run your applications on Azure with confidence, accelerating the entire modernization lifecycle.
 
@@ -45,33 +45,33 @@ When code changes are needed, the tool guides you through remediation using pred
 
 For more information, see [Predefined tasks](predefined-tasks.md).
 
-## Common Use Cases
+## Common use cases
 
 App Modernization for .NET (Preview) supports the following scenarios:
 
 - **Assessment of modernization issue**  
 
     Evaluates your application's readiness for Azure migration in Visual Studio, powered by [AppCAT for .NET](../appcat/install.md).
 
-![Assessment](media/overview_assessment.png)
+    ![Assessment](media/overview_assessment.png)
 
 - **Solution recommendations**  
 
     Recommends target Azure services for your application's resource dependencies, tailored to each category of assessed issues.
 
-![Solution](media/overview_solution.png)
+    ![Solution](media/overview_solution.png)
 
 - **Code remediation for common issues**
 
     Accelerates code changes for [common modernization issues](predefined-tasks.md) by applying predefined tasks that represent expert best practices.
 
-![Apply Task](media/overview_remediation.png)
+    ![Apply Task](media/overview_remediation.png)
 
 - **Automatic fixes for compilation errors:**  
 
     Automatically discovers and fixes compilation errors introduced by code changes.
 
-## Feedback and Privacy
+## Feedback and privacy
 
 - **Feedback:** We value your feedback—share [your thoughts here](https://aka.ms/AM4DFeedback) to help us improve the product.
 - **License:** This extension is licensed under the [GitHub Copilot Product Specific Terms](https://github.com/customer-terms/github-copilot-product-specific-terms).

diff --git a/docs/azure/migration/appmod/quickstart.md b/docs/azure/migration/appmod/quickstart.md
@@ -8,7 +8,7 @@ author: alexwolfmsft
 ms.author: alexwolf
 ---
 
-# Quickstart: Assess and Migrate a .NET Project with GitHub Copilot app modernization for .NET (Preview)
+# Quickstart: Assess and migrate a .NET Project with GitHub Copilot app modernization for .NET (Preview)
 
 In this quickstart, you assess and migrate a .NET project using [GitHub Copilot app modernization for .NET (Preview)](https://marketplace.visualstudio.com/items?itemName=vscjava.appmod-dotnet). You complete the following tasks:
 
@@ -33,7 +33,7 @@ GitHub Copilot is a dependency of the App Modernization Extension and experience
 
 For more information, see [Set up GitHub Copilot in Visual Studio](/visualstudio/ide/visual-studio-github-copilot-install-and-states?view=vs-2022).
 
-## Install the GitHub Copilot App Modernization Extension
+## Install the GitHub Copilot app modernization extension
 
 To complete the steps ahead, you need to install the GitHub Copilot app modernization for .NET (Preview) Visual Studio extension.
 

diff --git a/docs/azure/migration/appmod/sample.md b/docs/azure/migration/appmod/sample.md
@@ -8,11 +8,11 @@ author: alexwolfmsft
 ms.author: alexwolf
 ---
 
-# Contoso University Migration Sample
+# Contoso University migration sample
 
 The [Contoso University sample web app](https://github.com/Azure-Samples/dotnet-migration-copilot-samples/tree/main/ContosoUniversity) provides an example project you can experiment with using GitHub Copilot app modernization for .NET (Preview). For more information and step-by-step instructions, see the [quickstart guide](quickstart.md).
 
-## Scenario Overview
+## Scenario overview
 
 Contoso University is a fictional university management system originally built with .NET Framework 4.8. The application includes features such as:
 
@@ -37,6 +37,6 @@ Using App Modernization for .NET (Preview), you can update the sample to use mod
 
 This migration illustrates how to transform a legacy, on-premises application into a scalable and maintainable cloud-native solution using GitHub Copilot and Azure services.
 
-## Learn More
+## Learn more
 
 - [Quickstart: Assess and migrate a .NET project using GitHub Copilot app modernization for .NET (Preview)](quickstart.md)
diff --git a/docs/azure/sdk/snippets/aspnetcore-guidance/BlazorSample/BlazorSample.csproj b/docs/azure/sdk/snippets/aspnetcore-guidance/BlazorSample/BlazorSample.csproj
@@ -9,7 +9,7 @@
   <ItemGroup>
     <PackageReference Include="Azure.Messaging.ServiceBus" Version="7.20.1" />
 	  <PackageReference Include="Azure.Security.KeyVault.Secrets" Version="4.8.0" />
-	  <PackageReference Include="Azure.Storage.Blobs" Version="12.24.1" />
+	  <PackageReference Include="Azure.Storage.Blobs" Version="12.25.0" />
 	  <PackageReference Include="Microsoft.Extensions.Azure" Version="1.12.0" />
   </ItemGroup>
 

diff --git a/docs/azure/sdk/snippets/unit-testing/UnitTestingSampleApp.csproj b/docs/azure/sdk/snippets/unit-testing/UnitTestingSampleApp.csproj
@@ -16,7 +16,7 @@
     <PackageReference Include="Moq" Version="[4.20.72]" /> <!-- Context: https://github.com/Azure/azure-sdk-for-net/issues/38111 -->
     <PackageReference Include="NSubstitute" Version="5.3.0" />
     <PackageReference Include="xunit" Version="2.9.3" />
-    <PackageReference Include="xunit.runner.visualstudio" Version="3.1.2">
+    <PackageReference Include="xunit.runner.visualstudio" Version="3.1.3">
       <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
       <PrivateAssets>all</PrivateAssets>
     </PackageReference>

diff --git a/docs/core/diagnostics/debug-memory-leak.md b/docs/core/diagnostics/debug-memory-leak.md
@@ -56,6 +56,13 @@ The output should be similar to:
 4807 DiagnosticScena /home/user/git/samples/core/diagnostics/DiagnosticScenarios/bin/Debug/netcoreapp3.0/DiagnosticScenarios
 ```
 
+> [!NOTE]
+> If the previous command doesn't work or isn't found, you likely need to install the `dotnet-counters` tool first. Use the following command:
+>
+> ```console
+> dotnet tool install --global dotnet-counters
+> ```
+
 Now, check managed memory usage with the [dotnet-counters](dotnet-counters.md) tool. The `--refresh-interval` specifies the number of seconds between refreshes:
 
 ```console