You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Breaking change: Fixed tracestate parsing to reject keys that do not
begin with a lowercase letter, including keys beginning with digits, to
align with the W3C Trace Context specification.
Breaking change: Fixed an insecure disk retry default for OTLP export.
Disk retry now requires OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATH
when OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=disk is configured.
Improve efficiency of parsing of baggage and B3 propagation headers.
OtlpLogExporter now uses IHttpClientFactory on .NET 8+.
Fixed an issue in OTLP/gRPC retry handling when parsing gRPC statuses.
Fixed OTEL_SPAN_ATTRIBUTE_VALUE_LENGTH_LIMIT not being applied.
Fixed baggage and trace headers not respecting the maximum length in some cases.
Fixed BaggagePropagator to trim optional whitespace (OWS) around =
separators when parsing the baggage header.
Fixed BaggagePropagator to strip baggage properties from values when
parsing the baggage header.
Fixed OTLP persistent storage clean-up handling for malformed filenames.
Fixed resource leak in batch and periodic exporting task workers for Blazor/WASM.
Fixed LogRecord.LogLevel to preserve LogLevel.None.
Fixed OTEL_TRACES_SAMPLER_ARG handling for out-of-range values.
Fixed an issue with OTLP disk retry storage where metrics and logs used the
traces storage directory.
Fixed full OTLP endpoint being logged by internal diagnostics.
Improve efficiency of parsing of baggage, B3 and Jaeger propagation headers.
Hardened Zipkin exporter memory usage for endpoint caching and array tag
serialization.
Limit how much of the response body is read by the OTLP exporter when
export fails and error logging is enabled.
Added Task-based worker support for BatchExportProcessor and PeriodicExportingMetricReader to enable the OpenTelemetry SDK to work
in single-threaded WebAssembly environments such as Blazor and
Uno Platform.
Breaking change: The Baggage API now disallows empty baggage names and
treats baggage names and values as case sensitive, aligning with the latest Baggage API specification.
Various bug fixes across OpenTelemetry.Api and OpenTelemetry SDK,
including fixes for thread-safety, sampler edge cases, metrics precision,
and observable instrument lifecycle handling.
Added support for ActivitySource.TelemetrySchemaUrl
and Meter.TelemetrySchemaUrl properties across exporters.
Improved performance and reduced memory consumption for metrics histograms.
Added mTLS configuration support for the OTLP exporter (client cert/key and
CA certificate options).
OpenTelemetry.Exporter.Zipkin is deprecated and will stop receiving updates
in December 2026. Zipkin already supports OTLP ingestion.
Migrate to OpenTelemetry.Exporter.OpenTelemetryProtocol as stated
in the Deprecating Zipkin Exporter blog post.
Breaking Change When targeting net8.0, the package now depends on version 8.0.0 of the Microsoft.Extensions.DependencyInjection.Abstractions, Microsoft.Extensions.Diagnostics.Abstractions, Microsoft.Extensions.Hosting.Abstractions and Microsoft.Extensions.Logging.Configuration NuGet packages.
Update System.Diagnostics.DiagnosticSource dependency to 10.0.0
for all target frameworks.
Update Microsoft.Extensions.* dependencies to 10.0.0
for .NET Framework and .NET Standard.
Breaking Change NuGet packages now use the Sigstore bundle format
(.sigstore.json) for digital signatures instead of separate signature
(.sig) and certificate (.pem) files. This requires cosign 3.0 or later
for verification. See the Digital signing
section for updated verification instructions.
In version 1.13.0, the digital signature (.dll-keyless.sig) and
certificate (.dll-keyless.pem) files were unintentionally omitted from the
published NuGet packages.
This hotfix restores the Sigstore signing artifacts for all target frameworks
(net462, netstandard2.0, netstandard2.1, net8.0, net9.0), ensuring
the integrity of DLL verification using Sigstore cosign.
Replace IReadOnlyBasicProperties, IAmqpHeader generic type constraints in IChannel.BasicPublishAsync() with a single interface constraint. #1813
Fixed bugs:
ObjectDisposedException from MaybeHandlePublisherConfirmationTcsOnChannelShutdownAsync closing connection when CloseChannel Continuation is cancelled #1865
Possible connection leak when trying to create first connection #1856
Semaphore exception when publishing with confirmation #1818
Cancellation token not canceled in AsyncEventingBasicConsumer.ReceivedAsync #1787
Event handlers for Channel.ChannelShutdownAsync and Consumer.ShutdownAsync are all called on the last registration? #1837
Exception details lost when using async API #1831
Recovery loop is not cancelled on connection dispose #1825
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
Fix incorrect routing of some sorted-set and stream commands by @mgravell in #3080
ConfigurationOptions: don't serialize (ToString()) or clone Protocol if it comes from the defaults-provider by @mgravell in #3082
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:
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.
support multi-string-set with expiration MSETEX ...; details controlled via new Expiration API
support checked string-set SET ... IFEQ/IFNE/IFDEQ/IFDNE digestOrValue; details controlled via new ValueCondition API; also uses Expiration for expiry
support checked string-delete DELEX ... IFEQ/IFNE/IFDEQ/IFDNE digestOrValue (again via ValueCondition)
use checked string-set/delete to implement LockExtend[Async]/LockRelease[Async] when possible
support XREADGROUP ... CLAIM minIdleTime for simplified stream processing
Note that niche StringSet[Async] scenarios may require trivial build changes due to removing default parameter values; this simplify means explicitly specifying keepTtl, or using the new Expiration API. 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.
IMPORTANT: this release changes the distribution of pub/sub channels when using cluster:
(this change is specific to pub/sub with regular SUBSCRIBE channels, not "sharded" SSUBSCRIBE channels)
pre 2.9.24: all channels would always be routed similarly to key-like routing (and similar to SSUBSCRIBE)
from 2.9.24: non-SSUBSCRIBE channels are now randomly distributed to nodes by default, but can optionally use key-like routing by calling .WithKeyRouting() on the `RedisC
✂ Note
PR body was truncated to here.
Configuration
📅 Schedule: (UTC)
Branch creation
At any time (no schedule defined)
Automerge
At any time (no schedule defined)
🚦 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.
If you want to rebase/retry this PR, check this box
projectorigin-renovateBot
changed the title
Update dependency StackExchange.Redis to 2.9.24
Update dependency xunit.runner.visualstudio to 3.1.5
Sep 29, 2025
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
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:
2.1.66→2.1.797.2.0→7.2.23.32.1→3.35.12.71.0→2.80.02.72.0→2.81.19.0.3→9.0.59.0.3→9.0.51.12.0→1.16.01.12.0→1.16.01.12.0→1.16.01.12.0→1.16.01.12.0→1.16.01.12.0→1.15.17.1.2→7.2.12.9.17→2.13.179.0.4→9.0.68.14.0→8.19.16.0.3→6.1.52.71.0→2.80.03.1.4→3.1.5Release Notes
DapperLib/Dapper (Dapper)
v2.1.79Compare Source
What's Changed
New Contributors
Full Changelog: DapperLib/Dapper@2.1.72...2.1.79
v2.1.72Compare Source
What's Changed
New Contributors
Full Changelog: DapperLib/Dapper@2.1.66...2.1.72
fluentassertions/fluentassertions (FluentAssertions)
v7.2.2Compare Source
What's Changed
Fixes
"{}"is used as a dictionary key by @dennisdoomen in #3173WithTracingis safe when used withBeEquivalentToglobally by @dennisdoomen in #3173AssertionResultSetfixes from #3100 by @jnyrup in #3173Building
Full Changelog: fluentassertions/fluentassertions@7.2.1...7.2.2
v7.2.1Compare Source
What's Changed
Fixes
Full Changelog: fluentassertions/fluentassertions@7.2.0...7.2.1
grpc/grpc-dotnet (Grpc.AspNetCore)
v2.80.0What's Changed
New Contributors
Full Changelog: grpc/grpc-dotnet@v2.76.0...v2.80.0
v2.76.0What's Changed
New Contributors
Full Changelog: grpc/grpc-dotnet@v2.71.0...v2.76.0
npgsql/npgsql (Npgsql)
v9.0.5v9.0.5 contains several minor bug fixes.
Milestone issues
Full Changelog: npgsql/npgsql@v9.0.4...v9.0.5
v9.0.4v9.0.4 contains several minor bug fixes.
Milestone issues
Full Changelog: npgsql/npgsql@v9.0.3...v9.0.4
open-telemetry/opentelemetry-dotnet (OpenTelemetry)
v1.16.0Release details: 1.16.0
10 million values.
BaggagePropagatorto correctly follow Key and Value Encoding rules.TraceContextPropagatorto deduplicate duplicatetracestatekeys.ObservedTimestampwill now be exported for logs in the console exporter.NullReferenceExceptionwhen exporting OTLP logs if the scope key isnull.
storage retry.
OtlpLogExporterintegration withIHttpClientFactory.IHttpClientFactorywhen mTLS isenabled.
Retry-Afterresponse headers that specify a date instead of a delay.observed_time_unix_nanowill no longer always be identical totime_unix_nanowhen using the logs bridge API.
Nameagainst the instrument namesyntax.
OTEL_BSP_*andOTEL_BLRP_*environment variables.collection cycle.
ExemplarReservoirimplementations.LoggerProviderto fail toresolve when one of its dependencies depends on
ILoggerorILoggerFactory.v1.15.3Release details: 1.15.3
tracestateparsing to reject keys that do notbegin with a lowercase letter, including keys beginning with digits, to
align with the W3C Trace Context specification.
Disk retry now requires
OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATHwhen
OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=diskis configured.OtlpLogExporternow usesIHttpClientFactoryon .NET 8+.OTEL_SPAN_ATTRIBUTE_VALUE_LENGTH_LIMITnot being applied.BaggagePropagatorto trim optional whitespace (OWS) around=separators when parsing the
baggageheader.BaggagePropagatorto strip baggage properties from values whenparsing the
baggageheader.LogRecord.LogLevelto preserveLogLevel.None.OTEL_TRACES_SAMPLER_ARGhandling for out-of-range values.traces storage directory.
serialization.
v1.15.2Release details: 1.15.2
export fails and error logging is enabled.
BatchExportProcessorandPeriodicExportingMetricReaderto enable the OpenTelemetry SDK to workin single-threaded WebAssembly environments such as Blazor and
Uno Platform.
v1.15.1Release details: 1.15.1
treats baggage names and values as case sensitive, aligning with the latest
Baggage API specification.
OpenTelemetry.ApiandOpenTelemetrySDK,including fixes for thread-safety, sampler edge cases, metrics precision,
and observable instrument lifecycle handling.
v1.15.0Release details: 1.15.0
ActivitySource.TelemetrySchemaUrland
Meter.TelemetrySchemaUrlproperties across exporters.CA certificate options).
OpenTelemetry.Exporter.Zipkinis deprecated and will stop receiving updatesin December 2026. Zipkin already supports OTLP ingestion.
Migrate to
OpenTelemetry.Exporter.OpenTelemetryProtocolas statedin the Deprecating Zipkin Exporter blog post.
v1.14.0Release details: 1.14.0
net8.0, the package now depends on version8.0.0of theMicrosoft.Extensions.DependencyInjection.Abstractions,Microsoft.Extensions.Diagnostics.Abstractions,Microsoft.Extensions.Hosting.AbstractionsandMicrosoft.Extensions.Logging.ConfigurationNuGet packages.System.Diagnostics.DiagnosticSourcedependency to10.0.0for all target frameworks.
Microsoft.Extensions.*dependencies to10.0.0for .NET Framework and .NET Standard.
(
.sigstore.json) for digital signatures instead of separate signature(
.sig) and certificate (.pem) files. This requires cosign 3.0 or laterfor verification. See the Digital signing
section for updated verification instructions.
v1.13.1Release details: 1.13.1
1.13.0, the digital signature (.dll-keyless.sig) andcertificate (
.dll-keyless.pem) files were unintentionally omitted from thepublished NuGet packages.
(
net462,netstandard2.0,netstandard2.1,net8.0,net9.0), ensuringthe integrity of DLL verification using Sigstore cosign.
v1.13.0Release details: 1.13.0
OtlpExportProtocol.Grpcnow set the
TE=trailersHTTP request header to improve interoperability.EventNameis now exported by default asEventNameinstead oflogrecord.event.namewhen specified throughILoggeror the experimentallog bridge API.
rabbitmq/rabbitmq-dotnet-client (RabbitMQ.Client)
v7.2.1Full Changelog
Fixed bugs:
_confirmSemaphorebroken by cancelled CancellationToken allows concurrent access, corrupts_nextPublishSeqNo; #1900Closed issues:
Merged pull requests:
actions-up#1886 (lukebakken)v7.2.0Full Changelog
Implemented enhancements:
IReadOnlyBasicProperties, IAmqpHeadergeneric type constraints inIChannel.BasicPublishAsync()with a single interface constraint. #1813Fixed bugs:
Closed issues:
RabbitMQ.Client.OAuth22.0.0#1727Merged pull requests:
basic.returnmessages. #1832 (lukebakken)SemaphoreFullException#1819 (lukebakken)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 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 the `RedisCConfiguration
📅 Schedule: (UTC)
🚦 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.