Update dependency @sentry/node to v8 #1640

balena-renovate · 2024-05-16T15:55:34Z

This PR contains the following updates:

Package	Type	Update	Change	Pending
@sentry/node (source)	dependencies	major	`^7.116.0` -> `^8.0.0`	`8.10.0`

Release Notes

getsentry/sentry-javascript (@sentry/node)

`v8.9.2`

Compare Source

fix(profiling): Update exports so types generate properly (#12469)

`v8.9.1`

Important changes

feat(solid): Add Solid SDK

This release adds a dedicated SDK for Solid JS in alpha state with instrumentation for
Solid Router and a custom ErrorBoundary. See the
package README for how to use
the SDK.

Other changes

feat(deps): bump @opentelemetry/instrumentation-express from 0.40.0 to 0.40.1 (#12438)
feat(deps): bump @opentelemetry/instrumentation-mongodb from 0.44.0 to 0.45.0 (#12439)
feat(deps): bump @opentelemetry/propagator-aws-xray from 1.24.1 to 1.25.0 (#12437)
feat(nextjs): Allow for suppressing warning about missing global error handler file (#12369)
feat(redis): Add cache logic for redis-4 (#12429)
feat(replay): Replay Web Vital Breadcrumbs (#12296)
fix: Fix types export order (#12404)
fix(astro): Ensure server-side exports work correctly (#12453)
fix(aws-serverless): Add op to Otel-generated lambda function root span (#12430)
fix(aws-serverless): Only auto-patch handler in CJS when loading awslambda-auto (#12392)
fix(aws-serverless): Only start root span in Sentry wrapper if Otel didn't wrap handler (#12407)
fix(browser): Fix INP span creation & transaction tagging (#12372)
fix(nextjs): correct types conditional export ordering (#12355)
fix(replay): Fix guard for exception event (#12441)
fix(vue): Handle span name assignment for nested routes in VueRouter (#12398)

Work in this release was contributed by @soch4n. Thank you for your contribution!

`v8.9.0`

This release failed to publish correctly, please use 8.9.1 instead.

`v8.8.0`

Compare Source

feat: Upgrade OTEL dependencies (#12388)

This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use import-in-the-middle v1.8.0.
This should fix numerous issues with using OTEL instrumentation with ESM.

High level issues fixed with OTEL + ESM:

incompatibilities with using multiple loaders, commonly encountered while using tsx or similar libraries.
incompatibilities with libraries that use duplicate namespace exports like date-fns.
incompatibilities with libraries that use self-referencing namespace imports like openai.
incompatibilities with dynamic export patterns like exports with function calls.
ENOENT: no such file or directory bugs that libraries like discord.js
surface.

If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.

deps: Bump Sentry bundler plugins to version 2.18.0 (#12381)
feat: Add thirdPartyErrorFilterIntegration (#12267)
feat(core): Filter out error events with exception values and no stacktraces, values, or types (#12387)
feat(core): Ignore additional common but inactionable errors (#12384)
feat(deps): Bump @opentelemetry/propagator-aws-xray from 1.3.1 to 1.24.1 (#12333)
feat(deps): Bump @sentry/cli from 2.31.2 to 2.32.1 (#12332)
feat(redis): Support mget command in caching functionality (#12380)
feat(vercel-edge): Export core integrations from Vercel edge SDK (#12308)
fix(browser): Fix idle span ending (#12306)
fix(browser): Fix parenthesis parsing logic for chromium (#12373)
fix(browser): Fix types export path for CJS (#12305)
fix(feedback): Override TriggerLabel Option (#12316)
fix(feedback): Wait for document to be ready before doing autoinject (#12294)
fix(nextjs): Fix memory leak (#12335)
fix(nextjs): Fix version detection and option insertion logic for clientTraceMetadata option (#12323)
fix(nextjs): Update argument name in log message about sentry property on Next.js config object (#12366)
fix(node): Do not manually finish / update root Hapi spans. (#12287)
fix(node): Fix virtual parent span ID handling & update create-next-app E2E test (#12368)
fix(node): Skip capturing Hapi Boom responses v8. (#12288)
fix(performance): Fix LCP not getting picked up on initial pageload transaction by setting reportAllChanges to true
(#12360)
fix(replay): Avoid infinite loop of logs (#12309)
fix(replay): Ignore old events when manually starting replay (#12349)
ref(browser): Ensure idle span ending is consistent (#12310)
ref(profiling): unref timer (#12340)

Work in this release contributed by @dohooo, @mohd-akram, and @ykzts. Thank you for your contributions!

`v8.7.0`

Important Changes

feat(react): Add TanStack Router integration (#12095)

This release adds instrumentation for TanStack router with a new tanstackRouterBrowserTracingIntegration in the
@sentry/react SDK:

import * as Sentry from '@&#8203;sentry/react';
import { createRouter } from '@&#8203;tanstack/react-router';

const router = createRouter({
  // Your router options...
});

Sentry.init({
  dsn: '___PUBLIC_DSN___',
  integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)],
  tracesSampleRate: 1.0,
});

Other Changes

fix(nextjs): Do not hide sourceMappingURL comment on client when nextConfig.productionBrowserSourceMaps: true is
set (#12278)

`v8.6.0`

Important Changes

feat(metrics): Add timings method to metrics (#12226)

This introduces a new method, metrics.timing(), which can be used in two ways:
1. With a numeric value, to simplify creating a distribution metric. This will default to second as unit:
```
Sentry.metrics.timing('myMetric', 100);
```
1. With a callback, which will wrap the duration of the callback. This can accept a sync or async callback. It will
  create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:
```
const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction);
```

feat(react): Add Sentry.reactErrorHandler (#12147)

This PR introduces Sentry.reactErrorHandler, which you can use in React 19 as follows:

import * as Sentry from '@&#8203;sentry/react';
import { hydrateRoot } from 'react-dom/client';

ReactDOM.hydrateRoot(
  document.getElementById('root'),
  <React.StrictMode>
    <App />
  </React.StrictMode>,
  {
    onUncaughtError: Sentry.reactErrorHandler(),
    onCaughtError: Sentry.reactErrorHandler((error, errorInfo) => {
      // optional callback if users want custom config.
    }),
  },
);

For more details, take a look at the PR. Our
documentation will be updated soon!

Other Changes

feat(sveltekit): Add request data to server-side events (#12254)
fix(core): Pass in cron monitor config correctly (#12248)
fix(nextjs): Don't capture suspense errors in server components (#12261)
fix(tracing): Ensure sent spans are limited to 1000 (#12252)
ref(core): Use versioned carrier on global object (#12206)

`v8.5.0`

Compare Source

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 @&#8203;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('@&#8203;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)
ref(profiling-node): Add warning when using non-LTS node (#12211)

`v8.4.0`

Compare Source

Important Changes

feat(nextjs): Trace pageloads in App Router (#12157)

If you are using Next.js version 14.3.0-canary.64 or above, the Sentry Next.js SDK will now trace clientside pageloads
with React Server Components. This means, that client-side errors like
Error: An error occurred in the Server Components render., which previously didn't give you much information on how
that error was caused, can now be traced back to a specific error in a server component.

feat(angular): Add Support for Angular 18 (#12183)

This release guarantees support for Angular 18 with @sentry/angular.

Other Changes

feat(deps): Bump @opentelemetry/instrumentation-aws-lambda from 0.41.0 to 0.41.1 (#12078)
fix(metrics): Ensure string values are interpreted for metrics (#12165)

`v8.3.0`

Compare Source

Important Changes

Better Node Framework Span Data

This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi.

feat(node): Ensure connect spans have better data (#12130)
feat(node): Ensure express spans have better data (#12107)
feat(node): Ensure fastify spans have better data (#12106)
feat(node): Ensure hapi spans have better data (#12140)
feat(node): Ensure koa spans have better data (#12108)
feat(node): Ensure Nest.js spans have better data (#12139)
feat(deps): Bump @opentelemetry/instrumentation-express from 0.38.0 to 0.39.0 (#12079)
feat(node): No-code init via --import=@sentry/node/init (#11999)

When using Sentry in ESM mode, you can now use Sentry without manually calling init like this:

 SENTRY_DSN=https://[email protected]/0 node --import=@&#8203;sentry/node/init app.mjs

When using CommonJS, you can do:

 SENTRY_DSN=https://[email protected]/0 node --require=@&#8203;sentry/node/init app.js

Other Changes

chore: Align and update MIT license dates (#12143)
chore: Resolve or postpone a random assortment of TODOs (#11977)
doc(migration): Add entry for runWithAsyncContext (#12153)
docs: Add migration docs to point out that default import does not work (#12100)
docs(sveltekit): process.env.SENTRY_AUTH_TOKEN (#12118)
feat(browser): Ensure browserProfilingIntegration is published to CDN (#12158)
feat(google-cloud): Expose ESM build (#12149)
feat(nextjs): Ignore Prisma critical dependency warnings (#12144)
feat(node): Add app.free_memory info to events (#12150)
feat(node): Do not create GraphQL resolver spans by default (#12097)
feat(node): Use node: prefix for node built-ins (#11895)
feat(replay): Use unwrapped setTimeout to avoid e.g. angular change detection (#11924)
fix(core): Add dsn to span envelope header (#12096)
fix(feedback): Improve feedback border color in dark-mode, and prevent auto-dark mode when a theme is picked (#12126)
fix(feedback): Set optionOverrides to be optional in TS definition (#12125)
fix(nextjs): Don't put undefined values in props (#12131)
fix(nextjs): Fix legacy configuration method detection for emitting warning (#12136)
fix(node): Ensure fetch/http breadcrumbs are created correctly (#12137)
fix(node): Update @prisma/instrumentation from 5.13.0 to 5.14.0 (#12081)
ref(node): Add log for running in ESM/CommonJS mode (#12134)
ref(node): Handle failing hook registration gracefully (#12135)
ref(node): Only show instrumentation warning when tracing is enabled (#12141)

Work in this release contributed by @pboling. Thank you for your contribution!

`v8.2.1`

Compare Source

fix(aws-serverless): Fix build of lambda layer (#12083)
fix(nestjs): Broaden nest.js type (#12076)

`v8.2.0`

Compare Source

feat(redis-cache): Create cache-span with prefixed keys (get/set commands) (#12070)
feat(core): Add beforeSendSpan hook (#11886)
feat(browser): Improve idle span handling (#12065)
fix(node): Set transactionName for unsampled spans in httpIntegration (#12071)
fix(core): Export Scope interface as Scope (#12067)
fix(core): Avoid looking up client for hasTracingEnabled() if possible (#12066)
fix(browser): Use consistent timestamps (#12063)
fix(node): Fix check for performance integrations (#12043)
ref(sveltekit): Warn to delete source maps if Sentry plugin enabled source maps generation (#12072)

`v8.1.0`

Compare Source

This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we
updated some initially missed points in our migration guides and documentation.

feat(aws-serverless): Fix tree-shaking for aws-serverless package (#12017)
feat(node): Bump opentelemetry instrumentation to latest version (#12028)
feat(scope): Bring back lastEventId on isolation scope (#11951) (#12022)
fix(aws-serverless): Export awslambda-auto
fix(node): Do not warn for missing instrumentation if SDK is disabled (#12041)
fix(react): Set dependency-injected functions as early as possible (#12019)
fix(react): Warn and fall back gracefully if dependency injected functions are not available (#12026)
ref(core): Streamline parseSampleRate utility function (#12024)
ref(feedback): Make eventId optional and use lastEventId in report dialog (#12029)

`v8.0.0`

Compare Source

The Sentry JS SDK team is proud to announce the release of version 8.0.0 of Sentry's JavaScript SDKs - it's been a
long time coming! Thanks to everyone for your patience and a special shout out to the brave souls testing preview builds
and reporting issues - we appreciate your support!

How to Upgrade to Version 8:

We recommend reading the
migration guide docs to find out
how to address any breaking changes in your code for your specific platform or framework.

To automate upgrading to v8 as much as possible, use our migration codemod @sentry/migr8:

npx @&#8203;sentry/migr8@&#8203;latest

All deprecations from the v7 cycle, with the exception of getCurrentHub(), have been removed and can no longer be used
in v8. If you have an advanced Sentry SDK setup, we additionally recommend reading the
in-depth migration guide in our repo which highlights all changes with additional details and
information.

The rest of this changelog highlights the most important (breaking) changes and links to more detailed information.

Version Support

With v8, we dropped support for several old runtimes and browsers

Node SDKs: The Sentry JavaScript SDK v8 now supports Node.js 14.8.0 or higher. This applies to @sentry/node
and all of our node-based server-side sdks (@sentry/nextjs, @sentry/remix, etc.). Furthermore, version 8 now ships
with full support for ESM-based node apps using Node.js 18.19.0 or higher.

Browser SDKs: The browser SDKs now require
ES2018+
compatible browsers. New minimum browser versions:

Chrome 63
Edge 79
Safari/iOS Safari 12
Firefox 58
Opera 50
Samsung Internet 8.2

For more details, please see the
version support section in our migration guide.

Initializing Server-side SDKs (Node, Bun, Deno, Serverless):

In v8, we support a lot more node-based packages than before. In order to ensure auto-instrumentation works, the SDK now
needs to be imported and initialized before any other import in your code.

We recommend creating a new file (e.g. instrumentation.js) to import and initialize the SDK. Then, import the file on
top of your entry file or detailed instructions, check our updated SDK setup docs
initializing the SDK in v8.

Performance Monitoring Changes

The API around performance monitoring and tracing has been streamlined, and we've added support for more integrations
out of the box.

Functional Integrations

Integrations are now simple functions instead of classes. Class-based integrations
have been removed:

// old (v7)
Sentry.init({
  integrations: [new Sentry.BrowserTracing()],
});

// new (v8)
Sentry.init({
  integrations: [Sentry.browserTracingIntegration()],
});

Package removal

The following packages have been removed or replaced and will no longer be published:

Changes since `8.0.0-rc.3`

feat(nextjs): Remove transpileClientSDK (#11978)

As we are dropping support for Internet Explorer 11 and other other older browser versions wih version 8.0.0, we are
also removing the transpileClientSDK option from the Next.js SDK. If you need to support these browser versions,
please configure Webpack and Next.js to down-compile the SDK.
feat(serverless): Do not include performance integrations by default (#11998)

To keep Lambda bundle size reasonable, the SDK no longer ships with all performance (database) integrations by
default. Add the Sentry integrations of the databases and other tools you're using manually to your Sentry.init call
by following
this guide.
Note that this change does not apply if you use the SDK with the Sentry AWS Lambda layer.
feat(feedback): Simplify public css configuration for feedback (#11985)
fix(feedback): Check for empty user (#11993)
fix(replay): Fix type for replayCanvasIntegration (#11995)
fix(replay): Fix user activity not being updated in start() (#12001)

`v7.117.0`

Compare Source

feat(browser/v7): Publish browserprofling CDN bundle (#12224)
fix(v7/publish): Add v7 tag to @sentry/replay (#12304)

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 has been generated by Renovate Bot.

Update @sentry/node from 7.116.0 to 8.9.2 Change-type: patch

Page- · 2024-06-19T13:28:09Z

Handled by #1675

balena-renovate · 2024-06-19T13:51:19Z

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 8.x releases. But if you manually upgrade to 8.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

balena-renovate bot added the renovate label May 16, 2024

balena-renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch 5 times, most recently from 40e4e55 to 2f890f1 Compare May 27, 2024 02:11

balena-renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch 4 times, most recently from 5177047 to 5140689 Compare June 4, 2024 14:54

balena-renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch 12 times, most recently from ea784e4 to fe31f7f Compare June 11, 2024 15:51

balena-renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch 5 times, most recently from f2a2c30 to d5cf426 Compare June 17, 2024 16:54

Update dependency @sentry/node to v8

01b0637

Update @sentry/node from 7.116.0 to 8.9.2 Change-type: patch

balena-renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from d5cf426 to 01b0637 Compare June 18, 2024 08:52

Page- closed this Jun 19, 2024

balena-renovate bot deleted the renovate/major-sentry-javascript-monorepo branch June 19, 2024 13:51

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency @sentry/node to v8 #1640

Update dependency @sentry/node to v8 #1640

balena-renovate bot commented May 16, 2024 •

edited

Loading

Page- commented Jun 19, 2024

balena-renovate bot commented Jun 19, 2024

Update dependency @sentry/node to v8 #1640

Update dependency @sentry/node to v8 #1640

Conversation

balena-renovate bot commented May 16, 2024 • edited Loading

Release Notes

Important changes

Other changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

How to Upgrade to Version 8:

Version Support

Initializing Server-side SDKs (Node, Bun, Deno, Serverless):

Performance Monitoring Changes

Functional Integrations

Package removal

Changes since 8.0.0-rc.3

Configuration

Page- commented Jun 19, 2024

balena-renovate bot commented Jun 19, 2024

Renovate Ignore Notification

balena-renovate bot commented May 16, 2024 •

edited

Loading

Changes since `8.0.0-rc.3`