Bump the all-dependencies group with 5 updates#14
Merged
SvenGroot merged 1 commit intoMay 14, 2026
Merged
Conversation
Bumps coverlet.collector from 6.0.4 to 10.0.0 Bumps Microsoft.NET.Test.Sdk from 17.13.0 to 18.5.1 Bumps Microsoft.Windows.CsWin32 from 0.3.183 to 0.3.275 Bumps MSTest.TestAdapter from 3.8.3 to 4.2.3 Bumps MSTest.TestFramework from 3.8.3 to 4.2.3 --- updated-dependencies: - dependency-name: coverlet.collector dependency-version: 10.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-dependencies - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.5.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-dependencies - dependency-name: Microsoft.Windows.CsWin32 dependency-version: 0.3.275 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: all-dependencies - dependency-name: MSTest.TestAdapter dependency-version: 4.2.3 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-dependencies - dependency-name: MSTest.TestFramework dependency-version: 4.2.3 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
dependabot
Bot
deleted the
dependabot/nuget/src/Ookii.VmSockets.Tests/main/all-dependencies-df180d3dc4
branch
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
1 participant
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 coverlet.collector from 6.0.4 to 10.0.0.
Release notes
Sourced from coverlet.collector's releases.
10.0.0
Improvements
--coverlet-file-prefixoption for unique report files #1869Fixed
Maintenance
Diff between 8.0.1 and 10.0.0
8.0.1
Fixed
Improvements
Diff between 8.0.0 and 8.0.1
8.0.0
Special Thanks: A huge thank you to @Bertk for driving the majority of the work in this release! 🎉
Fixed
Improvements
Diff between 6.0.4 and 8.0.0
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 17.13.0 to 18.5.1.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
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
18.4.0
What's Changed
Add LoongArch64 support by @stdmnpkg in Add LoongArch64 support microsoft/vstest#15359
Refactor Condition evaluation by @Youssef1313 in Refactor Condition evaluation microsoft/vstest#15357
Adding info on extensions points part 1 by @nohwnd in Adding info on extensions points part 1 microsoft/vstest#15360
Add option to ask for uploading code QL before the standard window ends by @nohwnd in Add option to ask for uploading code QL before the standard window ends microsoft/vstest#15373
Update runtime versions by @nohwnd in Update runtime versions microsoft/vstest#15372
Fix .NET 10 regression for traits by @Youssef1313 in Fix .NET 10 regression for traits microsoft/vstest#15370
Update target frameworks to net10.0 and net11.0 by @dotnet-maestro[bot] in Update target frameworks to net10.0 and net11.0 microsoft/vstest#15349
Fix names in pipeline matrix so we don't have to align them by @nohwnd in Fix names in pipeline matrix so we don't have to align them microsoft/vstest#15365
Update SECURITY.md by @Youssef1313 in Update SECURITY.md microsoft/vstest#15342
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
... (truncated)
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:
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
... (truncated)
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:
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
Commits viewable in compare view.
Updated Microsoft.Windows.CsWin32 from 0.3.183 to 0.3.275.
Release notes
Sourced from Microsoft.Windows.CsWin32's releases.
0.3.275
Changes:
outreference if handle cannot be trivially represented as aSafeHandleThis list of changes was auto generated.
0.3.269
Changes:
Marshal.InitHandleAPI to avoid memory leak when OOM happensSafeHandlewhen freeing method accepts additional reserved parametersThis list of changes was auto generated.
0.3.264
Changes:
This list of changes was auto generated.
0.3.259
Changes:
This list of changes was auto generated.
0.3.257
Changes:
This list of changes was auto generated.
0.3.253
Changes:
This list of changes was auto generated.
0.3.252
Changes:
This list of changes was auto generated.
0.3.250
Changes:
This list of changes was auto generated.
0.3.248
Changes:
This list of changes was auto generated.
0.3.242
Changes:
This list of changes was auto generated.
0.3.238
Changes:
This list of changes was auto generated.
0.3.236
NOTE: This changes the signature of methods with optional parameters. This change is also documented at https://microsoft.github.io/CsWin32/docs/getting-started.html:
Optional out/ref parameters
Some parameters in win32 are
[optional, out]or[optional, in, out]. C# does not have an idiomatic way to represent this concept, so for any method that has such parameters, CsWin32 will generate two versions: one with allreforoutparameters included, and one with all such parameters omitted. For example:Working with Span-typed and MemorySize-d parameters
In the Win32 APIs there are many functions where one parameter is a buffer (
void*orbyte*) and another parameter is the size of that buffer. When generating for a target framework that supports Spans, there will be overloads of these functions that take aSpan<byte>which represents both of these parameters, since a Span refers to a chunk of memory and a length. For example, an API like IsTextUnicode has avoid*parameter whose length is described by the iSize parameter in the native signature. The CsWin32 projection of this method will be:Instead of passing the buffer and length separately, in this projection you pass just one parameter. Span is a flexible type with many things that can be converted to it safely. You will also see Span parameters for things that may look like a struct but are variable sized. For example, InitializeAcl looks like it returns an ACL struct but the parameter is annotated with a
[MemorySize]attribute in the metadata, indicating it is variable-sized based on another parameter. Thus, the cswin32 projection of this method will project this parameter as aSpan<byte>since the size of the parameter is variable:And you would call this by creating a buffer to receive the ACL. Then, after the call you can reinterpret the buffer as an ACL:
CsWin32 will also generate a struct-typed parameter for convenience but this overload will pass
sizeof(T)for the length parameter to the underlying Win32 API, so this only makes sense in some overloads such as SHGetFileInfo where the parameter has an annotation indicating it's variable-sized, but the size is only eversizeof(SHFILEINFOW):CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages:
CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages: