From 1bdc127469f33b76c51bb4e9d8803b73860310c4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Tue, 21 May 2024 17:53:06 +0200 Subject: [PATCH] Versioning and stability: Require SemVer (#4039) --- CHANGELOG.md | 3 +++ specification/versioning-and-stability.md | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 13e5b73e50b..2743be345ff 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -27,6 +27,9 @@ release. ### Common +- OpenTelemetry clients MUST follow SemVer 2.0.0. + ([#4039](https://github.com/open-telemetry/opentelemetry-specification/pull/4039)) + ### Supplementary Guidelines ## v1.33.0 (2024-05-09) diff --git a/specification/versioning-and-stability.md b/specification/versioning-and-stability.md index 07a545afb5c..fd5d8435ff7 100644 --- a/specification/versioning-and-stability.md +++ b/specification/versioning-and-stability.md @@ -310,7 +310,7 @@ We invented a new tracing API, but continue to support the old one. ## Version numbers -OpenTelemetry clients follow [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html), with the following clarifications. +OpenTelemetry clients MUST follow [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html), with the following clarifications. OpenTelemetry clients have four components: API, SDK, Semantic Conventions, and Contrib.