Define the Core packages term#5046
Merged
Merged
Conversation
reyang
reviewed
Apr 23, 2026
pellared
marked this pull request as draft
April 23, 2026 19:19
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Defines and introduces the term “Core packages” in the specification, and updates existing wording to use this term where appropriate.
Changes:
- Adds a “Core Packages” section to the specification overview (and TOC) defining the term.
- Updates references from “Core OpenTelemetry repositories” / “extension packages” to “OpenTelemetry Core packages” in relevant specs.
- Adds a changelog entry documenting the terminology addition.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| specification/trace/sdk.md | Replaces “Core OpenTelemetry repositories” wording with “OpenTelemetry Core packages” for IdGenerator guidance. |
| specification/overview.md | Adds a new “Core Packages” definition section and updates plugin wording to use the new term. |
| specification/context/api-propagators.md | Updates propagator distribution wording to use “OpenTelemetry Core packages” and aligns vendor-specific restrictions. |
| CHANGELOG.md | Notes the new “Core packages” term in the Common section. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
pellared
commented
Apr 24, 2026
pellared
marked this pull request as ready for review
April 24, 2026 15:00
reyang
reviewed
Apr 24, 2026
kamphaus
reviewed
Apr 24, 2026
reyang
enabled auto-merge
April 28, 2026 14:53
MrAlias
approved these changes
Apr 28, 2026
Merged
pull Bot
pushed a commit
to CodeWeaver13/opentelemetry-specification
that referenced
this pull request
May 20, 2026
### Metrics - Add in-development `Bind` API to synchronous instruments. ([open-telemetry#5050](open-telemetry#5050)) - Clarify that View-provided metric stream `name` is not subject to instrument name syntax validation. ([open-telemetry#5094](open-telemetry#5094)) ### Common - Define the Core packages term. ([open-telemetry#5046](open-telemetry#5046)) - Rework contributing guide to reflect current process. ([open-telemetry#5072](open-telemetry#5072)) ### Compatibility - Stabilize sections of Prometheus and OpenMetrics Compatibility. - Stabilize translation of labels prefixed with `otel_scope_` to OTLP Instrumentation Scope. ([open-telemetry#5004](open-telemetry#5004)) - Stabilize OpenTelemetry Gauge and Sum to Prometheus transformations. ([open-telemetry#5034](open-telemetry#5034)) - Stabilize OpenTelemetry Instrumentation Scope to Prometheus labels transformation. ([open-telemetry#5052](open-telemetry#5052)) - Stabilize sections of Prometheus Metrics Exporter. - Stabilize temporality. ([open-telemetry#5024](open-telemetry#5024)) - Stabilize version and format. ([open-telemetry#5083](open-telemetry#5083)) - Stabilize port configuration. ([open-telemetry#5026](open-telemetry#5026)) - Stabilize `scope_info_enabled` configuration. ([open-telemetry#5056](open-telemetry#5056)) - Change Prometheus Metric Exporter config property recommended names (`without_scope_info` -> `scope_info_enabled`, `without_target_info` -> `target_info_enabled`, `with_resource_constant_labels` -> `resource_constant_labels`) ([open-telemetry#5071](open-telemetry#5071)) - Clarify that OTel SDKs should not use unofficial Prometheus clients. ([open-telemetry#5082](open-telemetry#5082)) ### OTEPs - Add OTEP for Semantic Convention Schema v2 with support for multiple convention registries and resolved schema format ([open-telemetry#4815](open-telemetry#4815)) --------- Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
hilmarf
pushed a commit
to apeirora/opentelemetry-specification
that referenced
this pull request
Jun 1, 2026
### Metrics - Add in-development `Bind` API to synchronous instruments. ([open-telemetry#5050](open-telemetry#5050)) - Clarify that View-provided metric stream `name` is not subject to instrument name syntax validation. ([open-telemetry#5094](open-telemetry#5094)) ### Common - Define the Core packages term. ([open-telemetry#5046](open-telemetry#5046)) - Rework contributing guide to reflect current process. ([open-telemetry#5072](open-telemetry#5072)) ### Compatibility - Stabilize sections of Prometheus and OpenMetrics Compatibility. - Stabilize translation of labels prefixed with `otel_scope_` to OTLP Instrumentation Scope. ([open-telemetry#5004](open-telemetry#5004)) - Stabilize OpenTelemetry Gauge and Sum to Prometheus transformations. ([open-telemetry#5034](open-telemetry#5034)) - Stabilize OpenTelemetry Instrumentation Scope to Prometheus labels transformation. ([open-telemetry#5052](open-telemetry#5052)) - Stabilize sections of Prometheus Metrics Exporter. - Stabilize temporality. ([open-telemetry#5024](open-telemetry#5024)) - Stabilize version and format. ([open-telemetry#5083](open-telemetry#5083)) - Stabilize port configuration. ([open-telemetry#5026](open-telemetry#5026)) - Stabilize `scope_info_enabled` configuration. ([open-telemetry#5056](open-telemetry#5056)) - Change Prometheus Metric Exporter config property recommended names (`without_scope_info` -> `scope_info_enabled`, `without_target_info` -> `target_info_enabled`, `with_resource_constant_labels` -> `resource_constant_labels`) ([open-telemetry#5071](open-telemetry#5071)) - Clarify that OTel SDKs should not use unofficial Prometheus clients. ([open-telemetry#5082](open-telemetry#5082)) ### OTEPs - Add OTEP for Semantic Convention Schema v2 with support for multiple convention registries and resolved schema format ([open-telemetry#4815](open-telemetry#4815)) --------- Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per https://github.com/open-telemetry/opentelemetry-specification/pull/5042/files#r3125975557 and #5042 (comment)
Define the Core packages term.
Update occurrences of some existing wording where "Core packages" is a better fit.