Skip to content

Conversation

@dmathieu
Copy link
Member

@dmathieu dmathieu commented Nov 28, 2025

This is inspired by open-telemetry/opentelemetry-collector-contrib#44606

Mongo is the only package with an older semconv. See #8230 to move forward with the upgrade.

@dmathieu dmathieu added the Skip Changelog Allow PR to succeed without requiring an addition to the CHANGELOG label Nov 28, 2025
@dmathieu dmathieu marked this pull request as ready for review November 28, 2025 12:53
@dmathieu dmathieu requested a review from a team as a code owner November 28, 2025 12:53
list-mode: lax
deny:
- pkg: go.opentelemetry.io/otel/semconv
desc: Use go.opentelemetry.io/otel/semconv/v1.37.0 instead. If a newer semconv version has been released, update the depguard rule.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as I made on collector.

Suggested change
desc: Use go.opentelemetry.io/otel/semconv/v1.37.0 instead. If a newer semconv version has been released, update the depguard rule.
desc: Use go.opentelemetry.io/otel/semconv/v1.38.0 instead. When a newer semconv version is released, it must be added to the depguard rule.

Or

Suggested change
desc: Use go.opentelemetry.io/otel/semconv/v1.37.0 instead. If a newer semconv version has been released, update the depguard rule.
desc: Use go.opentelemetry.io/otel/semconv/v1.38.0 instead. If a newer semconv version has been released, update the depguard rule.

desc: Use go.opentelemetry.io/otel/semconv/v1.37.0 instead. If a newer semconv version has been released, update the depguard rule.
allow:
- go.opentelemetry.io/otel/semconv/v1.21.0 # still used by otelmongo
- go.opentelemetry.io/otel/semconv/v1.37.0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- go.opentelemetry.io/otel/semconv/v1.37.0
- go.opentelemetry.io/otel/semconv/v1.37.0
- go.opentelemetry.io/otel/semconv/v1.38.0

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upgrading to 1.38 makes sense. But it shouldn't be within this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Skip Changelog Allow PR to succeed without requiring an addition to the CHANGELOG

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants