Add breaking change documentation for PackageReference version requirement

Co-authored-by: gewarren <[email protected]>

Author: Copilot

docs/core/compatibility/10.0.md

@@ -78,6 +78,7 @@ If you're migrating an app to .NET 10, the breaking changes listed here might af
 | [MSBUILDCUSTOMBUILDEVENTWARNING escape hatch removed](sdk/10.0/custom-build-event-warning.md) | Behavioral change | Preview 1 |
 | [MSBuild custom culture resource handling](sdk/10.0/msbuild-custom-culture.md) | Behavioral change | Preview 1 |
 | [NU1510 is raised for direct references pruned by NuGet](sdk/10.0/nu1510-pruned-references.md) | Source incompatible | Preview 1 |
+| [PackageReference without a version will raise an error](sdk/10.0/nu1015-packagereference-version.md) | Behavioral change | Preview 6 |
 | [HTTP warnings promoted to errors in `dotnet package list` and `dotnet package search`](sdk/10.0/http-warnings-to-errors.md) | Behavioral/source incompatible change | Preview 4 |
 
 ## Windows Forms

docs/core/compatibility/sdk/10.0/nu1015-packagereference-version.md

@@ -0,0 +1,50 @@
+---
+title: "Breaking change - PackageReference without a version will raise an error"
+description: "Learn about the breaking change in .NET 10 where PackageReference without a version raises NU1015 error instead of NU1604 warning."
+ms.date: 12/17/2024
+ai-usage: ai-assisted
+ms.custom: https://github.com/dotnet/docs/issues/46386
+---
+
+# PackageReference without a version will raise an error
+
+Starting in .NET 10, NuGet raises a [`NU1015` error](/nuget/reference/errors-and-warnings/nu1015) when a `PackageReference` item doesn't have a version specified, instead of the previous [`NU1604` warning](/nuget/reference/errors-and-warnings/nu1604).
+
+## Version introduced
+
+.NET 10 Preview 6
+
+## Previous behavior
+
+Previously, NuGet raised a NU1604 warning with the text "Project dependency 'PackageA' does not contain an inclusive lower bound. Include a lower bound in the dependency version to ensure consistent restore results."
+
+## New behavior
+
+NuGet now raises a NU1015 error with the text "The following PackageReference item(s) do not have a version specified: PackageA"
+
+## Type of breaking change
+
+This is a [behavioral change](../../categories.md#behavioral-change).
+
+## Reason for change
+
+The "no lower bound" message was confusing, and it was unclear how to fix the issue. Additionally, NuGet would end up restoring the lowest version for that package, which is rarely what developers want. This change provides clearer and more actionable error messages when the version metadata is missing.
+
+There's no change when using Central Package Management, since by design the PackageReference XML should not have a version in that scenario.
+
+## Recommended action
+
+Add a version to the package reference, for example:
+
+```diff
+- <PackageReference Include="Some.Package" />
++ <PackageReference Include="Some.Package" Version="1.2.3" />
+```
+
+If the lowest package version is desired, then use `Version="0.0.0"`. In this case, NuGet will raise warning NU1603, rather than the previous NU1604.
+
+`SdkAnalysisLevel` can be set to `9.0.300` or lower, and NuGet will revert to the previous warning. However, this will affect all features that gate on SdkAnalysisLevel.
+
+## Affected APIs
+
+None.

docs/core/compatibility/toc.yml

@@ -74,6 +74,8 @@ items:
                 href: sdk/10.0/msbuild-custom-culture.md
               - name: NU1510 is raised for direct references pruned by NuGet
                 href: sdk/10.0/nu1510-pruned-references.md
+              - name: PackageReference without a version will raise an error
+                href: sdk/10.0/nu1015-packagereference-version.md
               - name: HTTP warnings promoted to errors in package list and search
                 href: sdk/10.0/http-warnings-to-errors.md
           - name: Windows Forms