commit c81e2b6e61147b7de2f01f6f7b3c13d42aa2e886
parent 4d6d9e1a9aecf1ce2dc66eb806bf9dbdea8a9489
Author: Kaleb Luedtke <trenlymc@gmail.com>
Date: Wed, 12 Feb 2025 19:47:41 -0600
Update YamlDotNet to Latest (#5191)
I know that NuGet packages are typically not updated unless there are
CVEs, important bug fixes, or other specific need to. However, when
reviewing the list of NuGet packages installed, I saw that YamlDotNet
was several versions out of date. This package directly affects the
parsing of manifests within WinGet and the associated utilities. Given
that, I thought it best to update it, especially given the fact that
1.10 is preparing to go through the release cycle, which would give
these changes enough time to be tested in the 1.11 previews and testing
cycles.
This change only directly updates the top-level project -
`WinGetUtilInterop`. I'm expecting that all the other projects which
have this NuGet package as a transient dependency will pick up this new
version, as all of them have a Project Dependency on
`WinGetUtilInterop`.
The projects which consume this change -
### Top-Level
* WinGetUtilInterop
### Transitive
* AppInstallerCLIE2ETests
* Tool\IndexCreationTool
* Tool\LocalhostWebServer
* WinGetSourceCreator
* WinGetUtilInterop.UnitTests
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/WinGetUtilInterop/WinGetUtilInterop.csproj b/src/WinGetUtilInterop/WinGetUtilInterop.csproj
@@ -11,7 +11,7 @@
</ItemGroup>
<ItemGroup>
- <PackageReference Include="YamlDotNet" Version="8.1.2" />
+ <PackageReference Include="YamlDotNet" Version="16.3.0" />
<PackageReference Include="StyleCop.Analyzers" Version="1.1.118">
<PrivateAssets>all</PrivateAssets>
</PackageReference>
