chore(deps): bump @sentry/integrations from 7.45.0 to 7.46.0

[dependabot]

Bumps @sentry/integrations from 7.45.0 to 7.46.0.

Release notes

Sourced from @​sentry/integrations's releases.

7.46.0

Important Changes

• feat(sveltekit): Add Performance Monitoring for SvelteKit
  • feat(sveltekit): Add meta tag for backend -> frontend (#7574)
  • fix(sveltekit): Explicitly export Node SDK exports (#7644)
  • fix(sveltekit): Handle nested server calls in sentryHandle (#7598)
  • ref(sveltekit): Split up universal and server load wrappers (#7652)

This release adds support for Performance Monitoring in our SvelteKit SDK for the client/server. We've also changed how you should initialize your SDK. Please read our updated SvelteKit README instructions for more details.

• feat(core): Add ignoreTransactions option (#7594)

You can now easily filter out certain transactions from being sent to Sentry based on their name.

Sentry.init({
  ignoreTransactions: ['/api/healthcheck', '/ping'],
})

• feat(node): Undici integration (#7582)
  • feat(nextjs): Add Undici integration automatically (#7648)
  • feat(sveltekit): Add Undici integration by default (#7650)

We've added an integration that automatically instruments Undici and Node server side fetch. This supports Undici v4.7.0 or higher and requires Node v16.7.0 or higher. After adding the integration outgoing requests made by Undici will have associated spans and breadcrumbs in Sentry.

Sentry.init({
  integrations: [new Sentry.Integrations.Undici()],
})

In our Next.js and SvelteKit SDKs, this integration is automatically added.

• feat(node): Add Sentry tRPC middleware (#7511)

We've added a new middleware for trpc that automatically adds TRPC information to Sentry transactions. This middleware is meant to be used in combination with a Sentry server integration (Next.js, Express, etc).

import { initTRPC } from '@trpc/server';
import * as Sentry from '@sentry/node';
const t = initTRPC.context().create();
const sentryMiddleware = t.middleware(
Sentry.Handlers.trpcMiddleware({
attachRpcInput: true,
}),
);
</tr></table>

... (truncated)

Changelog

Sourced from @​sentry/integrations's changelog.

7.46.0

Important Changes

• feat(sveltekit): Add Performance Monitoring for SvelteKit
  • feat(sveltekit): Add meta tag for backend -> frontend (#7574)
  • fix(sveltekit): Explicitly export Node SDK exports (#7644)
  • fix(sveltekit): Handle nested server calls in sentryHandle (#7598)
  • ref(sveltekit): Split up universal and server load wrappers (#7652)

This release adds support for Performance Monitoring in our SvelteKit SDK for the client/server. We've also changed how you should initialize your SDK. Please read our updated SvelteKit README instructions for more details.

• feat(core): Add ignoreTransactions option (#7594)

You can now easily filter out certain transactions from being sent to Sentry based on their name.

Sentry.init({
  ignoreTransactions: ['/api/healthcheck', '/ping'],
})

• feat(node): Undici integration (#7582)
  • feat(nextjs): Add Undici integration automatically (#7648)
  • feat(sveltekit): Add Undici integration by default (#7650)

We've added an integration that automatically instruments Undici and Node server side fetch. This supports Undici v4.7.0 or higher and requires Node v16.7.0 or higher. After adding the integration outgoing requests made by Undici will have associated spans and breadcrumbs in Sentry.

Sentry.init({
  integrations: [new Sentry.Integrations.Undici()],
})

In our Next.js and SvelteKit SDKs, this integration is automatically added.

• feat(node): Add Sentry tRPC middleware (#7511)

We've added a new middleware for trpc that automatically adds TRPC information to Sentry transactions. This middleware is meant to be used in combination with a Sentry server integration (Next.js, Express, etc).

import { initTRPC } from '@trpc/server';
import * as Sentry from '@sentry/node';
const t = initTRPC.context().create();
const sentryMiddleware = t.middleware(
Sentry.Handlers.trpcMiddleware({
attachRpcInput: true,
}),
);
</tr></table>

... (truncated)

Commits

• 993dc36 release: 7.46.0
• c622710 meta(changelog): Add @​sentry/tracing notes to 7.46.0 changelog (#7673)
• eb898f5 Merge pull request #7666 from getsentry/prepare-release/7.46.0
• 5e288f5 meta(changelog): Update changelog for 7.46.0
• d94a017 fix(docs): Remove references to @sentry/tracing from READMEs (#7600)
• 1403e77 test: Make E2E tests async & parallelizable (#7466)
• 9ecd152 feat(node): Sanitize URLs in Span descriptions and breadcrumbs (#7667)
• 65c44ec perf(build): Use @​rollup/plugin-typescript for es5 builds (#7665)
• 1eb271a doc(sveltekit): Move SDK initialization to hooks and restructure setup in REA...
• cefd523 ref(sveltekit): Inject init plugin only if sentry config files exist (#7663)
• 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 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 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)