chore(deps): update nuget packages (major)#402
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
5e954fd to
6f0710d
Compare
4d343f8 to
76a482d
Compare
d18c345 to
b5c27c7
Compare
b5c27c7 to
3cf7ea9
Compare
8016ce9 to
bdc6adf
Compare
bdc6adf to
2f5e66c
Compare
2f5e66c to
3d1725f
Compare
3d1725f to
2a37552
Compare
1f9812f to
be36702
Compare
cec871c to
96d276d
Compare
02d7aaa to
c6b71ae
Compare
671f113 to
dff52f2
Compare
7540e16 to
8f881b6
Compare
8f881b6 to
2d81bc5
Compare
2d81bc5 to
eca7496
Compare
eca7496 to
ae1e1e7
Compare
ae1e1e7 to
f2ceeff
Compare
94a059e to
6162ed8
Compare
2c1b86b to
addfea7
Compare
6404a36 to
4a57a70
Compare
5cefa53 to
37e024c
Compare
8a50d70 to
05b4888
Compare
6d955a9 to
51ddcfb
Compare
9b52d00 to
6432897
Compare
151b02e to
c0d22c0
Compare
|
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.



This PR contains the following updates:
3.7.500.80→4.0.9.53.7.510.6→4.0.25.13.7.502.39→4.0.3.63.7.504.32→4.0.7.68.1.0→9.0.09.0.0→10.1.02025.2.4→2026.2.08.0.24→10.0.98.0.24→10.0.92.11.0→3.0.08.0.0→10.0.1Release Notes
aws/aws-sdk-net (AWSSDK.Core)
v4.0.9v4.0.8v4.0.7v4.0.6Compare Source
v4.0.5Compare Source
v4.0.4v4.0.3Compare Source
v4.0.2v4.0.1v4.0.0JetBrains/JetBrains.Annotations (JetBrains.Annotations)
v2026.2.0Compare Source
dotnet/dotnet (Microsoft.AspNetCore.TestHost)
v10.0.9v10.0.8v10.0.7v10.0.6v10.0.5v10.0.4v10.0.3v10.0.2v10.0.1v9.0.7: .NET 9.0.7You can build .NET 9.0 from the repository by cloning the release tag
v9.0.7and 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
v9.0.6: .NET 9.0.6You can build .NET 9.0 from the repository by cloning the release tag
v9.0.6and 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
v9.0.5: .NET 9.0.5You can build .NET 9.0 from the repository by cloning the release tag
v9.0.5and 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
v9.0.4: .NET 9.0.4You can build .NET 9.0 from the repository by cloning the release tag
v9.0.4and 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
v9.0.3: .NET 9.0.3You can build .NET 9.0 from the repository by cloning the release tag
v9.0.3and 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
v9.0.2: .NET 9.0.2You can build .NET 9.0 from the repository by cloning the release tag
v9.0.2and 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
v9.0.1: .NET 9.0.1You can build .NET 9.0 from the repository by cloning the release tag
v9.0.1and 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
v9.0.0: .NET 9.0.0You can build .NET 9.0 from the repository by cloning the release tag
v9.0.0and 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
StackExchange/StackExchange.Redis (StackExchange.Redis)
v3.0.03.0.0 represents an overhaul of the internal IO logic, for both performance and stability reasons.
Intentionally, there are no† API changes in this release; it is a direct mirror of 2.13.17, but with the new IO core.
† addendum, one change discovered:
Execute[Async]now detects and respects "admin" commands, i.e. those protected byAllowAdmin; for example, in 2.x,db.Execute("FLUSHALL");would work even ifAllowAdminwas not enabled - this will now throw at the client without issuing the command to the serverWhat is the aim of the internals rewrite?
SE.Redis v2 made use of a few concepts internally:
v3 fundamentally revises these engineering decisions:
This allows for significant performance improvement, especially when processing large / complex results - for example, if we use the
LRANGE_600test fromredis-benchmark(orresp-benchmark):### classic SE.Redis 2.13.17.28173 ### LRANGE_600: 7,579 requests per second LRANGE_600: 7,554 requests per second LRANGE_600: 7,284 requests per second LRANGE_600: 7,158 requests per second LRANGE_600: 7,174 requests per secondvs
### classic SE.Redis 3.0.0.11234 ### LRANGE_600: 16,408 requests per second LRANGE_600: 17,681 requests per second LRANGE_600: 17,331 requests per second LRANGE_600: 17,317 requests per second LRANGE_600: 16,665 requests per second(for tests with simpler results, like
INCR, results of over 1M requests per second are achievable)3.0 is the first part of a wave of planned IO work; 3.1 will revise the "write" part of the write loop, moving message serialization out of the critical serialized core of the multiplexer. All of this work is based on extensive prototyping and benchmarking, demonstrating that these approaches, when combined, provide significant throughput and stability improvements.
This release has undergone extensive testing. If you experience problems, please let us know!
v2.13.10Compare Source
This release is marked inactive due to a critical bug when using TCP keep-alives on DNS (i.e. named, not IP) endpoints; this is specific to non-Windows platforms, before .NET 10. See #3086 and #3090
What's Changed
ConfigurationOptions: don't serialize (ToString()) or cloneProtocolif it comes from the defaults-provider by @mgravell in #3082Full Changelog: StackExchange/StackExchange.Redis@2.13.1...2.13.10
v2.13.1Compare Source
IMPORTANT: This release changes the default protocol from RESP2 to RESP3 for Azure Managed Redis endpoints (only); this
has scalability and feature advantages, but if you are using modules or ad-hoc commands, please see the RESP3 notes, which includes:
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.12.27...2.13.1
v2.12.14Compare Source
What's Changed
Impact: "high" if using cluster and high-integrity-mode together (resolves an issue that can mis-report
-MOVEDresponses as integrity failures)NuGet link
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.12.8...2.12.14
v2.12.8Compare Source
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.12.4...2.12.8
v2.12.4Compare Source
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.12.1...2.12.4
v2.12.1Compare Source
What's Changed
LCSoutputs and missingRedisType.VectorSet(#3028 by @mgravell)AsciiHash(#3028 by @mgravell)Full Changelog: StackExchange/StackExchange.Redis@2.11.8...2.12.1
v2.11.8Compare Source
What's Changed
-MOVEDerror pointing to same endpoint. by @barshaul in #3003HOTKEYSby @mgravell in #3017-MOVEDtest by @mgravell in #3020New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.11.3...2.11.8
v2.11.3Compare Source
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.11.0...2.11.3
coverlet-coverage/coverlet (coverlet.collector)
v10.0.1Improvements
Fixed
Maintenance
Diff between 10.0.0 and 10.0.1
v10.0.0Improvements
--coverlet-file-prefixoption for unique report files #1869Fixed
Maintenance
Diff between 8.0.1 and 10.0.0
v8.0.1Fixed
Improvements
Diff between 8.0.0 and 8.0.1
Configuration
📅 Schedule: (UTC)
🚦 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.