Skip to content

Bump the nuget group with 17 updates - #109

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/nuget/nuget-62872e322b
Open

dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/nuget/nuget-62872e322b

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Updated AWSSDK.S3 from 4.0.104.11 to 4.1.0.

Release notes

Sourced from AWSSDK.S3's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.Authentication.OpenIdConnect from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.Authentication.OpenIdConnect's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.DataProtection.EntityFrameworkCore from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.DataProtection.EntityFrameworkCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.Mvc.Testing from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.Mvc.Testing's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.OpenApi from 10.0.11 to 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.OpenApi's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.EntityFrameworkCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore.Design from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.EntityFrameworkCore.Design's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore.Relational from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.EntityFrameworkCore.Relational's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore.Tools from 10.0.14 to 11.0.0.

Release notes

Sourced from Microsoft.EntityFrameworkCore.Tools's releases.

10.0.404

You can build .NET 10.0 from the repository by cloning the release tag v10.0.404 and 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

Important

Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.404-servicing.26529.119.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID 2001:2001, while GitHub’s automatically generated archives use 0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.

10.0.403

You can build .NET 10.0 from the repository by cloning the release tag v10.0.403 and 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

10.0.402

You can build .NET 10.0 from the repository by cloning the release tag v10.0.402 and 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

10.0.401

Release

What's Changed

... (truncated)

10.0.400

You can build .NET 10.0 from the repository by cloning the release tag v10.0.400 and 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

10.0.303

You can build .NET 10.0 from the repository by cloning the release tag v10.0.303 and 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

10.0.302

You can build .NET 10.0 from the repository by cloning the release tag v10.0.302 and 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

10.0.301

You can build .NET 10.0 from the repository by cloning the release tag v10.0.301 and 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

10.0.300

You can build .NET 10.0 from the repository by cloning the release tag v10.0.300 and 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

10.0.204

You can build .NET 10.0 from the repository by cloning the release tag v10.0.204 and 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

10.0.203

You can build .NET 10.0 from the repository by cloning the release tag v10.0.203 and 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

10.0.202

You can build .NET 10.0 from the repository by cloning the release tag v10.0.202 and 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

10.0.201

You can build .NET 10.0 from the repository by cloning the release tag v10.0.201 and 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

10.0.200

You can build .NET 10.0 from the repository by cloning the release tag v10.0.200 and 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

10.0.115

You can build .NET 10.0 from the repository by cloning the release tag v10.0.115 and 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

Important

Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.115-servicing.26529.108.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signature was generated from a build-produced source archive with ownership normalized to UID/GID 2001:2001, while GitHub’s automatically generated archive uses 0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.

10.0.114

You can build .NET 10.0 from the repository by cloning the release tag v10.0.114 and 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

Important

Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.114-servicing.26522.126.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID 2001:2001, while GitHub’s automatically generated archives use 0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.

10.0.113

You can build .NET 10.0 from the repository by cloning the release tag v10.0.113 and 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

10.0.112

You can build .NET 10.0 from the repository by cloning the release tag v10.0.112 and 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

10.0.111

You can build .NET 10.0 from the repository by cloning the release tag v10.0.111 and 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

10.0.110

You can build .NET 10.0 from the repository by cloning the release tag v10.0.110 and 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

10.0.109

You can build .NET 10.0 from the repository by cloning the release tag v10.0.109 and 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

10.0.108

You can build .NET 10.0 from the repository by cloning the release tag v10.0.108 and 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

10.0.107

You can build .NET 10.0 from the repository by cloning the release tag v10.0.107 and 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

10.0.106

You can build .NET 10.0 from the repository by cloning the release tag v10.0.106 and 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

10.0.105

You can build .NET 10.0 from the repository by cloning the release tag v10.0.105 and 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

10.0.104

You can build .NET 10.0 from the repository by cloning the release tag v10.0.104 and 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

10.0.103

You can build .NET 10.0 from the repository by cloning the release tag v10.0.103 and 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 is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

10.0.102-sb1

You can build .NET 10.0 from the repository by cloning the release tag v10.0.102-sb1 and 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

10.0.101

You can build .NET 10.0 from the repository by cloning the release tag v10.0.101 and 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

10.0.100

You can build .NET 10.0 from the repository by cloning the release tag v10.0.100 and 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

To produce artifacts with the .NET 10 GA version strings, users must pass the branding argument to the build: --branding rtm.

10.0.100-rc.2.25502.107

You can build .NET 10.0 RC 2 from the repository by cloning the release tag v10.0.100-rc.2.25502.107 and 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

Note: GitHub automatically generates the "Source code (tar.gz/zip)" archives included in this release. Please download the official source code from:

10.0.100-rc.1.25451.107

You can build .NET 10.0 RC 1 from the repository by cloning the release tag v10.0.100-rc.1.25451.107 and 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

10.0.100-preview.7.25380.108

You can build .NET 10.0 Preview 7 from the repository by cloning the release tag v10.0.100-preview.7.25380.108 and 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

Commits viewable in compare view.

Updated Microsoft.Extensions.TimeProvider.Testing from 10.11.0 to 11.0.0.

Release notes

Sourced from Microsoft.Extensions.TimeProvider.Testing's releases.

11.0.0

Version 11.0.0 ships alongside .NET 11 and with net11 targets added to packages. Highlights of this release include new experimental Documents and Document Extraction abstractions, metric instrument descriptions, and a sliding-window retry budget for HTTP resilience.

Experimental API Changes

Now Stable

  • HTTP server latency telemetry (AddHttpServerLatencyTelemetry) APIs are now stable (previously EXTEXP0013) #​7898

New Experimental APIs

  • New experimental API: Documents abstractions in the new Microsoft.Extensions.Documents.Abstractions package (EXTEXP0019) #​7835
  • New experimental API: Document Extraction in the new Microsoft.Extensions.DocumentExtraction and Microsoft.Extensions.DocumentExtraction.Abstractions packages (MEDE0001) #​7588
  • New experimental API: HTTP resilience retry budget (HttpRetryBudgetOptions, HttpRetryResiliencePipelineBuilderExtensions, OnRetryBudgetExhaustedArguments) (EXTEXP0001) #​7867
  • New experimental API: Description on metric attributes (EXTEXP0003) #​7837

Obsoleted APIs

  • HybridCacheOptions.DisableCompression is now obsolete (EXTOBS0003) #​7885

What's Changed

Telemetry and Logging

  • Add Description to metric attributes and describe all instruments #​7837 by @​evgenyfedorov2 (co-authored by @​Copilot)
  • Capture trace context, thread ID and message template in buffered logs #​7818 by @​evgenyfedorov2 (co-authored by @​Copilot)
  • Allow bool and numeric types for strongly-typed metric tags #​7877 by @​evgenyfedorov2 (co-authored by @​Copilot)
  • Fix route parameter redaction when a parameter value contains a delimiter used later in the same path segment #​7828 by @​evgenyfedorov2 (co-authored by @​Copilot)
  • Fix lost log records when logging reentrantly on the same thread #​7847 by @​evgenyfedorov2 (co-authored by @​Copilot)
  • Fix logging generator stack overflow on type cycles #​7861 by @​evgenyfedorov2 (co-authored by @​Copilot)
  • Honor [LogPropertyIgnore] during transitive logging and [LogProperties(Transitive = true)] on properties #​7868 by @​evgenyfedorov2 (co-authored by @​Copilot)
  • Make DataClassificationSet static to decrease allocations #​7874 by @​evgenyfedorov2 (co-authored by @​Copilot)

Caching

  • Add HybridCache.GetOrCreateAsync overloads for dynamic setting of options #​7568 by @​svick (co-authored by @​Copilot)
  • Mark HybridCacheOptions.DisableCompression as obsolete #​7885 by @​slang25
  • Fix HybridCache stampede state removal race #​7814 by @​svick (co-authored by @​Copilot)
  • Fix HybridCache reservation over-release on DisableUnderlyingData miss #​7879 by @​Eng3bbas

AI

  • AI: Restore neutral tool approval rejection message #​7913 by @​jozkee (co-authored by @​Copilot)
  • Fix ImageGenerationOptions.Clone dropping StreamingCount #​7829 by @​Empiree
  • Fix evaluation context serialization without reflection fallback #​7869 by @​valkiara
  • Pin MessagePack 2.5.307 in AI template AppHost project #​7853 by @​evgenyfedorov2 (co-authored by @​Copilot)

Packaging and Target Frameworks

  • Condition framework-provided package references for .NET 11 #​7915 by @​jeffhandley (co-authored by @​Copilot)
    ... (truncated)

Commits viewable in compare view.

Updated OpenTelemetry.Extensions.Hosting from 1.17.0 to 1.21.0.

Release notes

Sourced from OpenTelemetry.Extensions.Hosting's releases.

1.21.0

For highlights and announcements pertaining to this release see: Release Notes > 1.21.0.

The following changes are from the previous release 1.21.0-rc.2.

1.21.0-rc.2

The following changes are from the previous release 1.21.0-rc.1.

  • NuGet: OpenTelemetry v1.21.0-rc.2

    • Fixed an exception when downscaling empty exponential histogram buckets after
      a reset.
      (#​8064)

    • Fixed tracing callbacks continuing after provider shutdown or disposal on older
      target frameworks.
      (#​8065)

    • Fixed initialization failures when environment variable access is denied.
      Configuration reloads retain the last successful values when access is denied.
      (#​8070)

    • Fixed a source, meter or legacy activity name with a trailing line feed
      matching a wildcard pattern which does not end in a wildcard.
      (#​8074)

    • Fixed OTEL_RESOURCE_ATTRIBUTES values being decoded as form data, which
      changed a + to a space. Values are now only percent-decoded, as defined by
      the Resource SDK specification.
      (#​8074)

    • Updated the schema URL of resources created by the SDK to use OpenTelemetry
      Semantic Conventions version 1.45.0.
      (#​8079)

    • Added support for batching the metric points exported by
      PeriodicExportingMetricReader. When a maximum export batch size is set,
      using the new constructor overload or
      PeriodicExportingMetricReaderOptions.MaxExportBatchSize, the metric
      points of each collection are split into batches of at most that many
      metric points, even if that splits up the metric points of a single
      metric. The batches are exported serially with the export timeout
      applying to each export. It can also be configured with the
      OTEL_METRIC_EXPORT_MAX_BATCH_SIZE environment variable.
      (#​8053)

    • Fixed PeriodicExportingMetricReader exporting a collection which was still
      in progress when Shutdown() timed out to its exporter after the exporter
      had been shut down.
      (#​8053)

    • Fixed PeriodicExportingMetricReader not making its final collection when
      Shutdown() was called before its background task had started running on
      platforms where threading is not available, such as browsers.
      (#​8053)

... (truncated)

1.21.0-rc.1

The following changes are from the previous release 1.20.1.

  • NuGet: OpenTelemetry v1.21.0-rc.1

    • Fixed a race in the self-diagnostics sink dispatcher where disposing it
      while its pump thread was exiting could throw ArgumentNullException on
      .NET Framework.
      (#​7983)

    • SelfDiagnosticsOptions is now automatically bound from the
      OpenTelemetry:SelfDiagnostics configuration section, when present.
      (#​8008)

    • Fixed a race where collecting a metric with delta temporality concurrently
      with the creation of a new MetricPoint could reclaim the MetricPoint
      while it was being created, losing the measurement.
      (#​8019)

    • Fixed a race where collecting a metric with delta temporality could export
      the same series twice in a single collection.
      (#​8019)

    • Fixed wildcard matching timeouts that could prevent configured source, meter,
      legacy activity, or metric view patterns from matching.
      (#​8014)

    • The timeout passed to MetricReader.Collect() (for example by
      MeterProvider.ForceFlush()), the ExportTimeoutMilliseconds of
      PeriodicExportingMetricReader and the ExporterTimeoutMilliseconds of
      BatchExportProcessor<T> are now made available to the exporter instead of
      being ignored once the export has started, so that the OTLP exporter can
      cancel an export which runs past the timeout. The ExportTimeoutMilliseconds
      of PeriodicExportingMetricReader now also limits exports which are not
      started by the reader itself, such as those of MeterProvider.ForceFlush().
      (#​7996)

    • Fixed a race where collecting a cumulative metric concurrently with the
      creation of a new MetricPoint could export a MetricPoint that was not yet
      fully initialized, could case a NullReferenceException when enumerating Tags.
      (#​8018)

    • Breaking Change Dropped support for net8.0 and net9.0.
      (#​6899)

    • Add support for .NET 11.0.
      (#​6899)

    • Added support for enabling ActivitySources from configuration using the
      Microsoft.Extensions.Diagnostics tracing APIs introduced in .NET 11 (for
      example, services.AddTracing(b => b.AddConfiguration(section))).
      ... (truncated)

1.21.0-beta.1

The following changes are from the previous release 1.20.1-beta.1.

  • NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.21.0-beta.1

    • Fixed OpenMetrics scrape responses containing a # UNIT line whose unit is
      not an underscore-separated suffix of the metric family name (for example
      auth.failedlogins with the unit logins), which caused scrapers such as
      Prometheus to reject the whole response. The # UNIT line is now omitted
      for such metrics; exported metric names are unchanged.
      (#​7993)

    • Fixed scrapes that negotiate different response formats within the
      ScrapeResponseCacheDurationMilliseconds window each triggering their own
      metrics collection. A collection now also writes the response for other
      formats whose scrapes arrived alongside a previous collection, so scrapes
      that keep arriving together are served from the cache. Fresh cached responses
      remain available while another format is serialized, even if that
      serialization fails.
      (#​7994)

    • Fixed array- and map-valued attributes being serialized as the .NET type
      name (e.g. System.Byte[], System.Int32[]) instead of being JSON-encoded
      as per the specification. byte[]-valued attributes are now
      Base64-encoded, and other array- and map-valued attributes are now
      JSON-encoded.
      (#​7694)

    • Fixed arrays of string-valued key/value pairs being
      serialized as JSON arrays of strings instead of JSON objects.
      (#​7694)

    • Fixed scrape clients which stop reading their response delaying other
      scrapes until ScrapeResponseTimeoutMilliseconds elapses.
      (#​8041)

    • Breaking Change Dropped support for net8.0 and net9.0.
      (#​6899)

    • Add support for .NET 11.0.
      (#​6899)

    • Fixed a scrape response containing the same series (metric name and labels)
      more than once, which causes Prometheus to reject the whole response, such as
      when metric or tag names are the same once escaped, tag names become the same
      when UTF-8 encoded, or the scope information is disabled. Duplicate series are
      now dropped, and a warning event is written.
      A metric which has the name of a sample that is generated for another one
      (for example _sum of a histogram) is now dropped, and a warning event is
      written.
      (#​8076)
      ... (truncated)

1.20.1

For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.

The following changes are from the previous release 1.20.0.

  • NuGet: OpenTelemetry v1.20.1

    • Fixed a possible race condition on ARM64 when multiple threads record the
      first measurement with no tags, or the first overflow measurement, that could
      cause the measurement to be recorded incorrectly.
      (#​7951)

    • Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
      and prefixed JWTs.
      (#​7955)

    • Fixed default HTTP client log filtering when registering the OTLP log exporter
      through OpenTelemetryLoggerOptions.
      (#​7959)

    • Fixed legacy self-diagnostics logging terminating the process when the log
      file is truncated or the log volume runs out of space.
      (#​7956)

    • Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
      instrumentation suppression, which could cause recursive exports or deadlocks.
      (#​7961)

    • Fixed delta double counters losing subsequent measurements after a non-finite
      or large value and idle metric points with a NaN value failing to be reclaimed.
      (#​7963)

    • Improve the assignment of values to exponential histogram buckets when the
      value is near a bucket boundary by using a pre-computed lookup table.
      (#​7911)

    • Fixed LogRecords being returned to the shared pool while still queued for
      export when an exporter stops enumerating a single-item or array
      Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
      on the same provider to export missing or incorrect data.
      (#​7965)

    • Fixed a SuppressInstrumentationScope.Enter() reference count never being
      released when the Activity it was entered for is not recorded, which caused
      all subsequent telemetry in that execution context to be suppressed.
      (#​7966)

    • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
      or SelfDiagnosticsOptions, are now always created as new files.
      (#​7968)

... (truncated)

1.20.1-rc.1

The following changes are from the previous release 1.20.0.

  • NuGet: OpenTelemetry v1.20.1-rc.1

    • Fixed a possible race condition on ARM64 when multiple threads record the
      first measurement with no tags, or the first overflow measurement, that could
      cause the measurement to be recorded incorrectly.
      (#​7951)

    • Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
      and prefixed JWTs.
      (#​7955)

    • Fixed default HTTP client log filtering when registering the OTLP log exporter
      through OpenTelemetryLoggerOptions.
      (#​7959)

    • Fixed legacy self-diagnostics logging terminating the process when the log
      file is truncated or the log volume runs out of space.
      (#​7956)

    • Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
      instrumentation suppression, which could cause recursive exports or deadlocks.
      (#​7961)

    • Fixed delta double counters losing subsequent measurements after a non-finite
      or large value and idle metric points with a NaN value failing to be reclaimed.
      (#​7963)

    • Improve the assignment of values to exponential histogram buckets when the
      value is near a bucket boundary by using a pre-computed lookup table.
      (#​7911)

    • Fixed LogRecords being returned to the shared pool while still queued for
      export when an exporter stops enumerating a single-item or array
      Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
      on the same provider to export missing or incorrect data.
      (#​7965)

    • Fixed a SuppressInstrumentationScope.Enter() reference count never being
      released when the Activity it was entered for is not recorded, which caused
      all subsequent telemetry in that execution context to be suppressed.
      (#​7966)

    • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
      or SelfDiagnosticsOptions, are now always created as new files.
      (#​7968)

    • Self-diagnostics messages written to the sinks configured by
      SelfDiagnosticsOptions are now truncated to 16,384 characters so that the
      ... (truncated)

1.20.1-beta.1

The following changes are from the previous release 1.20.0-beta.1.

  • NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.1-beta.1

    • Fixed scrape responses being handed to the server in a single write, which
      made the server buffer a full copy of the response for each client that did
      not read it until the request completed or timed out. Responses are now
      written in bounded slices so the server's back-pressure applies.
      (#​7957)

    • Fixed startup scrapes permanently omitting target_info and configured
      resource constant labels from subsequent scrape responses.
      (#​7984)

    • Updated OpenTelemetry core component version(s) to 1.20.1.
      (#​7990)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.1-beta.1

    • Fixed scrape responses being handed to the server in a single write, which
      on Linux and macOS made the listener allocate and hold a full copy of the
      response for each client that did not read it until the request completed or
      timed out. Responses are now written in bounded slices.
      (#​7957)

    • Fixed scrape requests that announce a request body holding a thread pool
      thread after their response had been sent on Linux and macOS for as long as
      the client kept trickling in the body. The connection is now closed after
      responding to a request with a body instead of being kept alive.
      (#​7962)

    • Fixed startup scrapes permanently omitting target_info and configured
      resource constant labels from subsequent scrape responses.
      (#​7984)

    • Updated OpenTelemetry core component version(s) to 1.20.1.
      (#​7990)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Shims.OpenTracing v1.20.1-beta.1

    • Updated OpenTelemetry core component version(s) to 1.20.1.
      (#​7990)

    See CHANGELOG for details.

1.20.0

For highlights and announcements pertaining to this release see: Release Notes > 1.20.0.

The following changes are from the previous release 1.19.1.

  • NuGet: OpenTelemetry v1.20.0

    • Fixed SuppressInstrumentationScope reference counts leaking between inherited asynchronous execution contexts.
      (#​7803)

    • Self-diagnostic features are explicitly disabled on browser-based platforms (e.g. Blazor) and are now non-functional. Previously, attempting to enable self-diagnostics on such platforms would result in an exception at runtime.
      (#​7799)

    • Added TracerProviderBuilder.ConfigureSampler which receives the resolved Sampler whether set programmatically, via OTEL_TRACES_SAMPLER, or by default, and returns a replacement. Intended for library authors who need to influence sampling without overriding a sampler the application has configured.
      (#​7780)

    • Fixed ResourceBuilder.CreateDefault ignoring OTEL_RESOURCE_ATTRIBUTES and OTEL_SERVICE_NAME environment variables when the host IConfiguration does not contain those settings.
      (#​7855)

    • Added improved self-diagnostics logging to improve the support experience. The new SelfDiagnosticsOptions class configures a rolling file sink and a console sink through the standard options pipeline. Sinks are off by default.
      (#​7588)

    • Fixed a race that could incorrectly route a concurrent metric measurement to the overflow point when its tag set was published as the cardinality limit was reached.
      (#​7804)

    • Added OpenTelemetryLoggerOptions.Version and OpenTelemetryLoggerOptions.SchemaUrl options to set an instrumentation library version and schema URL applied to logs emitted via the Microsoft.Extensions.Logging ILogger integration.
      (#​7727)

    • Fixed LogRecord.CategoryName resetting the current Logger's Version to null when set to a new value.
      (#​7727)

    • Bounded the internal cache of Logger scopes keyed by instrumentation to avoid unbounded growth.
      (#​7727)

    • Fixed the MeterProvider and its IServiceProvider being kept alive after the host is disposed when using Microsoft.Extensions.Diagnostics versions prior to 9.0, which never dispose their MetricsSubscriptionManager (and its underlying MeterListener).
      (#​7924)

    • Fixed a race condition between recording a measurement and collecting a histogram with delta temporality that could cause an empty data point (with a count of zero) to be exported in the next collection cycle.
      (#​7923)

    • Improved metric collection performance after metric streams are removed by compacting metric storage during collection.
      (#​7945)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.20.0

    • Added Logger.SchemaUrl and a LoggerProvider.GetLogger overload accepting a schema URL parameter using the new LoggerOptions type.
      (#​7727)

    • Breaking change (pre-release only versions): LoggerProvider's protected TryCreateLogger(string? name, out Logger? logger) extensibility method has been replaced by TryCreateLogger(LoggerOptions options, out Logger? logger). Custom LoggerProvider subclasses that override the previous overload must update to override the new one; the old overload is no longer called.
      ... (truncated)

1.20.0-rc.1

The following changes are from the previous release 1.19.1.

  • NuGet: OpenTelemetry v1.20.0-rc.1

    • Fixed SuppressInstrumentationScope reference counts leaking between inherited asynchronous execution contexts.
      (#​7803)

    • Self-diagnostic features are explicitly disabled on browser-based platforms (e.g. Blazor) and are now non-functional. Previously, attempting to enable self-diagnostics on such platforms would result in an exception at runtime.
      (#​7799)

    • Added TracerProviderBuilder.ConfigureSampler which receives the resolved Sampler whether set programmatically, via OTEL_TRACES_SAMPLER, or by default, and returns a replacement. Intended for library authors who need to influence sampling without overriding a sampler the application has configured.
      (#​7780)

    • Fixed ResourceBuilder.CreateDefault ignoring OTEL_RESOURCE_ATTRIBUTES and OTEL_SERVICE_NAME environment variables when the host IConfiguration does not contain those settings.
      (#​7855)

    • Added improved self-diagnostics logging to improve the support experience. The new SelfDiagnosticsOptions class configures a rolling file sink and a console sink through the standard options pipeline. Sinks are off by default.
      (#​7588)

    • Fixed a race that could ...

Description has been truncated

Bumps AWSSDK.S3 from 4.0.104.11 to 4.1.0
Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.14 to 10.0.15
Bumps Microsoft.AspNetCore.Authentication.OpenIdConnect from 10.0.14 to 10.0.15
Bumps Microsoft.AspNetCore.DataProtection.EntityFrameworkCore from 10.0.14 to 10.0.15
Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.14 to 10.0.15
Bumps Microsoft.AspNetCore.OpenApi from 10.0.11 to 10.0.15
Bumps Microsoft.EntityFrameworkCore from 10.0.14 to 10.0.15
Bumps Microsoft.EntityFrameworkCore.Design from 10.0.14 to 10.0.15
Bumps Microsoft.EntityFrameworkCore.Relational from 10.0.14 to 10.0.15
Bumps Microsoft.EntityFrameworkCore.Tools from 10.0.14 to 11.0.0
Bumps Microsoft.Extensions.TimeProvider.Testing from 10.11.0 to 11.0.0
Bumps OpenTelemetry.Extensions.Hosting from 1.17.0 to 1.21.0
Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.17.0 to 1.21.0
Bumps OpenTelemetry.Instrumentation.Http from 1.17.0 to 1.21.0
Bumps OpenTelemetry.Instrumentation.Runtime from 1.17.0 to 1.21.0
Bumps Scalar.AspNetCore from 2.19.0 to 2.21.0
Bumps TUnit from 1.81.10 to 1.85.0

---
updated-dependencies:
- dependency-name: AWSSDK.S3
  dependency-version: 4.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.AspNetCore.Authentication.OpenIdConnect
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.AspNetCore.DataProtection.EntityFrameworkCore
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.EntityFrameworkCore
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.AspNetCore.Mvc.Testing
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.AspNetCore.OpenApi
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.EntityFrameworkCore.Design
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.EntityFrameworkCore.Relational
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.EntityFrameworkCore.Tools
  dependency-version: 11.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget
- dependency-name: Microsoft.Extensions.TimeProvider.Testing
  dependency-version: 11.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget
- dependency-name: OpenTelemetry.Extensions.Hosting
  dependency-version: 1.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: OpenTelemetry.Instrumentation.AspNetCore
  dependency-version: 1.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: OpenTelemetry.Instrumentation.Http
  dependency-version: 1.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: OpenTelemetry.Instrumentation.Runtime
  dependency-version: 1.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: Scalar.AspNetCore
  dependency-version: 2.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: TUnit
  dependency-version: 1.85.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Nov 16, 2026
@coderabbitai

coderabbitai Bot commented Nov 16, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: cbd92ba3-18ce-4d53-9ebd-7f46f72a3a30

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

This branch has not been deployed

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

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants