Skip to content

Update nuget#729

Open
projectorigin-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nuget
Open

Update nuget#729
projectorigin-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nuget

Conversation

@projectorigin-renovate

@projectorigin-renovate projectorigin-renovate Bot commented Sep 26, 2025

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
Dapper nuget patch 2.1.662.1.79
FluentAssertions (source) nuget patch 7.2.07.2.2
Google.Protobuf nuget minor 3.32.13.35.1
Grpc.AspNetCore nuget minor 2.71.02.80.0
Grpc.Tools nuget minor 2.72.02.81.1
Npgsql nuget patch 9.0.39.0.5
Npgsql.OpenTelemetry nuget patch 9.0.39.0.5
OpenTelemetry (source) nuget minor 1.12.01.16.0
OpenTelemetry.Exporter.Console (source) nuget minor 1.12.01.16.0
OpenTelemetry.Exporter.OpenTelemetryProtocol (source) nuget minor 1.12.01.16.0
OpenTelemetry.Extensions.Hosting (source) nuget minor 1.12.01.16.0
OpenTelemetry.Instrumentation.AspNetCore (source) nuget minor 1.12.01.16.0
OpenTelemetry.Instrumentation.Runtime (source) nuget minor 1.12.01.15.1
RabbitMQ.Client (source) nuget minor 7.1.27.2.1
StackExchange.Redis (source) nuget minor 2.9.172.13.17
Swashbuckle.AspNetCore nuget patch 9.0.49.0.6
System.IdentityModel.Tokens.Jwt nuget minor 8.14.08.19.1
dbup-postgresql (source) nuget minor 6.0.36.1.5
dotnet-grpc nuget minor 2.71.02.80.0
xunit.runner.visualstudio nuget patch 3.1.43.1.5

Release Notes

DapperLib/Dapper (Dapper)

v2.1.79

Compare Source

What's Changed

New Contributors

Full Changelog: DapperLib/Dapper@2.1.72...2.1.79

v2.1.72

Compare Source

What's Changed

New Contributors

Full Changelog: DapperLib/Dapper@2.1.66...2.1.72

fluentassertions/fluentassertions (FluentAssertions)

v7.2.2

Compare Source

What's Changed
Fixes
Building

Full Changelog: fluentassertions/fluentassertions@7.2.1...7.2.2

v7.2.1

Compare Source

What's Changed
Fixes

Full Changelog: fluentassertions/fluentassertions@7.2.0...7.2.1

grpc/grpc-dotnet (Grpc.AspNetCore)

v2.80.0

What's Changed
New Contributors

Full Changelog: grpc/grpc-dotnet@v2.76.0...v2.80.0

v2.76.0

What's Changed
New Contributors

Full Changelog: grpc/grpc-dotnet@v2.71.0...v2.76.0

npgsql/npgsql (Npgsql)

v9.0.5

v9.0.5 contains several minor bug fixes.

Milestone issues

Full Changelog: npgsql/npgsql@v9.0.4...v9.0.5

v9.0.4

v9.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.0

Release details: 1.16.0

  • Breaking Change Explicit histogram boundaries no longer allow more than
    10 million values.
  • Fix BaggagePropagator to correctly follow Key and Value Encoding rules.
  • Add support for the W3C randomness flag.
  • Fixed TraceContextPropagator to deduplicate duplicate tracestate keys.
  • ObservedTimestamp will now be exported for logs in the console exporter.
  • Fixed NullReferenceException when exporting OTLP logs if the scope key is
    null.
  • Added opt-in support for gzip compression to the OTLP exporter.
  • Fixed OTLP disk retry data being stored incorrectly when using persistent
    storage retry.
  • Fixed OtlpLogExporter integration with IHttpClientFactory.
  • Do not enable the OTLP integration with IHttpClientFactory when mTLS is
    enabled.
  • Handle Retry-After response headers that specify a date instead of a delay.
  • observed_time_unix_nano will no longer always be identical to time_unix_nano
    when using the logs bridge API.
  • Stop validating View-provided metric stream Name against the instrument name
    syntax.
  • Fix incorrect validation of OTEL_BSP_* and OTEL_BLRP_* environment variables.
  • Fix observable instrument callbacks running once per reader instead of once per
    collection cycle.
  • Added exception safety for user-supplied ExemplarReservoir implementations.
  • Fixed a circular reference which could cause a LoggerProvider to fail to
    resolve when one of its dependencies depends on ILogger or ILoggerFactory.

v1.15.3

Release details: 1.15.3

  • 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.

v1.15.2

Release details: 1.15.2

  • 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.

v1.15.1

Release details: 1.15.1

  • 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.

v1.15.0

Release details: 1.15.0

  • 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.

v1.14.0

Release details: 1.14.0

  • Add support for .NET 10.0.
  • 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.

v1.13.1

Release details: 1.13.1

  • 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.

v1.13.0

Release details: 1.13.0

  • gRPC calls to export traces, logs, and metrics using OtlpExportProtocol.Grpc
    now set the TE=trailers HTTP request header to improve interoperability.
  • EventName is now exported by default as EventName instead of
    logrecord.event.name when specified through ILogger or the experimental
    log bridge API.
rabbitmq/rabbitmq-dotnet-client (RabbitMQ.Client)

v7.2.1

Full Changelog

Fixed bugs:

  • The Channel has been closed exception from HeartBeatReadCallback #​1884
  • Publisher confirms: _confirmSemaphore broken by cancelled CancellationToken allows concurrent access, corrupts _nextPublishSeqNo; #​1900
  • Auto-recovery attempts to restore bindings to deleted queues causing recovery failures #​1905

Closed issues:

  • Closing Channel does NOT remove the cached RecordedBinding, which will cause AutoRecovery fail #​1904

Merged pull requests:

v7.2.0

Full Changelog

Implemented enhancements:

  • Add support for SslStreamCertificateContext in SslOption #​1864
  • Consider including MessageId tag in RabbitMQActivitySource during BasicPublish #​1849
  • Consider allowing to set remote span as parent instead of link when propagating context via RabbitMQ #​1666
  • Make ConnectionFactory a real Factory pattern #​1844
  • Release an abstractions package #​1833
  • 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
  • Memory leak in Connection SharedArraypool #​1817
  • AutorecoveringConnection Memory Leak #​1808

Closed issues:

  • Ship public API changes #​1834
  • Update v7 migration guide #​1724
  • IConnectionFactory does not contain properties that are present in the class and are needed to correctly configure the connection. #​1836
  • Unexpected AMQP close-reason, initiated by Peer, code=504, text='CHANNEL_ERROR - expected 'channel.open' #​1835
  • Ship RabbitMQ.Client.OAuth2 2.0.0 #​1727

Merged pull requests:

StackExchange/StackExchange.Redis (StackExchange.Redis)

v2.13.17

Compare Source

What's Changed

New Contributors

Full Changelog: StackExchange/StackExchange.Redis@2.13.10...2.13.17

v2.13.10

Compare 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

Full Changelog: StackExchange/StackExchange.Redis@2.13.1...2.13.10

v2.13.1

Compare 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:

  • the purpose of RESP3
  • scenarios where RESP2 vs RESP3 may be visible
  • how to explicitly choose to remain on RESP2
  • notes on additional libraries such as NRedisStack

What's Changed

Full Changelog: StackExchange/StackExchange.Redis@2.12.27...2.13.1

v2.12.14

Compare Source

What's Changed

Impact: "high" if using cluster and high-integrity-mode together (resolves an issue that can mis-report -MOVED responses as integrity failures)

NuGet link

New Contributors

Full Changelog: StackExchange/StackExchange.Redis@2.12.8...2.12.14

v2.12.8

Compare Source

What's Changed

Full Changelog: StackExchange/StackExchange.Redis@2.12.4...2.12.8

v2.12.4

Compare Source

What's Changed

Full Changelog: StackExchange/StackExchange.Redis@2.12.1...2.12.4

v2.12.1

Compare Source

What's Changed

Full Changelog: StackExchange/StackExchange.Redis@2.11.8...2.12.1

v2.11.8

Compare Source

What's Changed

New Contributors

Full Changelog: StackExchange/StackExchange.Redis@2.11.3...2.11.8

v2.11.3

Compare Source

What's Changed

Full Changelog: StackExchange/StackExchange.Redis@2.11.0...2.11.3

v2.11.0

Compare Source

get 2.11.0 on NuGet

What's Changed

For Redis 8.6:

The 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.14

Compare 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

New Contributors

Full Changelog: StackExchange/StackExchange.Redis@2.10.1...2.10.14

v2.10.1

Adds support for Redis 8.4 features

  • 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.

What's Changed

Full Changelog: StackExchange/StackExchange.Redis@2.9.32...2.10.1

v2.9.32

Compare Source

What's Changed

Full Changelog: StackExchange/StackExchange.Redis@2.9.25...2.9.32

v2.9.25

Compare 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.24

Compare Source

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

This PR has been generated by Mend Renovate.

@projectorigin-renovate projectorigin-renovate Bot enabled auto-merge (squash) September 26, 2025 14:14
@projectorigin-renovate projectorigin-renovate Bot changed the title Update dependency StackExchange.Redis to 2.9.24 Update dependency xunit.runner.visualstudio to 3.1.5 Sep 29, 2025
@projectorigin-renovate projectorigin-renovate Bot changed the title Update dependency xunit.runner.visualstudio to 3.1.5 Update nuget Sep 29, 2025
@sonarqubecloud

sonarqubecloud Bot commented May 1, 2026

Copy link
Copy Markdown

@projectorigin-renovate

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@sonarqubecloud

Copy link
Copy Markdown

2 similar comments
@sonarqubecloud

Copy link
Copy Markdown

@sonarqubecloud

Copy link
Copy Markdown

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants