Bump @sentry/node from 11.6.0 to 11.7.0

[dependabot]

Bumps @sentry/node from 11.6.0 to 11.7.0.

Release notes

Sourced from @​sentry/node's releases.

11.7.0

Important Changes

• feat(cloudflare): Add opt-in cron monitoring for Cron Triggers (#25014)

  The new cronTriggersIntegration sends check-ins for Cron Triggers. Each check-in includes the schedule from controller.cron, so Sentry creates the monitor on the first run. The integration is opt-in, because monitors are billed.

  Cron Triggers have no names, so map each cron expression of your wrangler config to a monitor slug. With the Sentry Cloudflare Vite plugin, add the integration to src/instrument.server.ts:

  // src/monitorSlugs.ts
  export const monitorSlugs: Record<string, string> = {
    '30 9 * * MON-FRI': 'daily-report',
  };
  // src/instrument.server.ts
  import * as Sentry from '@​sentry/cloudflare';
  import { monitorSlugs } from './monitorSlugs';
  export default Sentry.defineCloudflareOptions(env => ({
  dsn: env.SENTRY_DSN,
  integrations: [Sentry.cronTriggersIntegration({ monitorSlug: cron => monitorSlugs[cron] })],
  }));
  // src/index.ts
  import { monitorSlugs } from './monitorSlugs';
  export default {
  async scheduled(controller, env) {
  switch (monitorSlugs[controller.cron]) {
  case 'daily-report':
  // Your daily report job
  break;
  }
  },
  };

  The monitorSlug function can also return monitor settings, for example { monitorSlug: 'daily-report', maxRuntime: 30 }, or undefined to send no check-ins for a trigger. Without monitorSlug, the SDK derives the slug from the cron expression. If you deploy with wrangler directly, pass the same integration to Sentry.withSentry.

• feat(node): Add neonIntegration for @​neondatabase/serverless (#25164, #25176)

  The new neonIntegration creates db spans for queries of the @neondatabase/serverless driver: for the WebSocket Client and Pool, and for the HTTP neon() function. This includes the neon-http and neon-serverless adapters of Drizzle. The integration is on by default when tracing is enabled.

• feat(node): Stop sending the process session once request sessions are tracked (#24915)

  Node servers sent release health data two times: as request session aggregates, and as the process session of processSessionIntegration. An error in a request also marked the process session as errored, so the SDK counted the error two times. Now the SDK drops the process session when it tracks the first request session. Scripts, CLIs and workers that do not serve requests keep the process session, and so do servers with httpServerIntegration({ sessions: false }). This changes the release health numbers of Node servers, because they no longer send the errored or crashed update of the process session.

• feat(server-utils): Record decide calls as gen_ai.decide spans (#25270, #25272, #25274, #25281)

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

11.7.0

Important Changes

• feat(cloudflare): Add opt-in cron monitoring for Cron Triggers (#25014)

  The new cronTriggersIntegration sends check-ins for Cron Triggers. Each check-in includes the schedule from controller.cron, so Sentry creates the monitor on the first run. The integration is opt-in, because monitors are billed.

  Cron Triggers have no names, so map each cron expression of your wrangler config to a monitor slug. With the Sentry Cloudflare Vite plugin, add the integration to src/instrument.server.ts:

  // src/monitorSlugs.ts
  export const monitorSlugs: Record<string, string> = {
    '30 9 * * MON-FRI': 'daily-report',
  };
  // src/instrument.server.ts
  import * as Sentry from '@​sentry/cloudflare';
  import { monitorSlugs } from './monitorSlugs';
  export default Sentry.defineCloudflareOptions(env => ({
  dsn: env.SENTRY_DSN,
  integrations: [Sentry.cronTriggersIntegration({ monitorSlug: cron => monitorSlugs[cron] })],
  }));
  // src/index.ts
  import { monitorSlugs } from './monitorSlugs';
  export default {
  async scheduled(controller, env) {
  switch (monitorSlugs[controller.cron]) {
  case 'daily-report':
  // Your daily report job
  break;
  }
  },
  };

  The monitorSlug function can also return monitor settings, for example { monitorSlug: 'daily-report', maxRuntime: 30 }, or undefined to send no check-ins for a trigger. Without monitorSlug, the SDK derives the slug from the cron expression. If you deploy with wrangler directly, pass the same integration to Sentry.withSentry.

• feat(node): Add neonIntegration for @​neondatabase/serverless (#25164, #25176)

  The new neonIntegration creates db spans for queries of the @neondatabase/serverless driver: for the WebSocket Client and Pool, and for the HTTP neon() function. This includes the neon-http and neon-serverless adapters of Drizzle. The integration is on by default when tracing is enabled.

• feat(node): Stop sending the process session once request sessions are tracked (#24915)

  Node servers sent release health data two times: as request session aggregates, and as the process session of processSessionIntegration. An error in a request also marked the process session as errored, so the SDK counted the error two times. Now the SDK drops the process session when it tracks the first request session. Scripts, CLIs and workers that do not serve requests keep the process session, and so do servers with httpServerIntegration({ sessions: false }). This changes the release health numbers of Node servers, because they no longer send the errored or crashed update of the process session.

• feat(server-utils): Record decide calls as gen_ai.decide spans (#25270, #25272, #25274, #25281)

... (truncated)

Commits

• 47dff7d release: 11.7.0
• 72588e6 Merge pull request #25296 from getsentry/prepare-release/11.7.0
• 323307a meta(changelog): Update changelog for 11.7.0
• 87bdc84 fix(bundler-plugins): Escape JSON in generated injection code (#25265)
• b80300b fix(server-utils): Stop treating previous_response_id as the OpenAI conversat...
• 236c0ce fix(browser): Apply urlQueryParams to breadcrumb and element timing URLs (#...
• ee04661 fix(browser): Apply urlQueryParams to event URLs, static span names and LCP...
• 1e86178 fix(nuxt): Keep @sentry/server-runtime-injection external on Nitro v3 (#24901)
• 8a6b9ca test(node-integration): Stop exporting NODE_VERSION and RUNTIME from the ...
• 9f7cbad feat(server-utils): Map Mastra classifier evaluations to gen_ai.decide spans ...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)