Skip to content
This repository was archived by the owner on Jun 30, 2025. It is now read-only.

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 28, 2024

Bumps @sentry/node from 8.4.0 to 8.5.0.

Release notes

Sourced from @​sentry/node's releases.

8.5.0

Important Changes

  • feat(react): Add React 19 to peer deps (#12207)

This release adds support for React 19 in the @sentry/react SDK package.

  • feat(node): Add @sentry/node/preload hook (#12213)

This release adds a new way to initialize @sentry/node, which allows you to use the SDK with performance instrumentation even if you cannot call Sentry.init() at the very start of your app.

First, run the SDK like this:

node --require @sentry/node/preload ./app.js

Now, you can initialize and import the rest of the SDK later or asynchronously:

const express = require('express');
const Sentry = require('@sentry/node');
const dsn = await getSentryDsn();
Sentry.init({ dsn });

For more details, head over to the PR Description of the new feature. Our docs will be updated soon with a new guide.

Other Changes

  • feat(browser): Do not include metrics in base CDN bundle (#12230)
  • feat(core): Add startNewTrace API (#12138)
  • feat(core): Allow to pass custom scope to captureFeedback() (#12216)
  • feat(core): Only allow SerializedSession in session envelope items (#11979)
  • feat(nextjs): Use Vercel's waitUntil to defer freezing of Vercel Lambdas (#12133)
  • feat(node): Ensure manual OTEL setup works (#12214)
  • fix(aws-serverless): Avoid minifying Module._resolveFilename in Lambda layer bundle (#12232)
  • fix(aws-serverless): Ensure lambda layer uses default export from ImportInTheMiddle (#12233)
  • fix(browser): Improve browser extension error message check (#12146)
  • fix(browser): Remove optional chaining in INP code (#12196)
  • fix(nextjs): Don't report React postpone errors (#12194)
  • fix(nextjs): Use global scope for generic event filters (#12205)
  • fix(node): Add origin to redis span (#12201)
  • fix(node): Change import of @prisma/instrumentation to use default import (#12185)
  • fix(node): Only import inspector asynchronously (#12231)
  • fix(replay): Update matcher for hydration error detection to new React docs (#12209)

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

8.5.0

Important Changes

  • feat(react): Add React 19 to peer deps (#12207)

This release adds support for React 19 in the @sentry/react SDK package.

  • feat(node): Add @sentry/node/preload hook (#12213)

This release adds a new way to initialize @sentry/node, which allows you to use the SDK with performance instrumentation even if you cannot call Sentry.init() at the very start of your app.

First, run the SDK like this:

node --require @sentry/node/preload ./app.js

Now, you can initialize and import the rest of the SDK later or asynchronously:

const express = require('express');
const Sentry = require('@sentry/node');
const dsn = await getSentryDsn();
Sentry.init({ dsn });

For more details, head over to the PR Description of the new feature. Our docs will be updated soon with a new guide.

Other Changes

  • feat(browser): Do not include metrics in base CDN bundle (#12230)
  • feat(core): Add startNewTrace API (#12138)
  • feat(core): Allow to pass custom scope to captureFeedback() (#12216)
  • feat(core): Only allow SerializedSession in session envelope items (#11979)
  • feat(nextjs): Use Vercel's waitUntil to defer freezing of Vercel Lambdas (#12133)
  • feat(node): Ensure manual OTEL setup works (#12214)
  • fix(aws-serverless): Avoid minifying Module._resolveFilename in Lambda layer bundle (#12232)
  • fix(aws-serverless): Ensure lambda layer uses default export from ImportInTheMiddle (#12233)
  • fix(browser): Improve browser extension error message check (#12146)
  • fix(browser): Remove optional chaining in INP code (#12196)
  • fix(nextjs): Don't report React postpone errors (#12194)
  • fix(nextjs): Use global scope for generic event filters (#12205)
  • fix(node): Add origin to redis span (#12201)
  • fix(node): Change import of @prisma/instrumentation to use default import (#12185)
  • fix(node): Only import inspector asynchronously (#12231)

... (truncated)

Commits
  • 63d8ba4 release: 8.5.0
  • 27a47f2 Merge pull request #12236 from getsentry/prepare-release/8.5.0
  • f32f88d meta: Add CHANGELOG entry for 8.5.0
  • 0fbe39a feat(browser): Do not include metrics in base CDN bundle (#12230)
  • 8dca102 fix(browser): Improve browser extension error message check (#12146)
  • 83c255a fix(aws): Ensure lambda layer uses default export from ImportInTheMiddle (#...
  • 5282753 fix: Only import inspector asynchronously (#12231)
  • 1f8f1b8 ref(profiling-node): Add warning when using non-LTS node (#12211)
  • c2b9079 fix(aws-serverless): Avoid minifying Module._resolveFilename in Lambda laye...
  • 2043f2d feat(nextjs): Use Vercel's waitUntil to defer freezing of Vercel Lambdas (#...
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [@sentry/node](https://github.com/getsentry/sentry-javascript) from 8.4.0 to 8.5.0.
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@8.4.0...8.5.0)

---
updated-dependencies:
- dependency-name: "@sentry/node"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels May 28, 2024
@dependabot dependabot bot requested review from bajtos and juliangruber May 28, 2024 08:00
@github-actions github-actions bot enabled auto-merge (squash) May 28, 2024 08:00
@socket-security
Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@sentry/node@8.5.0 Transitive: environment, filesystem, network, shell, unsafe +83 14.9 MB

🚮 Removed packages: npm/@sentry/node@8.4.0

View full report↗︎

@github-actions github-actions bot merged commit 3d8c8a6 into main May 28, 2024
@github-actions github-actions bot deleted the dependabot/npm_and_yarn/sentry/node-8.5.0 branch May 28, 2024 08:03
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants