Repository navigation
chore(deps): update non-major dependencies - #23
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
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:
8.1.2→8.1.102.9.17→2.13.17Release Notes
simplify9/SW-PrimitiveTypes (SimplyWorks.PrimitiveTypes)
v8.1.10Compare Source
v8.1.9Compare Source
v8.1.8Compare Source
v8.1.7Compare Source
v8.1.6Compare Source
v8.1.5Compare Source
v8.1.4Compare Source
v8.1.3Compare Source
StackExchange/StackExchange.Redis (StackExchange.Redis)
v2.13.17Compare Source
What's Changed
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.13.10...2.13.17
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 (AMR) 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
v2.11.0Compare Source
get 2.11.0 on NuGet
What's Changed
For Redis 8.6:
HOTKEYSby @mgravell in #3008The time-series changes for 8.6 are over in NRedisStack 1.3.0
Other features:
Internal bits:
New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.10.14...2.11.0
v2.10.14Compare Source
Priority: high; the backlog fix (#3002) is rare and niche (specific to low-memory scenarios), but fixes a problem where the client can get into a non-recoverable state.
What's Changed
HGETEX; no impact to release build by @mgravell in #2999New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.10.1...2.10.14
v2.10.1Adds support for Redis 8.4 features
MSETEX ...; details controlled via newExpirationAPISET ... IFEQ/IFNE/IFDEQ/IFDNE digestOrValue; details controlled via newValueConditionAPI; also usesExpirationfor expiryDELEX ... IFEQ/IFNE/IFDEQ/IFDNE digestOrValue(again viaValueCondition)LockExtend[Async]/LockRelease[Async]when possibleXREADGROUP ... CLAIM minIdleTimefor simplified stream processingNote that niche
StringSet[Async]scenarios may require trivial build changes due to removing default parameter values; this simplify means explicitly specifyingkeepTtl, or using the newExpirationAPI. There is no impact to already compiled code (no methods have been removed).8.4 also includes "hybrid search"; this is not currently exposed in SE.Redis, and will be added to NRedisStack ASAP.
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.9.32...2.10.1
v2.9.32Compare Source
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.9.25...2.9.32
v2.9.25Compare Source
IMPORTANT: this release changes the distribution of pub/sub channels when using cluster; see 2.9.24 for more details.
What's Changed
This change is a critical fix that fixes a packaging failure in 2.9.24; for the relevant feature changes: see 2.9.24.
Full Changelog: StackExchange/StackExchange.Redis@2.9.24...2.9.25
v2.9.24Compare Source
IMPORTANT: this release changes the distribution of pub/sub channels when using cluster:
(this change is specific to pub/sub with regular
SUBSCRIBEchannels, not "sharded"SSUBSCRIBEchannels)SSUBSCRIBE)SSUBSCRIBEchannels are now randomly distributed to nodes by default, but can optionally use key-like routing by calling.WithKeyRouting()on theRedisChannelvalueThis change represents a safer, "least surprises" default; most people expect their cluster to help distribute load, including pub/sub load, between nodes. This is especially useful when there are few (or even only a single) channel(s) that dominate the pub/sub load, which is surprisingly common. Without this change, all that load would be handled only by a single server, because the channel
my_notificationswould be treated similarly to a key, via hash-slot sharding, and all clients would connect to the node serving that slot - when in reality, any node can be used for subscription, with the server distributing events horizontally to all nodes.If you prefer the routed behaviour: use
.WithKeyRouting()before subscribing.What's Changed
SSUBSCRIBE) routing to random, with newWithKeyRouting()API to opt into routed by @mgravell in #2958New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.9.17...2.9.24
Configuration
📅 Schedule: (in timezone Asia/Amman)
* 0-8 * * 1)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate CLI.