Repository navigation
Conversation
This was referenced Oct 7, 2026
This branch has not been deployed
This file contains hidden or 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
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.
Adopt sentry-conventions through
664f7b4(getsentry/sentry-conventions#671) so MCP implementation names and resource URI schemes remain separate from OpenTelemetry network attributes. Previouslymcp.transport=CustomHTTPTransportfabricatednetwork.transport=CustomHTTPTransport, and afileresource scheme could prevent a real HTTP protocol from being backfilled.Two regression tests exercise the real normalizer with and without network metadata. Both fail at the old conventions pin and pass after the update. The submodule upgrade also brings the intervening conventions changes documented in both changelogs.
Deploy before releasing SDK changes that emit implementation names without a known network transport, including getsentry/sentry-javascript#24506 and getsentry/sentry-python#7925.
AI-assisted change, reviewed and validated with the complete Rust workspace test/doc/format/clippy checks, Python library tests and Python lint/type checks. The full integration run has 989 passes, 59 skips and 12 upload failures caused by the local objectstore response missing
session; all 12 also fail on the unchanged base commit with the same objectstore error.