ref(opentelemetry): Remove wrapContextManager export#22586
Conversation
Instead, the context manager accepts the async local storage instance now, so we can also use this in vercel-edge. this will eventually go away/move to server-utils likely so we can revisit this in a follow up.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
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 3f7d8fa. Configure here.
|
|
||
| export { setupEventContextTrace } from './setupEventContextTrace'; | ||
|
|
||
| // eslint-disable-next-line typescript/no-deprecated |
There was a problem hiding this comment.
Public API removed without migration docs
Medium Severity
wrapContextManagerClass is removed from the public @sentry/opentelemetry surface. That is a breaking public API removal. It was marked deprecated, but MIGRATION.md does not list this removal under @sentry/opentelemetry, and the package README still tells users they can use wrapContextManagerClass for a custom base. Flagged because the PR review rules call out public API removals and breaking changes without proper notices.
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit 3f7d8fa. Configure here.
1 participant
Instead, the context manager accepts the async local storage instance now, so we can also use this in vercel-edge. this will eventually go away/move to server-utils likely so we can revisit this in a follow up.
This also changes the manager slightly to not check for event emitter instance, as this does not work in vercel-edge, but look at the shape instead.