Bump the other-deps group with 2 updates

[dependabot]

Updated NSwag.AspNetCore from 14.7.0 to 14.7.1.

Release notes

Sourced from NSwag.AspNetCore's releases.

14.7.1

[!IMPORTANT]
Upgrade directly from v14.6.3 to v14.7.1 — skip v14.7.0.

v14.7.0 bundled NJsonSchema v11.6.0, which contained a regression that silently dropped nullability on required T? / [JsonRequired] T? DTO properties. The resulting OpenAPI/JSON schema marked those properties as non-nullable, so generated TypeScript and C# clients lost null-safety for fields the server can legitimately return as null (#​5359).

Corrections to v14.7.0

v14.7.1 updates to NJsonSchema v11.6.1, which corrects the handling of the C# required keyword and [JsonRequired]:

• These are now treated as presence markers (the property must be present in the JSON) rather than value constraints.
• Nullability from the declared type (string?, T?) is preserved.
• No spurious MinLength=1 on non-nullable strings.
• DataAnnotations [Required] semantics remain unchanged (still suppresses nullability and adds MinLength=1 to strings by default, matching its runtime behavior).

Observable client changes vs v14.7.0

For public required string[]? OptionList { get; init; } (#​5359):

	TypeScript client	C# client
v14.7.0 (broken)	optionList: string[] ❌	public string[] OptionList ❌
v14.7.1	optionList: string[] | null ✅	public string[]? OptionList ✅

For full details and truth tables across all required / [Required] / [JsonRequired] / [JsonProperty(Required=*)] combinations, see the NJsonSchema v11.6.1 release notes and NJsonSchema #​1919.

What's Changed

• Upgrade to NJsonSchema v11.6.1 (NSwag v14.7.1) by @​RicoSuter in Upgrade to NJsonSchema v11.6.1 (NSwag v14.7.1) RicoSuter/NSwag#5367 (fixes #​5359)

Full Changelog: RicoSuter/NSwag@v14.7.0...v14.7.1

Commits viewable in compare view.

Updated NSwag.MSBuild from 14.7.0 to 14.7.1.

Release notes

Sourced from NSwag.MSBuild's releases.

14.7.1

[!IMPORTANT]
Upgrade directly from v14.6.3 to v14.7.1 — skip v14.7.0.

v14.7.0 bundled NJsonSchema v11.6.0, which contained a regression that silently dropped nullability on required T? / [JsonRequired] T? DTO properties. The resulting OpenAPI/JSON schema marked those properties as non-nullable, so generated TypeScript and C# clients lost null-safety for fields the server can legitimately return as null (#​5359).

Corrections to v14.7.0

v14.7.1 updates to NJsonSchema v11.6.1, which corrects the handling of the C# required keyword and [JsonRequired]:

• These are now treated as presence markers (the property must be present in the JSON) rather than value constraints.
• Nullability from the declared type (string?, T?) is preserved.
• No spurious MinLength=1 on non-nullable strings.
• DataAnnotations [Required] semantics remain unchanged (still suppresses nullability and adds MinLength=1 to strings by default, matching its runtime behavior).

Observable client changes vs v14.7.0

For public required string[]? OptionList { get; init; } (#​5359):

	TypeScript client	C# client
v14.7.0 (broken)	optionList: string[] ❌	public string[] OptionList ❌
v14.7.1	optionList: string[] | null ✅	public string[]? OptionList ✅

For full details and truth tables across all required / [Required] / [JsonRequired] / [JsonProperty(Required=*)] combinations, see the NJsonSchema v11.6.1 release notes and NJsonSchema #​1919.

What's Changed

• Upgrade to NJsonSchema v11.6.1 (NSwag v14.7.1) by @​RicoSuter in Upgrade to NJsonSchema v11.6.1 (NSwag v14.7.1) RicoSuter/NSwag#5367 (fixes #​5359)

Full Changelog: RicoSuter/NSwag@v14.7.0...v14.7.1

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Superseded by #360.