fix(deps): update sentry-javascript monorepo to v8.17.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/browser (source)	8.13.0 -> 8.17.0
@sentry/node (source)	8.13.0 -> 8.17.0
@sentry/vue (source)	8.13.0 -> 8.17.0

---

Release Notes

getsentry/sentry-javascript (@​sentry/browser)

v8.17.0

Compare Source

• feat: Upgrade OTEL deps (#​12809)
• fix(nuxt): Add module to build:transpile script (#​12843)
• fix(browser): Allow SDK initialization in NW.js apps (#​12846)

v8.16.0

Compare Source

Important Changes

• feat(nextjs): Use spans generated by Next.js for App Router (#​12729)

Previously, the @sentry/nextjs SDK automatically recorded spans in the form of transactions for each of your top-level
server components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have
a root span, and more importantly, if you had data stream to the client, its duration was not captured because the
server component spans had finished before the data could finish streaming.

With this release, we will capture the duration of App Router requests in their entirety as a single transaction with
server component spans being descendants of that transaction. This means you will get more data that is also more
accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it
has before.

Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no
longer receive server component transactions like Page Server Component (/path/to/route) (unless using the Edge
runtime), and you will instead receive transactions for your App Router SSR requests that look like
GET /path/to/route.

If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.

• - feat(nestjs): Add nest cron monitoring support (#​12781)

The @sentry/nestjs SDK now includes a @SentryCron decorator that can be used to augment the native NestJS @Cron
decorator to send check-ins to Sentry before and after each cron job run:

import { Cron } from '@​nestjs/schedule';
import { SentryCron, MonitorConfig } from '@​sentry/nestjs';
import type { MonitorConfig } from '@​sentry/types';

const monitorConfig: MonitorConfig = {
  schedule: {
    type: 'crontab',
    value: '* * * * *',
  },
  checkinMargin: 2, // In minutes. Optional.
  maxRuntime: 10, // In minutes. Optional.
  timezone: 'America/Los_Angeles', // Optional.
};

export class MyCronService {
  @​Cron('* * * * *')
  @​SentryCron('my-monitor-slug', monitorConfig)
  handleCron() {
    // Your cron job logic here
  }
}

Other Changes

• feat(node): Allow to pass instrumentation config to httpIntegration (#​12761)
• feat(nuxt): Add server error hook (#​12796)
• feat(nuxt): Inject sentry config with Nuxt addPluginTemplate (#​12760)
• fix: Apply stack frame metadata before event processors (#​12799)
• fix(feedback): Add missing h import in ScreenshotEditor (#​12784)
• fix(node): Ensure autoSessionTracking is enabled by default (#​12790)
• ref(feedback): Let CropCorner inherit the existing h prop (#​12814)
• ref(otel): Ensure we never swallow args for ContextManager (#​12798)

v8.15.0

Compare Source

• feat(core): allow unregistering callback through on (#​11710)
• feat(nestjs): Add function-level span decorator to nestjs (#​12721)
• feat(otel): Export & use spanTimeInputToSeconds for otel span exporter (#​12699)
• fix(core): Pass origin as referrer for lazyLoadIntegration (#​12766)
• fix(deno): Publish from build directory (#​12773)
• fix(hapi): Specify error channel to filter boom errors (#​12725)
• fix(react): Revert back to jsxRuntime: 'classic' to prevent breaking react 17 (#​12775)
• fix(tracing): Report dropped spans for transactions (#​12751)
• ref(scope): Delete unused public getStack() (#​12737)

Work in this release was contributed by @​arturovt and @​jaulz. Thank you for your contributions!

v8.14.0

Compare Source

Important Changes

• feat(nestjs): Filter 4xx errors (#​12695)

The @sentry/nestjs SDK no longer captures 4xx errors automatically.

Other Changes

• chore(react): Remove private namespace JSX (#​12691)
• feat(deps): bump @​opentelemetry/propagator-aws-xray from 1.25.0 to 1.25.1 (#​12719)
• feat(deps): bump @​prisma/instrumentation from 5.16.0 to 5.16.1 (#​12718)
• feat(node): Add registerEsmLoaderHooks option (#​12684)
• feat(opentelemetry): Expose sampling helper (#​12674)
• fix(browser): Make sure measure spans have valid start timestamps (#​12648)
• fix(hapi): Widen type definitions (#​12710)
• fix(nextjs): Attempt to ignore critical dependency warnings (#​12694)
• fix(react): Fix React jsx runtime import for esm (#​12740)
• fix(replay): Start replay in afterAllSetup instead of next tick (#​12709)

Work in this release was contributed by @​quisido. Thank you for your contribution!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[coveralls]

coverage: 57.758%. remained the same
when pulling f9a71a7 on renovate/sentry-javascript-monorepo
into f6d0ef4 on devel.