From 32779798d03202215da62313d9ea299846c35b84 Mon Sep 17 00:00:00 2001
From: nxships <2096086+nxships@users.noreply.github.com>
Date: Tue, 11 Aug 2026 13:42:15 +0200
Subject: [PATCH] chore(deps): raise every NexusKit floor to 0.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

All five now name the release that is actually on the feed. Keeping the other
four at 0.5.0 while Sync sat at 0.5.1 invited the mix that NU1603 reports and
TreatWarningsAsErrors turns into a failed build — and it left the impression
that the framework packages are versioned independently, which they are not:
NexusKit publishes them together.
---
 Directory.Packages.props | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Directory.Packages.props b/Directory.Packages.props
index 24dbb38..014c974 100644
--- a/Directory.Packages.props
+++ b/Directory.Packages.props
@@ -28,10 +28,10 @@
     <!-- NexusKit framework. Open-ended ranges on purpose: the local workspace
          swaps these for ProjectReferences, and CI takes the newest published
          package. Do not let a bump turn them into exact pins. -->
-    <PackageVersion Include="NexusKit.Core" Version="[0.5.0,)" />
-    <PackageVersion Include="NexusKit.GameData" Version="[0.5.0,)" />
-    <PackageVersion Include="NexusKit.Persistence" Version="[0.5.0,)" />
-    <PackageVersion Include="NexusKit.Ui" Version="[0.5.0,)" />
+    <PackageVersion Include="NexusKit.Core" Version="[0.5.1,)" />
+    <PackageVersion Include="NexusKit.GameData" Version="[0.5.1,)" />
+    <PackageVersion Include="NexusKit.Persistence" Version="[0.5.1,)" />
+    <PackageVersion Include="NexusKit.Ui" Version="[0.5.1,)" />
     <!-- 0.5.1 rather than 0.5.0, because that is the release the library first appeared in.
          A floor naming a version that never contained it restores fine but raises NU1603 for
          the substitution, and TreatWarningsAsErrors turns that into a failed build.