chore!: Remove SEMANTIC_ATTRIBUTE_SENTRY_OP in favour of @sentry/conventions#22565
chore!: Remove SEMANTIC_ATTRIBUTE_SENTRY_OP in favour of @sentry/conventions#22565Lms24 wants to merge 1 commit into
SEMANTIC_ATTRIBUTE_SENTRY_OP in favour of @sentry/conventions#22565Conversation
SEMANTIC_ATTRIBUTE_SENTRY_OP in favour of @sentry/conventionsSEMANTIC_ATTRIBUTE_SENTRY_OP in favour of @sentry/conventions
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ef7ed2b. Configure here.
| import { waitForTransaction } from '@sentry-internal/test-utils'; | ||
| // Cannot use @sentry/angular here due to build stuff | ||
| import { SEMANTIC_ATTRIBUTE_SENTRY_OP, SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN } from '@sentry/core'; | ||
| import { SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN } from '@sentry/core'; |
There was a problem hiding this comment.
Public OP export removed without deprecation
High Severity
Flagged because it was mentioned in the PR review rules file: this removes the publicly exported SEMANTIC_ATTRIBUTE_SENTRY_OP from SDK entry points (@sentry/core and re-exports such as @sentry/nitro / @sentry/nuxt) without a deprecation notice. Sibling migrations kept deprecated aliases (for example SEMANTIC_ATTRIBUTE_SENTRY_SEGMENT_NAME), so external imports of SEMANTIC_ATTRIBUTE_SENTRY_OP will break at compile time.
Additional Locations (2)
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit ef7ed2b. Configure here.
No description provided.