From 1b2fbc996dc64590feb495157b8b38332cf59f0e Mon Sep 17 00:00:00 2001 From: Nick Cipollina Date: Tue, 21 Jul 2026 16:17:52 -0400 Subject: [PATCH 1/3] fix: use a publish-safe prerelease bound for version ranges The X.0.0-0 upper bound broke package publish - nuget.org's nuspec validator rejected the literal string as an invalid Version ('The NuGet package contains an invalid .nuspec file... invalid Version: 11.0.0-0'), even though it's valid SemVer2. Switching to X.0.0-preview.0 keeps the same guarantee (numeric dotted identifiers compare numerically, so preview.0 sorts below preview.1, preview.6.*, and any real preview build) while being letter-led like our own lower bounds, which the validator already accepts without complaint. Co-Authored-By: Claude Sonnet 5 --- Directory.Packages.props | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/Directory.Packages.props b/Directory.Packages.props index 5088694..b71f08c 100644 --- a/Directory.Packages.props +++ b/Directory.Packages.props @@ -44,22 +44,22 @@ preview version is pinned to match global.json's SDK pin (11.0.100-preview.6.26359.118) - bump both together. --> - - - - + + + + - - + + - - - - - - + + + + + + - - - - + + + + - - + + - - - - - - + + + + + + + @@ -53,6 +62,20 @@ +