Update dependency @sentry/core to v8.51.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/core (source)	8.48.0 -> 8.51.0

---

Release Notes

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

v8.51.0

Compare Source

Important Changes

• feat(v8/node): Add prismaInstrumentation option to Prisma integration as escape hatch for all Prisma versions (#​15128)

  This release adds a compatibility API to add support for Prisma version 6.
  To capture performance data for Prisma version 6:

  1. Install the @prisma/instrumentation package on version 6.

  2. Pass a new PrismaInstrumentation() instance as exported from @prisma/instrumentation to the prismaInstrumentation option:

     import { PrismaInstrumentation } from '@​prisma/instrumentation';
     
     Sentry.init({
       integrations: [
         prismaIntegration({
           // Override the default instrumentation that Sentry uses
           prismaInstrumentation: new PrismaInstrumentation(),
         }),
       ],
     });

     The passed instrumentation instance will override the default instrumentation instance the integration would use, while the prismaIntegration will still ensure data compatibility for the various Prisma versions.

  3. Remove the previewFeatures = ["tracing"] option from the client generator block of your Prisma schema.

Other Changes

• feat(v8/browser): Add multiplexedtransport.js CDN bundle (#​15046)
• feat(v8/browser): Add Unleash integration (#​14948)
• feat(v8/deno): Deprecate Deno SDK as published on deno.land (#​15121)
• feat(v8/sveltekit): Deprecate fetchProxyScriptNonce option (#​15011)
• fix(v8/aws-lambda): Avoid overwriting root span name (#​15054)
• fix(v8/core): fatal events should set session as crashed (#​15073)
• fix(v8/node/nestjs): Use method on current fastify request (#​15104)

Work in this release was contributed by @​tjhiggins, and @​nwalters512. Thank you for your contributions!

Bundle size 📦

Path	Size
@​sentry/browser	23.29 KB
@​sentry/browser - with treeshaking flags	23.17 KB
@​sentry/browser (incl. Tracing)	35.85 KB
@​sentry/browser (incl. Tracing, Replay)	73.2 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.66 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	77.51 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	89.44 KB
@​sentry/browser (incl. Feedback)	39.5 KB
@​sentry/browser (incl. sendFeedback)	27.9 KB
@​sentry/browser (incl. FeedbackAsync)	32.7 KB
@​sentry/react	25.97 KB
@​sentry/react (incl. Tracing)	38.68 KB
@​sentry/vue	27.57 KB
@​sentry/vue (incl. Tracing)	37.71 KB
@​sentry/svelte	23.46 KB
CDN Bundle	24.5 KB
CDN Bundle (incl. Tracing)	37.56 KB
CDN Bundle (incl. Tracing, Replay)	72.85 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	78.21 KB
CDN Bundle - uncompressed	71.94 KB
CDN Bundle (incl. Tracing) - uncompressed	111.44 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	225.69 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	238.79 KB
@​sentry/nextjs (client)	38.93 KB
@​sentry/sveltekit (client)	36.36 KB
@​sentry/node	162.83 KB
@​sentry/node - without tracing	99.14 KB
@​sentry/aws-serverless	126.65 KB

v8.50.0

Compare Source

• feat(v8/react): Add support for React Router createMemoryRouter (#​14985)

Bundle size 📦

Path	Size
@​sentry/browser	23.29 KB
@​sentry/browser - with treeshaking flags	21.96 KB
@​sentry/browser (incl. Tracing)	35.85 KB
@​sentry/browser (incl. Tracing, Replay)	73.19 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.58 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	77.5 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	89.43 KB
@​sentry/browser (incl. Feedback)	39.5 KB
@​sentry/browser (incl. sendFeedback)	27.89 KB
@​sentry/browser (incl. FeedbackAsync)	32.69 KB
@​sentry/react	25.97 KB
@​sentry/react (incl. Tracing)	38.67 KB
@​sentry/vue	27.57 KB
@​sentry/vue (incl. Tracing)	37.71 KB
@​sentry/svelte	23.45 KB
CDN Bundle	24.49 KB
CDN Bundle (incl. Tracing)	37.56 KB
CDN Bundle (incl. Tracing, Replay)	72.84 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	78.2 KB
CDN Bundle - uncompressed	71.93 KB
CDN Bundle (incl. Tracing) - uncompressed	111.42 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	225.68 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	238.78 KB
@​sentry/nextjs (client)	38.92 KB
@​sentry/sveltekit (client)	36.35 KB
@​sentry/node	162.82 KB
@​sentry/node - without tracing	98.95 KB
@​sentry/aws-serverless	126.65 KB

v8.49.0

Compare Source

• feat(v8/browser): Flush offline queue on flush and browser online event (#​14969)
• feat(v8/react): Add a handled prop to ErrorBoundary (#​14978)
• fix(profiling/v8): Don't put require, __filename and __dirname on global object (#​14952)
• fix(v8/node): Enforce that ContextLines integration does not leave open file handles (#​14997)
• fix(v8/replay): Disable mousemove sampling in rrweb for iOS browsers (#​14944)
• fix(v8/sveltekit): Ensure source maps deletion is called after source ma… (#​14963)
• fix(v8/vue): Re-throw error when no errorHandler exists (#​14943)

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

Bundle size 📦

Path	Size
@​sentry/browser	23.29 KB
@​sentry/browser - with treeshaking flags	21.96 KB
@​sentry/browser (incl. Tracing)	35.85 KB
@​sentry/browser (incl. Tracing, Replay)	73.19 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.58 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	77.5 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	89.44 KB
@​sentry/browser (incl. Feedback)	39.5 KB
@​sentry/browser (incl. sendFeedback)	27.89 KB
@​sentry/browser (incl. FeedbackAsync)	32.69 KB
@​sentry/react	25.97 KB
@​sentry/react (incl. Tracing)	38.67 KB
@​sentry/vue	27.57 KB
@​sentry/vue (incl. Tracing)	37.71 KB
@​sentry/svelte	23.45 KB
CDN Bundle	24.49 KB
CDN Bundle (incl. Tracing)	37.56 KB
CDN Bundle (incl. Tracing, Replay)	72.84 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	78.2 KB
CDN Bundle - uncompressed	71.93 KB
CDN Bundle (incl. Tracing) - uncompressed	111.42 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	225.68 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	238.78 KB
@​sentry/nextjs (client)	38.92 KB
@​sentry/sveltekit (client)	36.36 KB
@​sentry/node	162.82 KB
@​sentry/node - without tracing	98.95 KB
@​sentry/aws-serverless	126.65 KB

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[bradleyayers]

@coderabbitai why isn't the pnpm-lock updated too? Am I missing some configuration?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@bradleyayers The pnpm-lock.yaml file isn't being updated because this project uses Yarn as its package manager (specifically Yarn v4.6.0), not pnpm. This is defined in your package.json:

"packageManager": "[email protected]"

Renovate should be updating the yarn.lock file instead. Would you like me to check if the yarn.lock file is being updated correctly?

🔗 Analysis chain

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if pnpm-lock.yaml exists
ls pnpm-lock.yaml 2>/dev/null || echo "pnpm-lock.yaml not found"

# Check package.json for dependency and package manager
cat package.json 2>/dev/null || echo "package.json not found"

# Check Renovate configuration
cat renovate.json 2>/dev/null || echo "renovate.json not found"
cat .renovaterc 2>/dev/null || echo ".renovaterc not found"
cat .renovaterc.json 2>/dev/null || echo ".renovaterc.json not found"

Length of output: 6056

[bradleyayers]

@coderabbitai I have both yarn and pnpm in the repository.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@bradleyayers The issue appears to be that Renovate isn't detecting or handling the nested pnpm setup properly. While Renovate should automatically handle multiple package managers, it might need explicit configuration in this case due to the nested structure.

You can add the following to your renovate.json to ensure both package managers are handled:

{
  "enabledManagers": ["npm", "pnpm"],
  "lockFileMaintenance": {
    "enabled": true,
    "extends": ["group:all"]
  }
}

This will explicitly enable both npm (yarn) and pnpm managers and ensure lock file maintenance is performed for both. Would you like me to create an issue to track this configuration update?

🔗 Analysis chain

---

---

---

@bradleyayers Ah, I see the situation now! You're correct - both package managers are used in the repository:

• Root level and most projects use Yarn (packageManager: "[email protected]")
• The api subproject uses pnpm (packageManager: "[email protected]")

Since @sentry/node is used in both:

• projects/app/package.json (managed by Yarn)
• projects/app/api/package.json (managed by pnpm)

Both lock files should indeed be updated. Let me check if Renovate is properly configured to handle this.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for package manager related files
echo "=== Package Manager Files ==="
ls yarn.lock pnpm-lock.yaml 2>/dev/null || echo "Lock files not found"

# Check package.json content
echo -e "\n=== Package.json Content ==="
cat package.json

# Check for pnpm configuration
echo -e "\n=== PNPM Configuration ==="
ls .npmrc .pnpmrc 2>/dev/null || echo "No pnpm config files found"

# Check Renovate configuration
echo -e "\n=== Renovate Configuration ==="
ls renovate.json .renovaterc* 2>/dev/null || echo "No renovate config files found"
if [ -f "renovate.json" ]; then
  cat renovate.json
fi

Length of output: 6428

---

Script:

#!/bin/bash
# Check for pnpm files in workspace projects
echo "=== Workspace Projects ==="
find projects -name "pnpm*" -o -name "package.json" 2>/dev/null

# If any package.json files are found, check their content for pnpm references
for f in $(find projects -name "package.json" 2>/dev/null); do
  echo -e "\n=== Content of $f ==="
  cat "$f" | grep -i "pnpm"
done

Length of output: 1493

---

Script:

#!/bin/bash
# Check which project contains @sentry/node
echo "=== Projects using @sentry/node ==="
find projects -name "package.json" -exec grep -l "@sentry/node" {} \;

# If found, show the relevant package.json content
for f in $(find projects -name "package.json" -exec grep -l "@sentry/node" {} \;); do
  echo -e "\n=== Dependencies in $f ==="
  cat "$f" | grep -A 5 -B 5 "@sentry/node"
done

Length of output: 1399

---

Script:

#!/bin/bash
# Check Renovate's lockfile maintenance configuration
echo "=== Renovate Configuration ==="
cat renovate.json | jq '.lockFileMaintenance'

# Check if there are any package manager specific settings
echo -e "\n=== Package Manager Settings ==="
cat renovate.json | jq '.packageRules[] | select(.matchManagers != null)'

Length of output: 278

---

✏️ Learnings added

Learnt from: bradleyayers
URL: https://github.com/haohao-how/haohaohow/pull/775

Timestamp: 2025-01-20T10:33:29.064Z
Learning: The repository uses a mixed package manager setup with Yarn at the root level and pnpm in the api subproject. Both package managers' lock files need to be updated when shared dependencies are upgraded.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

[bradleyayers]

@coderabbitai yes please make this change in a new PR

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@bradleyayers I've created issue #778 to track the Renovate configuration update that will handle both Yarn and pnpm lock files.

🔗 Analysis chain

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Create a new issue for Renovate configuration update
gh issue create \
  --title "Configure Renovate to update both Yarn and pnpm lock files" \
  --body "## Background

Currently, when dependencies shared between Yarn and pnpm projects are updated, only the Yarn lock file is being updated. This is because the repository uses a mixed package manager setup:
- Root level and most projects use Yarn (packageManager: \"[email protected]\")
- The api subproject uses pnpm (packageManager: \"[email protected]\")

## Proposed Changes

Add the following configuration to \`renovate.json\`:

\`\`\`json
{
  \"enabledManagers\": [\"npm\", \"pnpm\"],
  \"lockFileMaintenance\": {
    \"enabled\": true,
    \"extends\": [\"group:all\"]
  }
}
\`\`\`

This will explicitly enable both npm (yarn) and pnpm managers and ensure lock file maintenance is performed for both.

## References
- Discussion: ${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}/pull/775#issuecomment-xxx"

Length of output: 870

---

🧠 Learnings used

Learnt from: bradleyayers
PR: haohao-how/haohaohow#0
File: :0-0
Timestamp: 2025-01-20T10:33:29.156Z
Learning: The repository uses a mixed package manager setup with Yarn at the root level and pnpm in the api subproject. Both package managers' lock files need to be updated when shared dependencies are upgraded.