From e20b4dbfab587e0c9753f67b831f57f52845d4a0 Mon Sep 17 00:00:00 2001 From: Miheichev Aleksandr Sergeevich Date: Sat, 22 Aug 2026 02:19:29 +0000 Subject: [PATCH] chore(deps): update CliWrap and TUnit, drop unused test pins (#10005) * chore(deps): update CliWrap and TUnit - CliWrap 3.10.4 -> 3.10.5 - TUnit 1.65.0 -> 1.65.38 - TUnit.Assertions.Should 1.65.0-beta -> 1.65.38-beta TUnit.Assertions.Should is versioned in lockstep with TUnit and published with a -beta suffix. Its 1.65.0-beta package depends on TUnit.Assertions 1.65.0-beta, so it has to move together with TUnit to keep the whole TUnit stack resolved on a single version (TUnit.Assertions 1.65.38 after this change). * chore(deps): drop unused AwesomeAssertions and xunit.v3 pins Since the migration to TUnit (c9e843aa) no project references AwesomeAssertions or xunit.v3 any more, so these two PackageVersion entries no longer pin anything: neither package appears in any project.assets.json, directly or transitively. Verified by restoring, building and publishing the whole solution with and without the two entries: the resolved package graph (769 entries across all projects) and the published output of every CI target - v2rayN win-x64, v2rayN.Desktop win-x64 and linux-x64, AmazTool win-x64, all self-contained - are byte-identical, and ServiceLib.Tests stays at 69/69. --- v2rayN/Directory.Packages.props | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/v2rayN/Directory.Packages.props b/v2rayN/Directory.Packages.props index ecbd8676..4e9f14c8 100644 --- a/v2rayN/Directory.Packages.props +++ b/v2rayN/Directory.Packages.props @@ -9,11 +9,10 @@ - - + @@ -28,10 +27,9 @@ - - + + -