Skip to content

Bump OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.16.0 to 1.17.0 - #47

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/OpenTelemetry.Exporter.OpenTelemetryProtocol-1.17.0
Closed

Bump OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.16.0 to 1.17.0#47
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/OpenTelemetry.Exporter.OpenTelemetryProtocol-1.17.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.16.0 to 1.17.0.

Release notes

Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.

1.17.0

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

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

... (truncated)

1.17.0-rc.1

The following changes are from the previous release 1.16.0.

  • NuGet: OpenTelemetry v1.17.0-rc.1

    • Fixed a metric point reclaim data race on CPU ARM architectures.
      (#​7401)

    • The library is now marked as trim and AOT compatible.
      (#​7441)

    • Replaced the vendored copy of
      EnvironmentVariablesConfigurationProvider with a direct
      Microsoft.Extensions.Configuration.EnvironmentVariables package dependency.
      Consumers gain automatic pickup of upstream bug fixes and security patches;
      no public API or behavioural change.
      (#​7146)

    • Added a verbose OpenTelemetry-Sdk self-diagnostics event that is emitted
      when an activity is dropped because its local (in-process) parent is not
      recorded.
      (#​7427)

    • Added support for a Schema URL on Resource instances.
      (#​7472)

    • Fixed a metric storage leak that occurred when meters and instruments were
      repeatedly created and disposed.
      (#​7466)

    • Added ExcludedTagKeys property to MetricStreamConfiguration to support
      excluding specific tag keys from metric streams.
      (#​7373)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.17.0-rc.1

    • Fixed TraceContextPropagator to normalize empty tracestate header values
      to null when extracting trace context.
      (#​7407,
      #​7433)

    • The library is now marked as trim and AOT compatible.
      (#​7441)

    • Experimental (pre-release builds only): Updated EnvironmentVariableCarrier.Get
      to read only the normalized environment variable name, following the updated
      environment variable carrier specification.
      Non-normalized carrier keys are no longer matched, even when they would
      normalize to the requested key.
      ... (truncated)

1.17.0-beta.1

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

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

    • Added a verbose-level diagnostic event for ignored metrics.
      (#​7429)

    • The library is now marked as trim and AOT compatible.
      (#​7441)

    • Fix double unit suffixes in metric names when using OpenMetrics.
      (#​7454)

    • Fix incorrect handling of leading digits in metric names for OpenMetrics.
      (#​7454)

    • Add PrometheusAspNetCoreOptions.ScopeInfoEnabled property to enable or
      disable scope labels in Prometheus metrics. Defaults to true.
      (#​7436)

    • Added support for the dots and values Prometheus UTF-8 name escaping
      schemes when negotiated via the Accept header.
      (#​7439)

    • Add PrometheusAspNetCoreOptions.TargetInfoEnabled property to enable or
      disable the target_info metric in Prometheus metrics. Defaults to true.
      (#​7438)

    • Added support for the allow-utf-8 Prometheus UTF-8 name escaping scheme
      when negotiated via the Accept header.
      (#​7440)

    • Add PrometheusAspNetCoreOptions.ResourceConstantLabels property to select
      resource attributes to add to each metric as constant labels. Defaults to
      null (no resource attributes are added as metric labels).
      (#​7471)

    • Add PrometheusAspNetCoreOptions.MaxScrapeResponseSizeBytes to configure
      the maximum size of a scrape response. The default is now ~166 MiB.
      (#​7487)

    • A scrape whose serialized output exceeds the maximum scrape response size
      limit now responds with HTTP 500.
      (#​7487)

    • Fixed the Prometheus text exposition format emitting redundant comments.
      (#​7491)

    • Made Accept header content negotiation consistent with the
      PrometheusHttpListener endpoint.
      ... (truncated)

Commits viewable in compare view.

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot
Bump OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.16.0 to 1.17.0
b65e90e 
---
updated-dependencies:
- dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol
  dependency-version: 1.17.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

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 Jul 18, 2026
@github-actions

github-actions Bot commented Jul 18, 2026

Copy link
Copy Markdown

Test Results

330 tests  ±0   330 ✅ ±0   1m 0s ⏱️ -2s
  4 suites ±0     0 💤 ±0 
  4 files   ±0     0 ❌ ±0 

Results for commit b65e90e. ± Comparison against base commit 466f962.

@xavierjohn xavierjohn mentioned this pull request Aug 18, 2026
Merged
xavierjohn added a commit that referenced this pull request Aug 18, 2026
@xavierjohn
Apply open dependency bumps and rename publish workflows after their …
b7b48bb 
…destination (#54)

* Apply open dependency bumps (setup-dotnet v6, OpenTelemetry 1.17.0, nbgv 3.10.91)

Consolidates the four open Dependabot PRs (#43, #47, #48, #51). Two of them
could not be merged as proposed without leaving the tree in a state the
existing version-policy comment explicitly forbids, so they are applied
together with the rest of their package set.

OpenTelemetry -> 1.17.0 (supersedes #47 and #48).
  #47 bumped only Exporter.OpenTelemetryProtocol and #48 only
  Instrumentation.Runtime. Taking either alone would split the set: the
  comment in Directory.Packages.props records that core (Exporter +
  Extensions.Hosting) tracks a single line, so moving Exporter to 1.17.0
  while Extensions.Hosting stayed at 1.16.0 would violate it.

  A matching 1.17.0 now exists for ALL five packages (verified against
  nuget.org), so the whole set is unified. This also clears pre-existing
  drift: Instrumentation.Runtime was still on 1.15.1 while
  Instrumentation.AspNetCore and .Http had already moved to 1.16.0 --
  which the comment claimed was not the case. The comment is rewritten to
  describe the actual policy: unify when a matching release exists across
  the set, and let contrib packages sit on their own latest when they lag,
  rather than forcing a lockstep version that has no matching release.

Nerdbank.GitVersioning 3.10.85 -> 3.10.91 (#43).
  Verified the version scheme is unaffected: packing still yields
  0.1.0-alpha.70.g7f3861c59d computed from the head commit.

actions/setup-dotnet v5 -> v6 (#51).
  All four workflows use the global-json-file input, which is unchanged
  across the major, so the bump is uniform.

Build clean, 352 tests passing.

* Rename publish workflows after their destination

Mirrors the same change made in the framework repo (xavierjohn/Trellis#700).

publish.yml       -> publish-nuget-org.yml        "Publish to NuGet.org"
publish-alpha.yml -> publish-github-packages.yml  "Publish to GitHub Packages"

Both workflows publish the same version; the only real difference is the
feed they push to. The old names implied the distinction was stable vs
alpha, so picking the right one from the Actions list meant opening the
file to check which feed it targeted. Naming them after the destination
removes that step. Cross-references in the header comments were updated to
match.

Also drops an inert flag from the GitHub Packages workflow:
--version-suffix "alpha.${{ github.run_number }}" is silently ignored,
because nbgv sets PackageVersion explicitly. Verified by packing with
--version-suffix "alpha.999" and still getting 0.1.0-alpha.71.gb09de4b2d0.
Since it never had any effect, the step is just "Pack" now.

Renaming a workflow file detaches its run history under the old name in
the Actions UI. That is expected and cosmetic.

Stacked on chore/dependency-bumps (#54) because that PR also edits both of
these files; merge #54 first to avoid a rename/modify conflict.
@dependabot @github

dependabot Bot commented on behalf of github Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/nuget/OpenTelemetry.Exporter.OpenTelemetryProtocol-1.17.0 branch August 18, 2026 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants