Add http semantic conventions notice to changelog #6737
Conversation
|
We should wait for #6710 to be merged before merging this one. |
CHANGELOG.md
Outdated
| @@ -8,11 +8,24 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm | |||
|
|
|||
| ## [Unreleased] | |||
|
|
|||
| ### ⚠️ Notice ⚠️ | |||
There was a problem hiding this comment.
This shouldn't be it's own section.
What about alert syntax?
There was a problem hiding this comment.
I have moved it to the deprecated section with a warning.
dmathieu
force-pushed
the
semconv-notice
branch
from
c2c2cfa to
3bdad50
Compare
CHANGELOG.md
Outdated
| > [!WARNING] | ||
| > This is the last version to use Semantic Conventions v1.20.0 for HTTP libraries | ||
| by default. The next version (0.61.0) will default to v1.26.0, and the | ||
| following one (0.62.0) will drop support for Semantic Conventions v1.20.0 | ||
| > | ||
| > You can switch to the new Semantic Conventions right now by setting the | ||
| `OTEL_HTTP_CLIENT_COMPATIBILITY_MODE=http/dup` environment variable in your | ||
| application. | ||
| > | ||
| > See also the [HTTP semantic conventions stability | ||
| migration](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/non-normative/http-migration.md) |
There was a problem hiding this comment.
I suggest putting this in the beginning of the changelog for given version. I mean just before ### Added.
There was a problem hiding this comment.
That's what I did at first. But @MrAlias seems to want it into another section.
There was a problem hiding this comment.
@MrAlias said the opposite.
This shouldn't be it's own section.
There was a problem hiding this comment.
I'm not sure what @MrAlias intended, so I've moved it back to the top of the changelog.
Closes #6731