Bump Swashbuckle.AspNetCore.Filters from 5.0.2 to 6.1.0 in /sources/ReleaseServer/ReleaseServer.WebApi.Test

[dependabot-preview]

Bumps Swashbuckle.AspNetCore.Filters from 5.0.2 to 6.1.0.

Changelog

Sourced from Swashbuckle.AspNetCore.Filters's changelog.

[6.1.0]

Added

• Issue #171 support auto example for ProducesDefaultResponseType.

[6.0.1] 2020-10-16

Fixed

• PR #161 restore NewtonsoftJson dependency.

[6.0.0] 2020-09-27

Fixed

• Issue #132 Support [System.Text.JsonPropertyNameAttribute]. This is a breaking change which rewrote how the examples are generated. Instead of explicitly using Newtonsoft's JsonConvert.SerializeObject(), I now use whichever JSON serializer is registered with the MVC pipeline, i.e. during services.AddControllers().

Removed

• contractResolver and jsonConverter parameters from [SwaggerRequestExampleAttribute].
• contractResolver and jsonConverter parameters from [SwaggerResponseExampleAttribute].
• Microsoft.AspNetCore.Mvc.NewtonsoftJson dependency.

Changed

• If you are using options.IgnoreObsoleteProperties(); and you want your Examples to not have the obsolete properties, then you will need to register my custom Newtonsoft ExcludeObsoletePropertiesResolver, e.g.

services.AddControllers()
    .AddNewtonsoftJson(opt =>
    {
        opt.SerializerSettings.ContractResolver = new ExcludeObsoletePropertiesResolver(opt.SerializerSettings.ContractResolver);

[5.1.2] 2020-06-25

Fixed

• #154 Upgrade to Microsoft.OpenApi 1.2.2 because 1.2.0 had breaking changes

Added

• Add services.AddSwaggerExamples() extension method to allow examples without automatic annotation

[5.1.1] 2020-04-12

Fixed

• #115 Added workaround for request examples when SerializeAsV2 = true
• #148 AddSwaggerExamplesFromAssemblies method does not scan for IMultipleExamplesProvider implementations

[5.1.0] 2020-04-05

Added

• PR #147 add support for multiple request and response examples. Thanks to @tomkludy and @pozy for the contribution.

Commits

• See full diff 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)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .github/dependabot.yml file in this repo:

• Update frequency
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #32.