Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 12, 2024

This PR contains the following updates:

Package Change Age Confidence
OpenTelemetry.Exporter.InMemory (source) 1.9.0 -> 1.13.1 age confidence
OpenTelemetry.Extensions.Hosting (source) 1.9.0 -> 1.13.1 age confidence

Release Notes

open-telemetry/opentelemetry-dotnet (OpenTelemetry.Exporter.InMemory)

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.

v1.12.0

Release details: 1.12.0

  • Breaking Change: OpenTelemetry.Exporter.OpenTelemetryProtocol now
    defaults to using OTLP/HTTP instead of OTLP/gRPC when targeting .NET Framework
    and .NET Standard. This change may cause telemetry export to fail unless
    appropriate adjustments are made. Explicitly setting OTLP/gRPC may result in a
    NotSupportedException unless further configuration is applied. See
    #​6209 for
    full details and mitigation guidance. #​6229

v1.11.1

Release details: 1.11.1

  • Fixed a bug preventing OpenTelemetry.Exporter.OpenTelemetryProtocol from
    exporting telemetry on .NET Framework.

v1.11.0

Release details: 1.11.0

  • OpenTelemetry.Exporter.OpenTelemetryProtocol no longer depends on the
    Google.Protobuf, Grpc, or Grpc.Net.Client packages. Serialization and
    transmission of outgoing data is now performed manually to improve the overall
    performance.

v1.10.0

Release details: 1.10.0

  • Bumped the package versions of System.Diagnostic.DiagnosticSource and other
    Microsoft.Extensions.* packages to 9.0.0.

  • Added support for new APIs introduced in System.Diagnostics.DiagnosticSource
    9.0.0:

  • Experimental features promoted to stable:

    • CardinalityLimit can now be managed for individual metrics via the View
      API. For details see: Changing cardinality limit for a
      Metric
      .

    • The overflow
      attribute

      (otel.metric.overflow) behavior is now enabled by default. The
      OTEL_DOTNET_EXPERIMENTAL_METRICS_EMIT_OVERFLOW_ATTRIBUTE environment
      variable is no longer required. For details see: Cardinality
      Limits
      .

    • The MetricPoint reclaim behavior is now enabled by default when Delta
      aggregation temporality is used. The
      OTEL_DOTNET_EXPERIMENTAL_METRICS_RECLAIM_UNUSED_METRIC_POINTS environment
      variable is no longer required. For details see: Cardinality
      Limits
      .

  • Added OpenTelemetrySdk.Create API for configuring OpenTelemetry .NET signals
    (logging, tracing, and metrics) via a single builder. This new API simplifies
    bootstrap and teardown, and supports cross-cutting extensions targeting
    IOpenTelemetryBuilder.

  • Removed out of support net6.0 target and added net9.0 target.


Configuration

📅 Schedule: 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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) November 12, 2024 22:34
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to 1.10.0 chore(deps): update opentelemetry-dotnet monorepo to 1.11.0 Jan 16, 2025
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from 1a5d07d to 52f3ac9 Compare January 16, 2025 04:28
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to 1.11.0 chore(deps): update opentelemetry-dotnet monorepo to 1.11.1 Jan 23, 2025
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from 52f3ac9 to c43bc80 Compare January 23, 2025 04:28
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from c43bc80 to 2ee3fbd Compare March 4, 2025 23:36
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to 1.11.1 chore(deps): update opentelemetry-dotnet monorepo to 1.11.2 Mar 4, 2025
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from 2ee3fbd to 9150840 Compare April 30, 2025 03:35
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to 1.11.2 chore(deps): update opentelemetry-dotnet monorepo to 1.12.0 Apr 30, 2025
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from 9150840 to 47a06be Compare October 1, 2025 21:23
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to 1.12.0 chore(deps): update opentelemetry-dotnet monorepo to 1.13.0 Oct 1, 2025
@renovate renovate bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from 47a06be to c16ca7c Compare October 9, 2025 18:37
@renovate renovate bot changed the title chore(deps): update opentelemetry-dotnet monorepo to 1.13.0 chore(deps): update opentelemetry-dotnet monorepo to 1.13.1 Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant