Bump GraphQL.Server.Transports.AspNetCore.SystemTextJson from 5.1.1 to 5.2.2

[dependabot]

Bumps GraphQL.Server.Transports.AspNetCore.SystemTextJson from 5.1.1 to 5.2.2.

Release notes

Sourced from GraphQL.Server.Transports.AspNetCore.SystemTextJson's releases.

Version 5.2.2

This updates the NuGet package dependency versions to prevent accidental usage of GraphQL.NET Server 5.x components with GraphQL.NET Server 6.x components. It contains no code changes.

Version 5.2.1

This release contains no functional changes but merely ensures that only compatible versions of GraphQL.NET (from 4.6.1 up to but not including 5.0.0) are used with this package.

What's Changed

• Restrict acceptable GraphQL.NET versions to v4 by @​Shane32 in graphql-dotnet/server#752

Full Changelog: graphql-dotnet/server@5.2.0...5.2.1

Version 5.2.0

This is a cumulative release before v6. It contains some improvements and bugfixes.

What's Changed

New features

• Provide service provider to subscription execution by @​Shane32 in graphql-dotnet/server#691
• Make WebSocketConnection.Connect virtual by @​Shane32 in graphql-dotnet/server#674
• Mark old IGraphQLBuilder extension methods obsolete and create new ones by @​Shane32 in graphql-dotnet/server#602
• Deserialization updates by @​Shane32 in graphql-dotnet/server#569
• Upgrade GraphiQL to 1.5.1 by @​boulc in graphql-dotnet/server#649

CI improvements

• NET6 support, embedded readme by @​sungam3r in graphql-dotnet/server#665
• Multi-TFM approvals by @​sungam3r in graphql-dotnet/server#675
• Auto approve API by @​sungam3r in graphql-dotnet/server#689
• Configure codecov to post fresh coverage comment by @​sungam3r in graphql-dotnet/server#664
• Add tests for properties marked with attribute by @​sungam3r in graphql-dotnet/server#681

Bugfixes

• Patch memory leak with subscriptions when client abruptly terminates by @​Shane32 in graphql-dotnet/server#668
• Dispose of WebSocket when done with it by @​Shane32 in graphql-dotnet/server#671
• Better Dispose pattern for WebSocketConnection by @​Shane32 in graphql-dotnet/server#673
• Dispose all subscriptions when connection broken by @​Shane32 in graphql-dotnet/server#677

New Contributors

• @​boulc made their first contribution in graphql-dotnet/server#649

Full Changelog: graphql-dotnet/server@5.1.1...5.2.0

Commits

• 06f096a Update package versioning
• f4a92ba Restrict acceptable GraphQL.NET versions to v4 (#752)
• 22ff03f Bump Moq from 4.16.1 to 4.17.2 (#747)
• f84d492 Bump actions/checkout from 2 to 3 (#742)
• 1e8a018 Bump actions/setup-dotnet from 1 to 2 (#739)
• 2fa6fdc CI changes (#744)
• 1b7d745 Bump actions/labeler from 3 to 4 (#743)
• 5f7b7b2 Bump actions/github-script from 5 to 6 (#723)
• a2672ff Bump coverlet.msbuild from 3.1.1 to 3.1.2 (#720)
• 7503bb1 Bump PublicApiGenerator from 10.2.0 to 10.3.0 (#713)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[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.