You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ensure backwards compatibility by adding a compile-time check that the
Resource remains comparable.
Document the shortcomings of direct comparison of a Resource.
---------
Co-authored-by: Robert Pająk <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,8 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
25
25
- The `go.opentelemetry.io/otel/semconv/v1.30.0` package.
26
26
The package contains semantic conventions from the `v1.30.0` version of the OpenTelemetry Semantic Conventions.
27
27
See the [migration documentation](./semconv/v1.30.0/MIGRATION.md) for information on how to upgrade from `go.opentelemetry.io/otel/semconv/v1.28.0`(#6240)
28
+
- Document the pitfalls of using `Resource` as a comparable type.
29
+
`Resource.Equal` and `Resource.Equivalent` should be used instead. (#6272)
0 commit comments