Bump NJsonSchema from 11.6.0 to 11.6.1

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Pinned NJsonSchema at 11.6.1.

Release notes

Sourced from NJsonSchema's releases.

11.6.1

[!IMPORTANT]
v11.6.0 should not be used — it introduced a regression that caused required T? / [JsonRequired] T? properties to incorrectly lose their nullability and gain a spurious MinLength=1 on strings. Please upgrade directly from v11.5.x to v11.6.1.

Corrections to v11.6.0

v11.6.0 added support for the C# 11 required keyword and [JsonRequired] in schema generation (#​1908), but folded them into the same bucket as DataAnnotations [Required] — which conflated three distinct concepts:

• Presence (belongs in schema's required array): required keyword, [JsonRequired], [Required], [DataMember(IsRequired=true)], Newtonsoft Required.Always/AllowNull
• Non-null value (suppresses nullable): [Required] only (plus Newtonsoft Required.Always/DisallowNull for runtime correctness)
• Non-empty string (MinLength=1 on strings): [Required] only (unless AllowEmptyStrings=true)

v11.6.1 (#​1919) restores the correct separation. The required keyword and [JsonRequired] are now presence-only markers — they add the property to the schema's required array without suppressing nullability or adding MinLength=1.

Behavioral deltas vs v11.6.0 (all restoring correctness)

C# declaration	v11.6.0 (broken)	v11.6.1
required string?	nullable: false, MinLength: 1 ❌	nullable: true, no MinLength ✅
required string	MinLength: 1 ❌	no MinLength ✅
[JsonRequired] string?	nullable: false, MinLength: 1 ❌	nullable: true, no MinLength ✅
[JsonRequired] string	MinLength: 1 ❌	no MinLength ✅

[Required], [JsonProperty(Required=*)], and [DataMember(IsRequired=true)] semantics are unchanged across v11.5.x / v11.6.0 / v11.6.1.

Downstream impact

The v11.6.0 regression surfaced in NSwag as NSwag#​5359: TypeScript clients generated from required T? DTO properties silently lost their | null, removing null-safety for fields the server can legitimately return as null. v11.6.1 fixes this. A matching NSwag release is required to pick up the fix.

What's Changed

• required string? incorrectly loses nullable and gains MinLength=1 by @​inghamc in required string? incorrectly loses nullable and gains MinLength=1 RicoSuter/NJsonSchema#1919

New Contributors

• @​inghamc made their first contribution in required string? incorrectly loses nullable and gains MinLength=1 RicoSuter/NJsonSchema#1919

Full Changelog: RicoSuter/NJsonSchema@v11.6.0...v11.6.1

Commits viewable in compare view.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud