Upgrade HTTP JSON outside legacy Blazor builds

Proprietary

Upgrade System.Net.Http.Json using the existing NuGet version/property/central planner, except when the captured build declares the legacy Blazor WebAssembly.Build package. Preserve the entire captured package policy in that case, including shared versions. The old Mono linker can fail on newer JSON assemblies. This does not migrate Blazor build tools or establish general runtime compatibility for other consumers.

OpenRewrite.Recipes.CSharp.Migration.Dotnet.NetFrameworkToDotNet.UpgradeHttpJsonOutsideLegacyBlazor

Required

NewVersionString

Version selected for System.Net.Http.Json; resolved by the existing NuGet planner.

Optional

RegenerateMarkerBoolean

DefaultTrueFalse

Refresh native metadata after the edit. Composites can defer to their final attestation.

mod run . --recipe=OpenRewrite.Recipes.CSharp.Migration.Dotnet.NetFrameworkToDotNet.UpgradeHttpJsonOutsideLegacyBlazor \
  -P NewVersion=10.0.x

Install it once, then run it on every repository under the current directory. New to the Moderne CLI? Set it up.