Skip to content

Move nonstable semconv opt-ins to preview flag in 3.0#18914

Merged
laurit merged 2 commits into
open-telemetry:mainfrom
trask:semconv-stability
Jun 8, 2026
Merged

Move nonstable semconv opt-ins to preview flag in 3.0#18914
laurit merged 2 commits into
open-telemetry:mainfrom
trask:semconv-stability

Conversation

@trask

@trask trask commented Jun 5, 2026

Copy link
Copy Markdown
Member

Nonstable semconv (xyz) shouldn't be using otel.semconv-stability.opt-in=xyz, since this looks like a stable property per our VERSIONING.md.

Instead we've recently adopted otel.semconv-stability.preview=xyz.

This makes that change for existing usages in 3.0, except for the two semconv which we're planning to stabilize in 3.0: database and code.

Resolves #15849

@trask
trask requested a review from a team as a code owner June 5, 2026 22:41
Copilot AI review requested due to automatic review settings June 5, 2026 22:41

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adjusts semantic convention stability gating in SemconvStability to align opt-in flags with the project’s 3.0 semconv stability policy (stable vs preview), and marks some transitional accessors as deprecated ahead of 3.0 removal.

Changes:

  • Updates service.peer and rpc semconv gating logic (intended: move opt-ins from otel.semconv-stability.opt-in to otel.semconv-stability.preview).
  • Adds @Deprecated markers to several transition-era accessors slated for removal in 3.0.

@laurit
laurit merged commit 18e4a87 into open-telemetry:main Jun 8, 2026
95 checks passed
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.

Update from peer.service to service.peer.name

3 participants