Update dependency @sentry/ember to v8 #8645
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.116.0->8.7.0Release Notes
getsentry/sentry-javascript (@sentry/ember)
v8.7.0Important Changes
feat(react): Add TanStack Router integration (#12095)
This release adds instrumentation for TanStack router with a new
tanstackRouterBrowserTracingIntegrationin the@sentry/reactSDK:Other Changes
sourceMappingURLcomment on client whennextConfig.productionBrowserSourceMaps: trueisset (#12278)
v8.6.0Important Changes
feat(metrics): Add
timingsmethod to metrics (#12226)This introduces a new method,
metrics.timing(), which can be used in two ways:secondas unit:create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:
feat(react): Add
Sentry.reactErrorHandler(#12147)This PR introduces
Sentry.reactErrorHandler, which you can use in React 19 as follows:For more details, take a look at the PR. Our
documentation will be updated soon!
Other Changes
v8.5.0Compare Source
Important Changes
This release adds support for React 19 in the
@sentry/reactSDK package.@sentry/node/preloadhook (#12213)This release adds a new way to initialize
@sentry/node, which allows you to use the SDK with performanceinstrumentation even if you cannot call
Sentry.init()at the very start of your app.First, run the SDK like this:
Now, you can initialize and import the rest of the SDK later or asynchronously:
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
startNewTraceAPI (#12138)captureFeedback()(#12216)SerializedSessionin session envelope items (#11979)waitUntilto defer freezing of Vercel Lambdas (#12133)Module._resolveFilenamein Lambda layer bundle (#12232)ImportInTheMiddle(#12233)@prisma/instrumentationto use default import (#12185)inspectorasynchronously (#12231)v8.4.0Compare Source
Important Changes
If you are using Next.js version
14.3.0-canary.64or above, the Sentry Next.js SDK will now trace clientside pageloadswith 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 howthat error was caused, can now be traced back to a specific error in a server component.
This release guarantees support for Angular 18 with
@sentry/angular.Other Changes
v8.3.0Compare Source
Important Changes
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:
When using CommonJS, you can do:
Other Changes
browserProfilingIntegrationis published to CDN (#12158)node:prefix for node built-ins (#11895)setTimeoutto avoid e.g. angular change detection (#11924)undefinedvalues in props (#12131)@prisma/instrumentationfrom 5.13.0 to 5.14.0 (#12081)Work in this release contributed by @pboling. Thank you for your contribution!
v8.2.1Compare Source
v8.2.0Compare Source
beforeSendSpanhook (#11886)Scope(#12067)hasTracingEnabled()if possible (#12066)v8.1.0Compare 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.
lastEventIdon isolation scope (#11951) (#12022)awslambda-autoparseSampleRateutility function (#12024)eventIdoptional and uselastEventIdin report dialog (#12029)v8.0.0Compare Source
Important Changes
The Bun SDK will now capture global unhandled errors.
Other Changes
http.clientspans if there is an active parent span (#11974)execArgvare not sent to worker threads (#11963)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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.