chore(deps): update nuget packages #181
Open
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/nuget
branch
4 times, most recently
from
b1abff1 to
ca0cbae
Compare
renovate
bot
force-pushed
the
renovate/nuget
branch
7 times, most recently
from
99542e2 to
29e40b7
Compare
renovate
bot
force-pushed
the
renovate/nuget
branch
3 times, most recently
from
24af30d to
71a7368
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nuget
branch
2 times, most recently
from
2a33aa4 to
e47773f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nuget
branch
6 times, most recently
from
adaf806 to
87caea5
Compare
renovate
bot
force-pushed
the
renovate/nuget
branch
6 times, most recently
from
bc9c7c1 to
afbde2e
Compare
renovate
bot
force-pushed
the
renovate/nuget
branch
7 times, most recently
from
29a8852 to
5b2a518
Compare
renovate
bot
force-pushed
the
renovate/nuget
branch
6 times, most recently
from
31711d2 to
627c87a
Compare
renovate
bot
force-pushed
the
renovate/nuget
branch
5 times, most recently
from
b98f9a2 to
592a819
Compare
renovate
bot
force-pushed
the
renovate/nuget
branch
4 times, most recently
from
1582130 to
7462635
Compare
renovate
bot
force-pushed
the
renovate/nuget
branch
from
7462635 to
9948803
Compare
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.
This PR contains the following updates:
3.7.106.1->3.7.415.143.7.103.16->3.7.401.583.19.0->3.25.03.19.0->3.25.03.19.0->3.25.00.4.0->0.5.14.18.0->4.18.12.64.0->2.70.08.0.0->8.0.18.0.0->8.0.18.0.0->8.0.18.0.0->8.0.18.0.0->8.0.317.6.3->17.13.01.18.1->1.21.23.13.3->3.14.03.6.1->3.10.04.5.0->4.6.03.0.1->3.1.17.0.0->7.0.18.0.4->8.0.56.0.0->6.0.43.2.26->3.2.46Release Notes
aws/aws-sdk-net (AWSSDK.S3)
v3.7.414v3.7.413.3Compare Source
v3.7.413.2Compare Source
v3.7.413.1Compare Source
v3.7.413v3.7.411v3.7.410v3.7.409v3.7.408v3.7.407v3.7.406.1Compare Source
v3.7.406v3.7.404v3.7.403.1Compare Source
v3.7.403v3.7.402v3.7.401v3.7.400v3.7.308v3.7.306v3.7.305v3.7.304v3.7.303Compare Source
v3.7.302v3.7.301v3.7.300v3.7.204v3.7.202v3.7.200v3.7.108v3.7.107AutoFixture/AutoFixture (AutoFixture)
v4.18.1: Version v4.18.1What's Changed
Full Changelog: AutoFixture/AutoFixture@v4.18.0...v4.18.1
dotnet/runtime (Microsoft.Extensions.Configuration.FileExtensions)
v8.0.1: .NET 8.0.1Release
microsoft/vstest (Microsoft.NET.Test.Sdk)
v17.13.0What's Changed
Add letter number among valid identifiers in class name by @nohwnd in https://github.com/microsoft/vstest/pull/13868
Fix formatting in Runner by @mthalman in https://github.com/microsoft/vstest/pull/13871
Downgrade xunit skip warning to info by @nohwnd in https://github.com/microsoft/vstest/pull/10381
Add msdia for arm64 into nuget by @nohwnd in https://github.com/microsoft/vstest/pull/10382
Enable native debugging for vstest.console by @ocitrev in https://github.com/microsoft/vstest/pull/10401
Fix RFCs links by @Youssef1313 in https://github.com/microsoft/vstest/pull/10424
Convert to auto property by @nohwnd in https://github.com/microsoft/vstest/pull/10365
Update Versions.props by @nohwnd in https://github.com/microsoft/vstest/pull/10378
Enable TSA by @jakubch1 in https://github.com/microsoft/vstest/pull/10385
Arm64 dia by @nohwnd in https://github.com/microsoft/vstest/pull/10390
Update source-build team references by @MichaelSimons in https://github.com/microsoft/vstest/pull/10388
Exclude .signature.p7s from nupkg file count by @ellahathaway in https://github.com/microsoft/vstest/pull/10418
Set NetCurrent so that it doesn't roll forward automatically by @ViktorHofer in https://github.com/microsoft/vstest/pull/10622
New Contributors
Full Changelog: microsoft/vstest@v17.12.0...v17.13.0
v17.12.0What's Changed
Internal and infrastructure fixes:
Full Changelog: microsoft/vstest@v17.11.1...v17.12.0
v17.11.1What's Changed
Full Changelog: microsoft/vstest@v17.11.0...v17.11.1
v17.11.0What's Changed
New Contributors
Full Changelog: microsoft/vstest@v17.10.0...v17.11.0-release-24352-06
v17.10.0What's Changed
2338548by @dotnet-bot in https://github.com/microsoft/vstest/pull/4794And many infrastructure related changes and updates.
New Contributors
Full Changelog: microsoft/vstest@v17.9.0...v17.10.0
v17.9.0What's Changed
HtmlLoggerby @daveMueller in https://github.com/microsoft/vstest/pull/4744New Contributors
Full Changelog: microsoft/vstest@v17.8.0...v17.9.0
v17.8.0What's Changed
Full Changelog: microsoft/vstest@v17.7.2...v17.8.0
v17.7.2What's Changed
Full Changelog: microsoft/vstest@v17.7.1...v17.7.2
v17.7.1What's Changed
Full Changelog: microsoft/vstest@v17.7.0...v17.7.1
v17.7.0The most pressing issues were all backported to 17.6.1, 17.6.2 and 17.6.3.
Issues fixed (since 17.6.3)
Don't print socket transport error in console by @nohwnd in #4493 which fixes #4461
When testhost crashes, we no longer print the transport error:
This error is a side-effect or our architecture is almost never the culprit. Instead it leads developers away from the actual issue which is crash of testhost, or datacollector.
Pass workloads to proxy managers in #4422 by @nohwnd
Which allows datacollector users to only receive the sources that are currently running in the testhost associated to datacollector, instead of all the sources that have the same target framework.
Fix Newtonsoft versions in testhost.deps.json in #4367 by @nohwnd
testhost.runtimeconfig.json files that we ship with testhost contained an old version of Newtonsoft.Json. The version in this file does not have an effect on execution, but some compliance tools statically analyze it and report possible vulnerabilities.
Other fixes:
Special thanks to @SimonCropp for the many fixes regarding nullability spelling and code style in #4518, #4520, #4525, #4526, #4521, #4519, #4522, #4529 🙇
Full Changelog: microsoft/vstest@v17.6.3...v17.7.0
Drops
nunit/nunit (NUnit)
v3.14.0: NUnit 3.14.0See release notes
nunit/nunit.analyzers (NUnit.Analyzers)
v3.10.0: NUnit Analyzers 3.10 (and 2.10)Compare Source
NUnit Analyzers 3.10 (and 2.10) - November 27, 2023
This release adds a couple of improvements to the analyzers:
These improvements extend the functionality in the beta that added support for NUnit 4 and
for migrating to NUnit 4. Especially, the handling of the movement of classic asserts into a new namespace
NUnit.Framework.Legacy and of the improved assert result messages - for more information see
https://docs.nunit.org/articles/nunit/Towards-NUnit4.html. The analyzers can help updating the
classic assert and fix the assert messages.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Tooling, Process, and Documentation
v3.9.0: NUnit Analyzers 3.9 (and 2.9)Compare Source
NUnit Analyzers 3.9 (and 2.9) - October 27, 2023
This release contains bugfixes to NUnit2045 - Use Assert.Multiple - and NUnit1032 -
An IDisposable field/property should be Disposed in a TearDown method - and corrects
a StackOverflowException when tests calls methods recursively.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Bugs
v3.8.0: NUnit Analyzers 3.8 (and 2.8)Compare Source
NUnit Analyzers 3.8 (and 2.8) - September 25, 2023
This release contains a fix to the WithinUsageAnalyzer and handling of false duplicates when
combining NUnit1032 - An IDisposable field/property should be Disposed in a TearDown method -
with LifeCycle.InstancePerTestCase.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v3.7.0: NUnit Analyzers 3.7 (and 2.7)Compare Source
NUnit Analyzers 3.7 (and 2.7) - September 16, 2023
This release contains a lot of improvements and corrections to the supression of non-nullable fields and properties
that are assigned in setup methods (and not in constructors). We have also added suppression of:
The release also contain some improvements to the performance of the analyzers by avoid repeated calls to
GetTypeByMetadataName. Also ValuesAttribute is now also handled by the analyzer in a similar manner as TestCaseAttribute.
Most of the work done in this release have either been driven by or made by @manfred-brands.
The release contains contributions from the following users (in alphabetical order):
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.