Sourced from @​sentry/profiling-node's releases.

10.13.0

Important Changes

• feat(browser): Add option to explicitly end pageload span via reportPageLoaded() (#17697)

  With this release you can take manual control of ending the pageload span. Usually this span is ended automatically by the SDK, based on a period of inactivity after the initial page was loaded in the browser. If you want full control over the pageload duration, you can tell Sentry, when your page was fully loaded:

  Sentry.init({
    //...
    integrations: [
      // 1. Enable manual pageload reporting
      Sentry.browserTracingIntegration({ enableReportPageLoaded: true }),
    ],
  });
  // 2. Whenever you decide the page is loaded, call:
  
  Sentry.reportPageLoaded();
  
  

  Note that if Sentry.reportPageLoaded() is not called within 30 seconds of the initial pageload (or whatever value the finalTimeout option is set to), the pageload span will be ended automatically.

• feat(core,node): Add instrumentation for GoogleGenerativeAI (#17625)

  The SDK now automatically instruments the @google/generative-ai package to provide insights into your AI operations.

• feat(nextjs): Promote useRunAfterProductionCompileHook to non-experimental build option (#17721)

  The useRunAfterProductionCompileHook option is no longer experimental and is now a stable build option for Next.js projects.

• feat(nextjs): Use afterProductionCompile hook for webpack builds (#17655)

  Next.js projects using webpack can opt-in to use the useRunAfterProductionCompileHook hook for source map uploads.

• feat(nextjs): Flip default value for useRunAfterProductionCompileHook for Turbopack builds (#17722)

  The useRunAfterProductionCompileHook option is now enabled by default for Turbopack builds, enabling automated source map uploads.

• feat(node): Do not drop 300 and 304 status codes by default (#17686)

  HTTP transactions with 300 and 304 status codes are now captured by default, providing better visibility into redirect and caching behavior.

Other Changes

• feat(core): Add logger to core and allow scope to be passed log methods (#17698)
• feat(core): Allow to pass onSuccess to handleCallbackErrors (#17679)
• feat(core): Create template attributes in consoleLoggingIntegration (#17703)
• feat(deps): bump @​sentry/cli from 2.52.0 to 2.53.0 (#17652)
• feat(node): Add extra platforms to os context (#17720)
• fix(browser): Ensure idle span duration is adjusted when child spans are ignored (#17700)

... (truncated)

Sourced from @​sentry/profiling-node's changelog.

10.13.0

Important Changes

• feat(browser): Add option to explicitly end pageload span via reportPageLoaded() (#17697)

  With this release you can take manual control of ending the pageload span. Usually this span is ended automatically by the SDK, based on a period of inactivity after the initial page was loaded in the browser. If you want full control over the pageload duration, you can tell Sentry, when your page was fully loaded:

  Sentry.init({
    //...
    integrations: [
      // 1. Enable manual pageload reporting
      Sentry.browserTracingIntegration({ enableReportPageLoaded: true }),
    ],
  });
  // 2. Whenever you decide the page is loaded, call:
  
  Sentry.reportPageLoaded();
  
  

  Note that if Sentry.reportPageLoaded() is not called within 30 seconds of the initial pageload (or whatever value the finalTimeout option is set to), the pageload span will be ended automatically.

• feat(core,node): Add instrumentation for GoogleGenerativeAI (#17625)

  The SDK now automatically instruments the @google/generative-ai package to provide insights into your AI operations.

• feat(nextjs): Promote useRunAfterProductionCompileHook to non-experimental build option (#17721)

  The useRunAfterProductionCompileHook option is no longer experimental and is now a stable build option for Next.js projects.

• feat(nextjs): Use afterProductionCompile hook for webpack builds (#17655)

  Next.js projects using webpack can opt-in to use the useRunAfterProductionCompileHook hook for source map uploads.

• feat(nextjs): Flip default value for useRunAfterProductionCompileHook for Turbopack builds (#17722)

  The useRunAfterProductionCompileHook option is now enabled by default for Turbopack builds, enabling automated source map uploads.

• feat(node): Do not drop 300 and 304 status codes by default (#17686)

  HTTP transactions with 300 and 304 status codes are now captured by default, providing better visibility into redirect and caching behavior.

Other Changes

• feat(core): Add logger to core and allow scope to be passed log methods (#17698)
• feat(core): Allow to pass onSuccess to handleCallbackErrors (#17679)
• feat(core): Create template attributes in consoleLoggingIntegration (#17703)
• feat(deps): bump @​sentry/cli from 2.52.0 to 2.53.0 (#17652)
• feat(node): Add extra platforms to os context (#17720)

... (truncated)

• See full diff in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)