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.
This PR contains the following updates:
3.7.401.6
->3.7.401.15
8.0.1
->8.1.0
6.12.0
->6.12.1
0.3.0
->0.4.0
8.0.0
->8.0.8
8.0.7
->8.0.8
8.0.0
->8.9.1
17.8.0
->17.11.1
4.18.4
->4.20.72
2.1.0-beta.2
->2.1.0-beta.3
4.15.0
->4.25.0
0.5.2
->0.5.3
3.6.0
->3.10.0
6.0.0
->6.0.2
2.4.2
->2.9.0
2.6.1
->2.9.0
2.4.5
->2.8.2
2.5.3
->2.8.2
Release Notes
fluentassertions/fluentassertions (FluentAssertions)
v6.12.1
Compare Source
What's Changed
Improvements
BeEmpty()
andBeNullOrEmpty()
performance forIEnumerable<T>
, by materializing only the first item - #2530Fixes
DateTimeOffset
withBeWithin(...).Before(...)
- #2312BeEquivalentTo
will now find and can map subject properties that are implemented through an explicitly-implemented interface - #2152because
andbecauseArgs
were not passed down the equivalency tree - #2318BeEquivalentTo
can again compare a non-genericIDictionary
with a generic one - #2358FormattingOptions
were not respected in innerAssertionScope
- #2329true
andfalse
in failure messages and make them formattable to a customBooleanFormatter
- #2390, #2393NotBeOfType
when wrapped in anAssertionScope
and the subject is null - #2399BeWritable
/BeReadable
when wrapped in anAssertionScope
and the subject is read-only/write-only - #2399ThrowExactly[Async]
when wrapped in anAssertionScope
and no exception is thrown - #2398[Not]HaveExplicitProperty
when wrapped in anAssertionScope
and not implementing the interface - #2403[Not]HaveExplicitMethod
when wrapped in anAssertionScope
and not implementing the interface - #2403BeEquivalentTo
to excludeprivate protected
members from the comparison - #2417BeEquivalentTo
on an emptyArraySegment
- #2445, #2511BeEquivalentTo
with a custom comparer can now handle null values - #2489AssertionScope(context)
create a chained context - #2607AssertionScope
constructor would not create an actual scope associated with the thread - #2607ThrowWithinAsync
not respectingOperationCanceledException
- #2614BeEquivalentTo
with anIEqualityComparer
targeting nullable types - #2648Full Changelog: fluentassertions/fluentassertions@6.12.0...6.12.1
martincostello/xunit-logging (MartinCostello.Logging.XUnit)
v0.4.0
What's Changed
New Contributors
Full Changelog: martincostello/xunit-logging@v0.3.0...v0.4.0
dotnet/aspnetcore (Microsoft.AspNetCore.Mvc.Testing)
v8.0.8
v8.0.7
v8.0.6
v8.0.5
: .NET 8.0.5Release
What's Changed
31993df
to77afe8e
by @dependabot in https://github.com/dotnet/aspnetcore/pull/54872Type.GetType
when activating types in data protection by @github-actions in https://github.com/dotnet/aspnetcore/pull/54762Full Changelog: dotnet/aspnetcore@v8.0.4...v8.0.5
v8.0.4
: .NET 8.0.4Release
v8.0.3
: .NET 8.0.3Release
v8.0.2
: .NET 8.0.2Release
v8.0.1
: .NET 8.0.1Release
dotnet/efcore (Microsoft.EntityFrameworkCore.InMemory)
v8.0.8
: .NET 8.0.8Release
dotnet/extensions (Microsoft.Extensions.TimeProvider.Testing)
v8.9.1
: .NET Extensions 8.9.18.9.1 packages are no all published in NuGet.org
What's Changed
Full Changelog: dotnet/extensions@v8.9.0...v8.9.1
v8.9.0
: .NET Extensions 8.9.08.9.0 packages are now all published to NuGet.org
What's Changed
New Contributors
Full Changelog: dotnet/extensions@v8.8.0...v8.9.0
v8.8.0
: .NET Extensions 8.88.8.0 packages are now all published in NuGet.org.
What's Changed
New Contributors
Full Changelog: dotnet/extensions@v8.7.0...v8.8.0
v8.7.0
: .NET Extensions 8.7.08.7.0 packages are now all published in NuGet.org.
What's Changed
New Contributors
Full Changelog: dotnet/extensions@v8.6.0...v8.7.0
v8.6.0
: .NET Extensions 8.6.08.6.0 packages are now all published in NuGet.org.
What's Changed
Full Changelog: dotnet/extensions@v8.5.0...v8.6.0
v8.5.0
: .NET Extensions 8.5.08.5.0 packages are now all published in NuGet.org.
What's Changed
New Contributors
Full Changelog: dotnet/extensions@v8.4.0...v8.5.0
v8.4.0
: .NET Extensions 8.4.08.4.0 packages are now all published in NuGet.org.
What's Changed
New Contributors
Full Changelog: dotnet/extensions@v8.3.0...v8.4.0
v8.3.0
: .NET Extensions 8.3.08.3.0 packages are now all published in NuGet.org.
What's Changed
New Contributors
Full Changelog: dotnet/extensions@v8.2.0...v8.3.0
v8.2.0
: .NET Extensions 8.2.08.2.0 packages are now all published in NuGet.org.
What's Changed
Configuration
📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.