ci: keep Dependabot off action majors and off the build-only NU1903

.github/dependabot.yml

@@ -2,13 +2,23 @@
 #
 # github-actions keeps the SHA-pinned actions in the workflows current — a pin without an update
 # path just ages. Weekly, one grouped PR, so a security release in an action is not waiting a month.
+# Majors are excluded: this is the publish path, and release.yml documents why upload-artifact
+# stays on v6 and download-artifact on v7 (v8 stops auto-unzipping, which would break the push
+# step). A major is a deliberate change with a test behind it, not a Monday PR.
 #
 # nuget covers the test project only. The shipping projects under src/ are deliberately excluded:
 # their EF Core and provider references are floors chosen on purpose (see the csproj comments) —
 # raising one raises every consumer's minimum, which is a release decision, not a dependency
 # update. The test project's EF Core and provider references track those floors for the same
 # reason and are ignored here; bump them by hand together with the floor. Security advisories
 # still surface for everything through Dependabot security updates and NuGetAudit at build time.
+#
+# The src/ entry exists only so that security updates there honour its ignore list: with
+# open-pull-requests-limit 0 it proposes no version updates at all. System.Security.Cryptography.Xml
+# is reached only through Microsoft.EntityFrameworkCore.Design (PrivateAssets=all) — consumers
+# never receive it, NU1903 is kept as a warning for that reason (Directory.Build.props), and
+# Dependabot's remedy is a *direct* reference, which would ship the package to every consumer to
+# silence a warning that only ever concerned build machines.
 version: 2
 updates:
   - package-ecosystem: github-actions
@@ -18,6 +28,9 @@ updates:
     groups:
       actions:
         patterns: [ "*" ]
+    ignore:
+      - dependency-name: "*"
+        update-types: [ "version-update:semver-major" ]
 
   - package-ecosystem: nuget
     directory: /test/EFCore.ComplexIndexes.Tests
@@ -29,3 +42,12 @@ updates:
     ignore:
       - dependency-name: "Microsoft.EntityFrameworkCore*"
       - dependency-name: "Npgsql.EntityFrameworkCore.PostgreSQL*"
+
+  - package-ecosystem: nuget
+    directories:
+      - /src/*
+    schedule:
+      interval: monthly
+    open-pull-requests-limit: 0
+    ignore:
+      - dependency-name: "System.Security.Cryptography.Xml"

CLAUDE.md

@@ -36,9 +36,13 @@ the build reports green.
 suite (Docker), then a pack job whose value is partly that packing *is* a check — a package
 declaring `PackageReadmeFile` without packing the file fails with NU5019. Everything runs on
 ubuntu-latest. Actions in both workflows are pinned to commit SHAs with the tag in a trailing
-comment; `.github/dependabot.yml` keeps those pins current (weekly, grouped) and covers the test
-project's NuGet references monthly — not `src/`, whose EF Core and provider floors are release
-decisions.
+comment; `.github/dependabot.yml` keeps those pins current (weekly, grouped, minors and patches
+only — majors on the publish path are deliberate, see the artifact-action comments in
+`release.yml`) and covers the test project's NuGet references monthly — not `src/`, whose EF Core
+and provider floors are release decisions. A `src/` entry with no version updates exists only so
+security updates there honour its ignore list: Dependabot's fix for the build-only NU1903 would be
+a *direct* `System.Security.Cryptography.Xml` reference, shipping to consumers a package they never
+had.
 
 The unit job used to fan out across ubuntu/windows/macos for the repository-convention tests, which
 do real path work. Dropped in favour of reacting if it ever bites: **no shipped code touches the