ref(server-utils): Rename vercelAiIntegration to vercelAIIntegration - #23360
Conversation
size-limit report 📦
|
b5e18f5 to
398735d
Compare
6279ff4 to
5139b31
Compare
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 5139b31. Configure here.
| * Auto-instrument the `ai` SDK's native telemetry tracing channel (ai >= 7). | ||
| */ | ||
| export const vercelAiIntegration = defineIntegration(_vercelAiIntegration); | ||
| export const vercelAIIntegration = defineIntegration(_vercelAIIntegration); |
There was a problem hiding this comment.
Rename lacks deprecated alias
Medium Severity
Flagged because it was mentioned in the review rules file (Breaking Changes): the public vercelAiIntegration export is removed/renamed to vercelAIIntegration in @sentry/server-utils and dropped from @sentry/deno without a deprecated alias. Recent Deno renames in this repo kept @deprecated forwards for back-compat; this mechanical rename does not.
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit 5139b31. Configure here.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
5139b31 to
6e6bfc4
Compare
…span processing (#23384) Removes the OpenTelemetry-span post-processing path for the Vercel AI SDK from `@sentry/server-utils` — `addVercelAiProcessors` and every helper reachable only through it (the `spanStart`/`processSpan`/event-processor pipeline, plus the now-orphaned `utils.ts`, `constants.ts`, `types.ts`, and the `AI_*` attribute constants). `getProviderMetadataAttributes` is kept, since the `ai` >= 7 tracing-channel subscriber still shares it. Per-runtime handling of the `vercelAIIntegration`: - **Vercel Edge**: removed entirely. It relied on the OTel span post-processor, which is no longer available, and Vercel AI is not supported on the Edge runtime going forward. This also removes it from the Edge runtime of `@sentry/nextjs`. - **Deno**: re-exports `vercelAIIntegration` from `@sentry/server-utils/orchestrion` — the same integration Node uses and the one Deno's default set already registered. - **Cloudflare**: re-exports `vercelAIIntegration` from `@sentry/server-utils` (its existing import source; Cloudflare has not yet moved to the orchestrion entry). It now uses the channel-based integration directly instead of wrapping it with the OTel processors. A migration note is added under the v11 "AI integrations" removed-APIs section, and `addVercelAiProcessors` is dropped from the "moved helpers" list there. Stacked on top of #23360 (the `vercelAiIntegration` → `vercelAIIntegration` rename). --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>


Renames the orchestrion channel-integration factory
vercelAiIntegrationtovercelAIIntegrationin@sentry/server-utils, and updates every consumer (@sentry/node,@sentry/deno,@sentry/cloudflare) accordingly.Reasoning:
vercelAIIntegrationis the public, OTel-parity casing that@sentry/nodealready exposed by aliasing the server-utils export (vercelAiIntegration as vercelAIIntegration). Making the canonical export match that casing lets node drop the alias and keeps the factory name consistent across SDKs.Notes on the edge SDKs:
@sentry/cloudflareand@sentry/denowrap the server-utils factory in their ownvercelAIIntegration, so they import it under a local alias (channelVercelAIIntegration/serverUtilsVercelAiIntegration) to avoid a name clash.@sentry/denoalready re-exports its ownvercelAIIntegrationfrom its Deno-specific integration, so the (now duplicate) server-utils re-export is dropped from its barrel. TheVercelAiOptionstype keeps its existing casing.Split out of a larger
@sentry/server-utilscleanup branch as an isolated, mechanical rename.