Bump Newtonsoft.Json from 13.0.1 to 13.0.2

[dependabot]

Bumps Newtonsoft.Json from 13.0.1 to 13.0.2.

Release notes

Sourced from Newtonsoft.Json's releases.

13.0.2

• New feature - Add support for DateOnly and TimeOnly
• New feature - Add UnixDateTimeConverter.AllowPreEpoch property
• New feature - Add copy constructor to JsonSerializerSettings
• New feature - Add JsonCloneSettings to disable copy annotations
• Change - Add nullable annotation to JToken.ToObject(Type, JsonSerializer)
• Change - Reduced allocations by reusing boxed values
• Fix - Fixed MaxDepth when used with ToObject inside of a JsonConverter
• Fix - Fixed deserializing mismatched JToken types in properties
• Fix - Fixed merging enumerable content and validate content
• Fix - Fixed using $type with arrays of more than two dimensions
• Fix - Fixed rare race condition in name table when deserializing on device with ARM processors
• Fix - Fixed deserializing via constructor with ignored base type properties
• Fix - Fixed MaxDepth not being used with ISerializable deserialization

Commits

• 4fba53a Remove prerelease for 13.0.2
• b15df4b Add missing headers
• 789bfd3 Update to 13.0.2-beta3
• b13717a Add JsonCloneSettings to disable copy annotations (#2757)
• d0a328e Fix MaxDepth not being used with ISerializable deserialization (#2736)
• aae9284 Update SDK
• bd98970 Update to 13.0.2-beta2
• 4dc9af6 Add roll forward to global.json (#2726)
• b8f4ef0 Fixing misspelling (#2698)
• cb9eed9 Fix deserializing via constructor with ignored base type properties (#2711)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.csproj : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[ghost]

🎉v7.4.0-preview.1 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes