Bump the all group with 7 updates #50
Closed
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 DotNet.ReproducibleBuilds from 1.2.25 to 1.2.39.
Release notes
Sourced from DotNet.ReproducibleBuilds's releases.
1.2.39
Additions
Removals
Changed
Tidying up
New Contributors
Full Changelog: dotnet/reproducible-builds@v1.2.25...v1.2.39
Commits viewable in compare view.
Updated FluentAssertions from 8.5.0 to 8.8.0.
Release notes
Sourced from FluentAssertions's releases.
8.8.0
What's Changed
New features
Improvements
Documentation
configparameter by @jnyrup in Add docs forconfigparameter fluentassertions/fluentassertions#3104Others
Full Changelog: fluentassertions/fluentassertions@8.7.1...8.8.0
8.7.1
What's Changed
Others
Full Changelog: fluentassertions/fluentassertions@8.7.0...8.7.1
8.7.0
What's Changed
New features
Others
DisableImplicitNuGetFallbackFolderby @jnyrup in SetDisableImplicitNuGetFallbackFolderfluentassertions/fluentassertions#3095Full Changelog: fluentassertions/fluentassertions@8.6.0...8.7.0
8.6.0
What's Changed
Improvements
Value.ThatMatchesandValue.ThatSatisfiesby @dennisdoomen in Add support for inline assertions using Value.ThatMatches and Value.ThatSatisfies fluentassertions/fluentassertions#3076Others
New Contributors
Full Changelog: fluentassertions/fluentassertions@8.5.0...8.6.0
Commits viewable in compare view.
Updated GitHubActionsTestLogger from 2.4.1 to 3.0.1.
Release notes
Sourced from GitHubActionsTestLogger's releases.
3.0.1
Full Changelog: Tyrrrz/GitHubActionsTestLogger@3.0...3.0.1
3.0
Configuration breaking changes
@trait.XYZreplacement token has been removed.See the readme for updated usage instructions.
What's Changed
Microsoft.Testing.Platformby @Tyrrrz in Add support forMicrosoft.Testing.PlatformTyrrrz/GitHubActionsTestLogger#53New Contributors
Full Changelog: Tyrrrz/GitHubActionsTestLogger@2.4.1...3.0
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 17.14.1 to 18.0.1.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
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)
Commits viewable in compare view.
Updated Microsoft.Windows.CsWin32 from 0.3.183 to 0.3.257.
Release notes
Sourced from Microsoft.Windows.CsWin32's releases.
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: