chore(deps): bump @sentry/node and @sentry/nextjs in /keep-ui

[dependabot]

Bumps @sentry/node to 8.52.0 and updates ancestor dependency @sentry/nextjs. These dependencies need to be updated together.

Updates @sentry/node from 8.38.0 to 8.52.0

Release notes

Sourced from @​sentry/node's releases.

8.52.0

Important Changes

• feat(solidstart): Add withSentry wrapper for SolidStart config (#15135)

To enable the SolidStart SDK, wrap your SolidStart Config with withSentry. The sentrySolidStartVite plugin is now automatically added by withSentry and you can pass the Sentry build-time options like this:

import { defineConfig } from '@solidjs/start/config';
import { withSentry } from '@sentry/solidstart';
export default defineConfig(
withSentry(
{
/* Your SolidStart config options... */
},
{
// Options for setting up source maps
org: process.env.SENTRY_ORG,
project: process.env.SENTRY_PROJECT,
authToken: process.env.SENTRY_AUTH_TOKEN,
},
),
);

With the withSentry wrapper, the Sentry server config should not be added to the public directory anymore. Add the Sentry server config in src/instrument.server.ts. Then, the server config will be placed inside the server build output as instrument.server.mjs.

Now, there are two options to set up the SDK:

1. (recommended) Provide an --import CLI flag to the start command like this (path depends on your server setup): node --import ./.output/server/instrument.server.mjs .output/server/index.mjs
2. Add autoInjectServerSentry: 'top-level-import' and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)

   withSentry(
     {
       /* Your SolidStart config options... */
     },
     {
       // Optional: Install Sentry with a top-level import
       autoInjectServerSentry: 'top-level-import',
     },
   );

Other Changes

• feat(v8/core): Add client outcomes for breadcrumbs buffer (#15149)

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

8.52.0

Important Changes

• feat(solidstart): Add withSentry wrapper for SolidStart config (#15135)

To enable the SolidStart SDK, wrap your SolidStart Config with withSentry. The sentrySolidStartVite plugin is now automatically added by withSentry and you can pass the Sentry build-time options like this:

import { defineConfig } from '@solidjs/start/config';
import { withSentry } from '@sentry/solidstart';
export default defineConfig(
withSentry(
{
/* Your SolidStart config options... */
},
{
// Options for setting up source maps
org: process.env.SENTRY_ORG,
project: process.env.SENTRY_PROJECT,
authToken: process.env.SENTRY_AUTH_TOKEN,
},
),
);

With the withSentry wrapper, the Sentry server config should not be added to the public directory anymore. Add the Sentry server config in src/instrument.server.ts. Then, the server config will be placed inside the server build output as instrument.server.mjs.

Now, there are two options to set up the SDK:

1. (recommended) Provide an --import CLI flag to the start command like this (path depends on your server setup): node --import ./.output/server/instrument.server.mjs .output/server/index.mjs
2. Add autoInjectServerSentry: 'top-level-import' and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)

   withSentry(
     {
       /* Your SolidStart config options... */
     },
     {
       // Optional: Install Sentry with a top-level import
       autoInjectServerSentry: 'top-level-import',
     },
   );

Other Changes

... (truncated)

Commits

• bbafacb release: 8.52.0
• a6f7300 meta(changelog): Update CHANGELOG for 8.52.0 (#15177)
• cb6aca7 fix(v8/core): Pass module into loadModule (#15139) (#15166)
• 4a83c9a test(v8/e2e): Avoid making request to example.com in nextjs e2e test (#15176)
• 3fa3510 test(v8/e2e): Unflake replay recording data optional e2e test (#15168) (#15172)
• fe0272a fix(v8/bun): Ensure instrumentation of Bun.serve survives a server reload (...
• a3ddff6 feat(v8/core): Improve error formatting in ZodErrors integration (#15155)
• b468ab0 feat(v8/core): Add client outcomes for breadcrumbs buffer (#15149)
• a76f243 feat(v8/solidstart): Add withSentry wrapper for SolidStart config (#15135)
• d5f80af Merge branch 'release/8.51.0' into v8
• Additional commits viewable in compare view

Updates @sentry/nextjs from 8.38.0 to 8.52.0

Release notes

Sourced from @​sentry/nextjs's releases.

8.52.0

Important Changes

• feat(solidstart): Add withSentry wrapper for SolidStart config (#15135)

To enable the SolidStart SDK, wrap your SolidStart Config with withSentry. The sentrySolidStartVite plugin is now automatically added by withSentry and you can pass the Sentry build-time options like this:

import { defineConfig } from '@solidjs/start/config';
import { withSentry } from '@sentry/solidstart';
export default defineConfig(
withSentry(
{
/* Your SolidStart config options... */
},
{
// Options for setting up source maps
org: process.env.SENTRY_ORG,
project: process.env.SENTRY_PROJECT,
authToken: process.env.SENTRY_AUTH_TOKEN,
},
),
);

With the withSentry wrapper, the Sentry server config should not be added to the public directory anymore. Add the Sentry server config in src/instrument.server.ts. Then, the server config will be placed inside the server build output as instrument.server.mjs.

Now, there are two options to set up the SDK:

1. (recommended) Provide an --import CLI flag to the start command like this (path depends on your server setup): node --import ./.output/server/instrument.server.mjs .output/server/index.mjs
2. Add autoInjectServerSentry: 'top-level-import' and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)

   withSentry(
     {
       /* Your SolidStart config options... */
     },
     {
       // Optional: Install Sentry with a top-level import
       autoInjectServerSentry: 'top-level-import',
     },
   );

Other Changes

• feat(v8/core): Add client outcomes for breadcrumbs buffer (#15149)

... (truncated)

Changelog

Sourced from @​sentry/nextjs's changelog.

8.52.0

Important Changes

• feat(solidstart): Add withSentry wrapper for SolidStart config (#15135)

To enable the SolidStart SDK, wrap your SolidStart Config with withSentry. The sentrySolidStartVite plugin is now automatically added by withSentry and you can pass the Sentry build-time options like this:

import { defineConfig } from '@solidjs/start/config';
import { withSentry } from '@sentry/solidstart';
export default defineConfig(
withSentry(
{
/* Your SolidStart config options... */
},
{
// Options for setting up source maps
org: process.env.SENTRY_ORG,
project: process.env.SENTRY_PROJECT,
authToken: process.env.SENTRY_AUTH_TOKEN,
},
),
);

With the withSentry wrapper, the Sentry server config should not be added to the public directory anymore. Add the Sentry server config in src/instrument.server.ts. Then, the server config will be placed inside the server build output as instrument.server.mjs.

Now, there are two options to set up the SDK:

1. (recommended) Provide an --import CLI flag to the start command like this (path depends on your server setup): node --import ./.output/server/instrument.server.mjs .output/server/index.mjs
2. Add autoInjectServerSentry: 'top-level-import' and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)

   withSentry(
     {
       /* Your SolidStart config options... */
     },
     {
       // Optional: Install Sentry with a top-level import
       autoInjectServerSentry: 'top-level-import',
     },
   );

Other Changes

... (truncated)

Commits

• bbafacb release: 8.52.0
• a6f7300 meta(changelog): Update CHANGELOG for 8.52.0 (#15177)
• cb6aca7 fix(v8/core): Pass module into loadModule (#15139) (#15166)
• 4a83c9a test(v8/e2e): Avoid making request to example.com in nextjs e2e test (#15176)
• 3fa3510 test(v8/e2e): Unflake replay recording data optional e2e test (#15168) (#15172)
• fe0272a fix(v8/bun): Ensure instrumentation of Bun.serve survives a server reload (...
• a3ddff6 feat(v8/core): Improve error formatting in ZodErrors integration (#15155)
• b468ab0 feat(v8/core): Add client outcomes for breadcrumbs buffer (#15149)
• a76f243 feat(v8/solidstart): Add withSentry wrapper for SolidStart config (#15135)
• d5f80af Merge branch 'release/8.51.0' into v8
• 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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
keep	⬜️ Ignored (Inspect)	Visit Preview		Jan 30, 2025 10:40am

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ talboren
✅ shahargl
❌ dependabot[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[shahargl]

@talboren any reason not to merge?

[talboren]

@talboren any reason not to merge?

Nope, merging