From f538bd7d3ae48676a769a408893963b26026d829 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Thu, 13 Aug 2026 06:09:39 +0000
Subject: [PATCH] Bump Microsoft.Extensions.DependencyInjection.Abstractions
 from 10.0.10 to 10.0.11

---
updated-dependencies:
- dependency-name: Microsoft.Extensions.DependencyInjection.Abstractions
  dependency-version: 10.0.11
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
---
 Directory.Packages.props | 158 +++++++++++++++++++--------------------
 1 file changed, 79 insertions(+), 79 deletions(-)

diff --git a/Directory.Packages.props b/Directory.Packages.props
index e558aba..1c51168 100644
--- a/Directory.Packages.props
+++ b/Directory.Packages.props
@@ -1,79 +1,79 @@
-<Project>
-
-  <!--
-    Central Package Management.
-
-    All NuGet versions are declared here, once. Projects reference packages with
-    <PackageReference Include="..." /> and no Version attribute, which makes version
-    drift between projects impossible.
-
-    Transitive pinning is on, so an indirect dependency can be forced to a specific
-    version from here without taking a direct reference on it. That is how the
-    SQLite security pin below works.
-
-    Edit this file by hand. Running several `dotnet add package` commands in parallel
-    races on it and can truncate it.
-  -->
-
-  <PropertyGroup>
-    <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
-    <CentralPackageTransitivePinningEnabled>true</CentralPackageTransitivePinningEnabled>
-    <!--
-      Treat vulnerable packages as build failures, including transitive ones.
-      This is deliberately strict: Cayrast loads third-party modules and reads
-      untrusted files, so shipping a known-vulnerable dependency is not a warning.
-    -->
-    <NuGetAudit>true</NuGetAudit>
-    <NuGetAuditMode>all</NuGetAuditMode>
-    <NuGetAuditLevel>low</NuGetAuditLevel>
-  </PropertyGroup>
-
-  <ItemGroup Label="Hosting and infrastructure">
-    <PackageVersion Include="Microsoft.Extensions.Hosting" Version="10.0.10" />
-    <PackageVersion Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="10.0.10" />
-    <PackageVersion Include="Microsoft.Extensions.Logging.Abstractions" Version="10.0.10" />
-  </ItemGroup>
-
-  <ItemGroup Label="Logging">
-    <PackageVersion Include="Serilog.Extensions.Hosting" Version="10.0.0" />
-    <PackageVersion Include="Serilog.Sinks.File" Version="7.0.0" />
-  </ItemGroup>
-
-  <ItemGroup Label="UI">
-    <!--
-      Kept aligned with the shipping Evergreen WebView2 Runtime. The SDK only needs
-      to be no newer than the installed runtime; pinning near it avoids calling APIs
-      that are missing on user machines.
-    -->
-    <PackageVersion Include="Microsoft.Web.WebView2" Version="1.0.4129.50" />
-  </ItemGroup>
-
-  <ItemGroup Label="Storage">
-    <PackageVersion Include="Microsoft.Data.Sqlite" Version="10.0.10" />
-    <!--
-      SECURITY PIN — do not remove without re-checking the advisory.
-
-      Microsoft.Data.Sqlite 10.0.10 resolves SQLitePCLRaw.lib.e_sqlite3 2.1.11, which
-      carries a high-severity SQLite vulnerability (GHSA-2m69-gcr7-jv3q). This forces
-      the patched 2.1.12 instead.
-
-      Pinning only lib.e_sqlite3 is deliberate. That package contains just the native
-      SQLite binary and exposes no managed API, so moving it forward cannot break
-      Microsoft.Data.Sqlite's compile-time contract. The managed SQLitePCLRaw packages
-      (core, bundle, provider) have since moved to a 3.0.x line with a different API
-      surface, and dragging those forward under a 2.1.x-compiled consumer would risk a
-      runtime failure to buy nothing extra.
-    -->
-    <PackageVersion Include="SQLitePCLRaw.lib.e_sqlite3" Version="2.1.12" />
-  </ItemGroup>
-
-  <ItemGroup Label="Testing">
-    <PackageVersion Include="Microsoft.NET.Test.Sdk" Version="18.8.1" />
-    <PackageVersion Include="xunit.v3" Version="3.2.2" />
-    <PackageVersion Include="xunit.runner.visualstudio" Version="3.1.5">
-      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
-      <PrivateAssets>all</PrivateAssets>
-    </PackageVersion>
-  </ItemGroup>
-
-</Project>
+<Project>
+
+  <!--
+    Central Package Management.
+
+    All NuGet versions are declared here, once. Projects reference packages with
+    <PackageReference Include="..." /> and no Version attribute, which makes version
+    drift between projects impossible.
+
+    Transitive pinning is on, so an indirect dependency can be forced to a specific
+    version from here without taking a direct reference on it. That is how the
+    SQLite security pin below works.
+
+    Edit this file by hand. Running several `dotnet add package` commands in parallel
+    races on it and can truncate it.
+  -->
+
+  <PropertyGroup>
+    <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
+    <CentralPackageTransitivePinningEnabled>true</CentralPackageTransitivePinningEnabled>
+    <!--
+      Treat vulnerable packages as build failures, including transitive ones.
+      This is deliberately strict: Cayrast loads third-party modules and reads
+      untrusted files, so shipping a known-vulnerable dependency is not a warning.
+    -->
+    <NuGetAudit>true</NuGetAudit>
+    <NuGetAuditMode>all</NuGetAuditMode>
+    <NuGetAuditLevel>low</NuGetAuditLevel>
+  </PropertyGroup>
+
+  <ItemGroup Label="Hosting and infrastructure">
+    <PackageVersion Include="Microsoft.Extensions.Hosting" Version="10.0.10" />
+    <PackageVersion Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="10.0.11" />
+    <PackageVersion Include="Microsoft.Extensions.Logging.Abstractions" Version="10.0.10" />
+  </ItemGroup>
+
+  <ItemGroup Label="Logging">
+    <PackageVersion Include="Serilog.Extensions.Hosting" Version="10.0.0" />
+    <PackageVersion Include="Serilog.Sinks.File" Version="7.0.0" />
+  </ItemGroup>
+
+  <ItemGroup Label="UI">
+    <!--
+      Kept aligned with the shipping Evergreen WebView2 Runtime. The SDK only needs
+      to be no newer than the installed runtime; pinning near it avoids calling APIs
+      that are missing on user machines.
+    -->
+    <PackageVersion Include="Microsoft.Web.WebView2" Version="1.0.4129.50" />
+  </ItemGroup>
+
+  <ItemGroup Label="Storage">
+    <PackageVersion Include="Microsoft.Data.Sqlite" Version="10.0.10" />
+    <!--
+      SECURITY PIN — do not remove without re-checking the advisory.
+
+      Microsoft.Data.Sqlite 10.0.10 resolves SQLitePCLRaw.lib.e_sqlite3 2.1.11, which
+      carries a high-severity SQLite vulnerability (GHSA-2m69-gcr7-jv3q). This forces
+      the patched 2.1.12 instead.
+
+      Pinning only lib.e_sqlite3 is deliberate. That package contains just the native
+      SQLite binary and exposes no managed API, so moving it forward cannot break
+      Microsoft.Data.Sqlite's compile-time contract. The managed SQLitePCLRaw packages
+      (core, bundle, provider) have since moved to a 3.0.x line with a different API
+      surface, and dragging those forward under a 2.1.x-compiled consumer would risk a
+      runtime failure to buy nothing extra.
+    -->
+    <PackageVersion Include="SQLitePCLRaw.lib.e_sqlite3" Version="2.1.12" />
+  </ItemGroup>
+
+  <ItemGroup Label="Testing">
+    <PackageVersion Include="Microsoft.NET.Test.Sdk" Version="18.8.1" />
+    <PackageVersion Include="xunit.v3" Version="3.2.2" />
+    <PackageVersion Include="xunit.runner.visualstudio" Version="3.1.5">
+      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
+      <PrivateAssets>all</PrivateAssets>
+    </PackageVersion>
+  </ItemGroup>
+
+</Project>