[BUGFIX]: conflicting Schema URL: https://opentelemetry.io/schemas/1.25.0 and https://opentelemetry.io/schemas/1.12.0" #218
Conversation
This file contains 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
…25.0 and https://opentelemetry.io/schemas/1.12.0" Signed-off-by: Celian GARCIA <celian.garcia@amadeus.com>
This pull request was closed.
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.
I propose to remove the schema from the merge to mitigate the following issue
The nightmare of it is explained in the following issue
open-telemetry/opentelemetry-go#2341
old wording for same error. Now at least they provide the two conflicting schema.
We could also keep schema and make a test of start on each PR, guaranteeing that the version of semconv align with default but in my opinion, as long as we merge with default containing the default schema that's fine.