Skip to content

chore(deps): Bump the nuget-dependencies group with 5 updates#3

Merged
JerrettDavis merged 1 commit into
mainfrom
dependabot/nuget/src/AgentContainers.Core/nuget-dependencies-3552bec3ea
Jun 16, 2026
Merged

chore(deps): Bump the nuget-dependencies group with 5 updates#3
JerrettDavis merged 1 commit into
mainfrom
dependabot/nuget/src/AgentContainers.Core/nuget-dependencies-3552bec3ea

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 16, 2026

Copy link
Copy Markdown
Contributor

Updated Microsoft.NET.Test.Sdk from 17.9.0 to 18.6.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

18.6.0

What's Changed

Changes to tests and infra

18.5.1

What's Changed

Full Changelog: microsoft/vstest@v18.5.0...v18.5.1

18.5.0

⚠️ Unlisted on Nuget, because of #​15718

What's Changed

Full Changelog: microsoft/vstest@v18.4.0...v18.5.0

18.4.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v18.3.0...v18.4.0

18.3.0

What's Changed

Internal fixes and updates

New Contributors

18.0.1

What's Changed

Fixing an issue with loading covrun64.dll on systems that have .NET 10 SDK installed: https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/code-coverage-dynamic-native-instrumentation

Internal changes

Full Changelog: microsoft/vstest@v18.0.0...v18.0.1

18.0.0

What's Changed

Internal fixes and updates

17.14.1

What's Changed

Full Changelog: microsoft/vstest@v17.14.0...v17.14.1

17.14.0

What's Changed

.NET versions updated

This version of VS Test upgraded .NET to net8 and net9. All projects targeting net6.0 (or other end-of-life .NET target frameworks) should pin their version of Microsoft.NET.Test.SDK to 17.13.0, or update the projects to net8 or newer. We remain backwards compatible with previous versions of Microsoft.NET.Test.SDK. This change does NOT prevent you from:

  • Updating to the latest VS, and running tests from net6.0 test projects.
  • Updating to the latest .NET SDK, and running tests from net6.0 test projects.

It also has no impact on .NET Framework projects, where we continue targeting .NET Framework 4.6.2.

Changes

Internal version updates and fixes

New Contributors

17.14.0-preview-25107-01

What's Changed

.NET versions updated

This version of VS Test upgraded .NET to net8 and net9. All projects targeting net6.0 (or other end-of-life .NET target frameworks) should pin their version of Microsoft.NET.Test.SDK to 17.13.0, or update the projects to net8 or newer. We remain backwards compatible with previous versions of Microsoft.NET.Test.SDK. This change does NOT prevent you from:

  • Updating to the latest VS, and running tests from net6.0 test projects.
  • Updating to the latest .NET SDK, and running tests from net6.0 test projects.

It also has no impact on .NET Framework projects, where we continue targeting .NET Framework 4.6.2.

Changes

Internal version updates and fixes

Will probably revert before release:

New Contributors

Full Changelog: microsoft/vstest@v17.13.0...v17.14.0-preview-25107-01

17.13.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.12.0...v17.13.0

17.12.0

What's Changed

Internal and infrastructure fixes:

Full Changelog: microsoft/vstest@v17.11.1...v17.12.0

17.11.1

What's Changed

Full Changelog: microsoft/vstest@v17.11.0...v17.11.1

17.11.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.10.0...v17.11.0-release-24352-06

17.11.0-release-24373-02

What's Changed

Full Changelog: microsoft/vstest@v17.11.0-release-24352-06...v17.11.0-release-24373-02

17.11.0-release-24352-06

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.10.0...v17.11.0-release-24352-06

17.10.0

What's Changed

And many infrastructure related changes and updates.

New Contributors

Full Changelog: microsoft/vstest@v17.9.0...v17.10.0

17.10.0-release-24177-07

What's Changed

New Contributors

And many infrastructure related changes to migrate our pipelines to common build system.

Full Changelog: microsoft/vstest@v17.10.0-preview-24080-01...v17.10.0-release-24177-07

17.10.0-preview-24080-01

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.9.0-preview-23577-04...v17.10.0-preview-24080-01

Commits viewable in compare view.

Updated NJsonSchema from 11.1.0 to 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

New Contributors

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

11.6.0

[!CAUTION]
Do not use this release — upgrade to v11.6.1 or later.

v11.6.0 introduced a regression in the handling of the C# required keyword and [JsonRequired]: required T? / [JsonRequired] T? properties incorrectly lost their nullability and gained a spurious MinLength=1 on strings. This broke downstream client generation — see NSwag#​5359. Fixed in v11.6.1 (#​1919).


Potentially breaking changes

  • C# 11 required keyword now recognized as required: Properties using the C# 11 required keyword (RequiredMemberAttribute / JsonRequiredAttribute) are now correctly treated as required in schema generation and code output. Previously these were incorrectly treated as optional (Required.Default). This changes generated code: such properties now get Required.Always, [Required] attribute, and the required modifier when UseRequiredKeyword is enabled. (#​1908)
  • Both JsonStringEnumMemberName and EnumMember attributes are now emitted for enum members when using System.Text.Json, for compatibility with NSwag's reflection-based URL parameter serialization. (#​1905)
  • $schema version preserved in ToJson() instead of forcing draft-04. If you relied on the output always being draft-04, this may affect you. (#​1881)
  • patternProperties validation now correctly applies to all matching properties, not just the first. (#​1898)
  • MinLength no longer incorrectly applied to DateTime, DateTimeOffset, DateOnly, TimeOnly properties. (#​1900)

What's Changed

New Contributors

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

11.5.2

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.5.1...v11.5.2

11.5.1

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.5.0...v11.5.1

11.5.0

What's Changed

Breaking changes:

Others:

Full Changelog: RicoSuter/NJsonSchema@v11.4.0...v11.5.0

11.4.0

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.3.2...v11.4.0

11.3.2

What's Changed

Full Changelog: RicoSuter/NJsonSchema@v11.3.1...v11.3.2

11.3.1

What's Changed

Full Changelog: RicoSuter/NJsonSchema@v11.3.0...v11.3.1

11.3.0

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.2.0...v11.3.0

11.2.0

What's Changed

New Contributors

Commits viewable in compare view.

Updated xunit from 2.7.0 to 2.9.3.

Release notes

Sourced from xunit's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated xunit.runner.visualstudio from 2.5.7 to 3.1.5.

Release notes

Sourced from xunit.runner.visualstudio's releases.

3.1.5

Release notes: https://xunit.net/releases/visualstudio/3.1.5

Commits viewable in compare view.

Updated YamlDotNet from 16.3.0 to 18.0.0.

Release notes

Sourced from YamlDotNet's releases.

18.0.0

What's Changed

  • Add a parse method wrapper and caching to fix AoT compilation by @​EdwardCooke in Add a parse method wrapper and caching to fix AoT compilation aaubry/YamlDotNet#1103
    BREAKING CHANGE This is a breaking change in the TypeInspectorSkeleton class and the ITypeInspector interface by adding 2 methods . Quick fix to resolve those breaking changes in your own custom TypeInspector is to return false on the HasParseMethod method and return null or throw an exception on the Parse method.

Full Changelog: https://github.com/aaubry/YamlDotNe...

Description has been truncated

Bumps Microsoft.NET.Test.Sdk from 17.9.0 to 18.6.0
Bumps NJsonSchema from 11.1.0 to 11.6.1
Bumps xunit from 2.7.0 to 2.9.3
Bumps xunit.runner.visualstudio from 2.5.7 to 3.1.5
Bumps YamlDotNet from 16.3.0 to 18.0.0

---
updated-dependencies:
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.6.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget-dependencies
- dependency-name: NJsonSchema
  dependency-version: 11.6.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: xunit
  dependency-version: 2.9.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: xunit.runner.visualstudio
  dependency-version: 3.1.5
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget-dependencies
- dependency-name: YamlDotNet
  dependency-version: 18.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@JerrettDavis JerrettDavis merged commit 44bd3e4 into main Jun 16, 2026
5 checks passed
@JerrettDavis JerrettDavis deleted the dependabot/nuget/src/AgentContainers.Core/nuget-dependencies-3552bec3ea branch June 16, 2026 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant