Skip to content

Supersede Dependabot #2: Newtonsoft.Json 13 no longer applies - #15

Merged
hippi345 merged 1 commit into
masterfrom
cursor/newtonsoft-json-13-22ef
Oct 27, 2026
Merged

hippi345 merged 1 commit into
masterfrom
cursor/newtonsoft-json-13-22ef

Conversation

@hippi345

@hippi345 hippi345 commented Oct 26, 2026 •

Copy link
Copy Markdown
Owner

Summary

This pull request supersedes #2 (Bump Newtonsoft.Json from 10.0.2 to 13.0.2 in /AzCopyAndDelete/AzCopyAndDelete).

#2 updates AzCopyAndDelete/AzCopyAndDelete/packages.config and conflicts with master. That manifest, the committed packages/Newtonsoft.Json.10.0.2 tree, and the .NET Framework project that referenced it were removed when the app moved to SDK-style projects on .NET 8 and Azure.Storage.Blobs. Application code never called Newtonsoft.Json directly; the package was pulled in by the legacy Storage SDK.

The current restore graph has no Newtonsoft.Json reference (direct or transitive). dotnet list AzCopyAndDelete.sln package --vulnerable --include-transitive reports no vulnerable packages, so there is no 13.0.2 package bump to apply on this tree. #2 is left open and is not merged.

NuGet updates in Dependabot are now grouped (groups.nuget with pattern *) so later package bumps open as one pull request instead of one PR per package.

Test plan

  • dotnet format AzCopyAndDelete.sln --verify-no-changes
  • dotnet build AzCopyAndDelete.sln -c Release
  • dotnet test AzCopyAndDelete.sln -c Release (16 passed)
  • dotnet list package graph contains no Newtonsoft.Json
  • GitHub Actions CI on this pull request
Open in Web Open in Cursor 

Newtonsoft.Json 10.0.2 existed only in the removed packages.config project, so the 13.0.2 bump cannot be applied on the SDK-style tree. Group NuGet updates for the current solution.
@hippi345
hippi345 merged commit 59f40bc into master Oct 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant