Repository navigation
Bump the nuget-dependencies group with 4 updates - #1131
Merged
KevinJump merged 1 commit intoOct 15, 2026
Merged
Conversation
Bumps Microsoft.NET.Test.Sdk from 18.4.0 to 18.11.0 Bumps Microsoft.SourceLink.GitHub from 10.0.201 to 10.0.402 Bumps NJsonSchema from 11.5.2 to 11.6.1 Bumps NUnit3TestAdapter from 6.2.0 to 6.3.1 --- updated-dependencies: - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies - dependency-name: Microsoft.SourceLink.GitHub dependency-version: 10.0.402 dependency-type: direct:production update-type: version-update:semver-patch 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: NUnit3TestAdapter dependency-version: 6.3.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
dependabot
Bot
deleted the
dependabot/nuget/nuget-dependencies-1033f429c8
branch
October 15, 2026 14:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Microsoft.NET.Test.Sdk from 18.4.0 to 18.11.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.11.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.10.1...v18.11.0
18.10.1
What's Changed
Full Changelog: microsoft/vstest@v18.10.0...v18.10.1
18.10.0
What's Changed
vstest.consoleand datacollector by @nohwnd in Run Microsoft.Testing.Platform test apps under vstest.console and datacollector microsoft/vstest#16201Full Changelog: microsoft/vstest@v18.9.0...v18.10.0
18.9.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.8.0...v18.9.0
18.8.1
What's Changed
Full Changelog: microsoft/vstest@v18.8.0...v18.8.1
18.8.0
What's Changed
Full Changelog: microsoft/vstest@v18.7.0...v18.8.0
18.7.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.6.0...v18.7.0
18.6.0
What's Changed
Changes to tests and infra
... (truncated)
18.5.1
What's Changed
Full Changelog: microsoft/vstest@v18.5.0...v18.5.1
18.5.0
What's Changed
Full Changelog: microsoft/vstest@v18.4.0...v18.5.0
Commits viewable in compare view.
Updated Microsoft.SourceLink.GitHub from 10.0.201 to 10.0.402.
Release notes
Sourced from Microsoft.SourceLink.GitHub's releases.
10.0.402
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.402and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.401
Release
What's Changed
... (truncated)
10.0.400
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.400and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.303
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.303and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.302
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.302and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.301
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.301and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.300
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.300and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.204
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.204and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.203
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.203and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.202
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.202and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Commits viewable in compare view.
Updated NJsonSchema from 11.5.2 to 11.6.1.
Release notes
Sourced from NJsonSchema's releases.
11.6.1
Corrections to v11.6.0
v11.6.0 added support for the C# 11
requiredkeyword and[JsonRequired]in schema generation (#1908), but folded them into the same bucket as DataAnnotations[Required]— which conflated three distinct concepts:requiredarray):requiredkeyword,[JsonRequired],[Required],[DataMember(IsRequired=true)], NewtonsoftRequired.Always/AllowNull[Required]only (plus NewtonsoftRequired.Always/DisallowNullfor runtime correctness)MinLength=1on strings):[Required]only (unlessAllowEmptyStrings=true)v11.6.1 (#1919) restores the correct separation. The
requiredkeyword and[JsonRequired]are now presence-only markers — they add the property to the schema'srequiredarray without suppressing nullability or addingMinLength=1.Behavioral deltas vs v11.6.0 (all restoring correctness)
required string?nullable: false,MinLength: 1❌nullable: true, noMinLength✅required stringMinLength: 1❌MinLength✅[JsonRequired] string?nullable: false,MinLength: 1❌nullable: true, noMinLength✅[JsonRequired] stringMinLength: 1❌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
Potentially breaking changes
requiredkeyword now recognized as required: Properties using the C# 11requiredkeyword (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 getRequired.Always,[Required]attribute, and therequiredmodifier whenUseRequiredKeywordis enabled. (#1908)JsonStringEnumMemberNameandEnumMemberattributes are now emitted for enum members when using System.Text.Json, for compatibility with NSwag's reflection-based URL parameter serialization. (#1905)$schemaversion preserved inToJson()instead of forcing draft-04. If you relied on the output always being draft-04, this may affect you. (#1881)patternPropertiesvalidation now correctly applies to all matching properties, not just the first. (#1898)DateTime,DateTimeOffset,DateOnly,TimeOnlyproperties. (#1900)What's Changed
+in JSON reference paths being decoded as space by @Copilot in Fix+in JSON reference paths being decoded as space RicoSuter/NJsonSchema#1880-1generating invalid C# identifier instead ofMinus1by @Copilot in Fix property named-1generating invalid C# identifier instead ofMinus1RicoSuter/NJsonSchema#1882New Contributors
+in JSON reference paths being decoded as space RicoSuter/NJsonSchema#1880Full Changelog: RicoSuter/NJsonSchema@v11.5.2...v11.6.0
Commits viewable in compare view.
Updated NUnit3TestAdapter from 6.2.0 to 6.3.1.
Release notes
Sourced from NUnit3TestAdapter's releases.
6.3.1
This is a hotfix release for issue 1504
6.3.0
See Release notes
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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