chore(deps): bump @sentry/node from 8.15.0 to 8.17.0 in the sentry group

[dependabot]

Bumps the sentry group with 1 update: @sentry/node.

Updates @sentry/node from 8.15.0 to 8.17.0

Release notes

Sourced from @​sentry/node's releases.

8.17.0

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

Bundle size 📦

Path	Size
@​sentry/browser	22.31 KB
@​sentry/browser (incl. Tracing)	33.45 KB
@​sentry/browser (incl. Tracing, Replay)	69.2 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	62.53 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	73.27 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	85.9 KB
@​sentry/browser (incl. Tracing, Replay, Feedback, metrics)	87.76 KB
@​sentry/browser (incl. metrics)	26.59 KB
@​sentry/browser (incl. Feedback)	38.98 KB
@​sentry/browser (incl. sendFeedback)	26.92 KB
@​sentry/browser (incl. FeedbackAsync)	31.54 KB
@​sentry/react	25.05 KB
@​sentry/react (incl. Tracing)	36.49 KB
@​sentry/vue	26.41 KB
@​sentry/vue (incl. Tracing)	35.31 KB
@​sentry/svelte	22.44 KB
CDN Bundle	23.52 KB
CDN Bundle (incl. Tracing)	35.21 KB
CDN Bundle (incl. Tracing, Replay)	69.31 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	74.51 KB
CDN Bundle - uncompressed	69.02 KB
CDN Bundle (incl. Tracing) - uncompressed	104.04 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	214.43 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	227.15 KB
@​sentry/nextjs (client)	36.37 KB
@​sentry/sveltekit (client)	34.1 KB
@​sentry/node	130.79 KB
@​sentry/node - without tracing	91.88 KB
@​sentry/aws-serverless	117.05 KB

8.16.0

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

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

8.17.0

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

8.16.0

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 {
</tr></table>

... (truncated)

Commits

• a03e28c release: 8.17.0
• 2ff5b7b Merge pull request #12845 from getsentry/prepare-release/8.17.0
• 27626ad meta(changelog): Update changelog for 8.17.0
• afef63e fix(browser): Allow SDK initialization in NW.js apps (#12846)
• a79c566 fix(nuxt): Add module to build:transpile script (#12843)
• ed3d12f test(e2e): Add e2e test for AWS lambda in ESM mode (#12833)
• 339f25e ci: Shut up truffle hog (#12767)
• c69440a feat: Upgrade OTEL deps (#12809)
• ffef97f Merge pull request #12835 from getsentry/master
• 0f36aa5 Merge branch 'release/8.16.0'
• 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 will merge this PR once CI passes on it, as requested by @mdn-bot.

---

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 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[mdn-bot]

@dependabot squash and merge