fix(deps): update sentry-javascript monorepo to v8 (major) #150
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.38.0->^8.0.0^7.38.0->^8.0.0Release Notes
getsentry/sentry-javascript (@sentry/node)
v8.19.0Compare Source
node --import=@sentry/node/import app.js
v8.18.0Compare Source
Important Changes
enableTracing(12897)The
enableTracingoption has been deprecated and will be removed in the next major version. We recommend removing itin favor of the
tracesSampleRateandtracesSampleroptions. If you want to enable performance monitoring, please setthe
tracesSampleRateto a sample rate of your choice, or provide a sampling function astracesSampleroptioninstead. If you want to disable performance monitoring, remove the
tracesSamplerandtracesSampleRateoptions.Other Changes
excludeandincludeoptions for ESM loader (#12910)experimental_captureRequestErrorforonRequestErrorhook (#12885)rrwebto 2.25.0 (#12478)ErrorEventcheck in ErrorHandler to avoid throwing in Node environments (#12892)ignoreIncomingRequestscallback (#12929)otel.kind: INTERNALattribute (#12841)nullasparentSpaninstartSpan*(#12928)Work in this release was contributed by @GitSquared and @mcous. Thank you for your contributions!
Bundle size 📦
v8.17.0Compare Source
v8.16.0Compare Source
Important Changes
Previously, the
@sentry/nextjsSDK automatically recorded spans in the form of transactions for each of your top-levelserver components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have
a root span, and more importantly, if you had data stream to the client, its duration was not captured because the
server component spans had finished before the data could finish streaming.
With this release, we will capture the duration of App Router requests in their entirety as a single transaction with
server component spans being descendants of that transaction. This means you will get more data that is also more
accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it
has before.
Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no
longer receive server component transactions like
Page Server Component (/path/to/route)(unless using the Edgeruntime), and you will instead receive transactions for your App Router SSR requests that look like
GET /path/to/route.If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.
The
@sentry/nestjsSDK now includes a@SentryCrondecorator that can be used to augment the native NestJS@Crondecorator to send check-ins to Sentry before and after each cron job run:
Other Changes
httpIntegration(#12761)addPluginTemplate(#12760)himport inScreenshotEditor(#12784)autoSessionTrackingis enabled by default (#12790)v8.15.0Compare Source
on(#11710)spanTimeInputToSecondsfor otel span exporter (#12699)lazyLoadIntegration(#12766)jsxRuntime: 'classic'to prevent breaking react 17 (#12775)getStack()(#12737)Work in this release was contributed by @arturovt and @jaulz. Thank you for your contributions!
v8.14.0Compare Source
Important Changes
The
@sentry/nestjsSDK no longer captures 4xx errors automatically.Other Changes
JSX(#12691)registerEsmLoaderHooksoption (#12684)afterAllSetupinstead of next tick (#12709)Work in this release was contributed by @quisido. Thank you for your contribution!
v8.13.0Compare Source
Important Changes
@sentry/nestjs)in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (
@sentry/node) supporting the same set offeatures. See the docs for how to use the SDK.
Other Changes
2.20.1(#12641)v8.12.0Compare Source
Important Changes
This release introduces breaking changes to the
@sentry/solidpackage (which is currently out in alpha).We've made it easier to get started with the solid router integration by removing the need to pass use* hooks
explicitly to
solidRouterBrowserTracingIntegration. ImportsolidRouterBrowserTracingIntegrationfrom@sentry/solid/solidrouterand add it toSentry.initSentry.init()now returns a client directly, so you don't need to explicitly callgetClient()anymore:deleteSourcemapsAfterUploadoption (#12457)This adds an easy way to delete sourcemaps immediately after uploading them:
maxSpanWaitDuration(#12610)Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before
discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is
necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However,
if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early.
In this case, you can increase this duration to a value that fits your expected data.
Other Changes
window.Sentry(#12580)isRemixV2as optional in exposed types. (#12614)Work in this release was contributed by @n4bb12. Thank you for your contribution!
v8.11.0Compare Source
Important Changes
parentSpanoption tostartSpan*APIs (#12567)We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to
explicitly manage the parent-child relationship of your spans better.
Other Changes
@sentry/nodeexports from framework SDKs. (#12589)Bundle size 📦
v8.10.0Compare Source
Important Changes
opentelemetry-instrumentation-remix. (#12110)You can now simplify your remix instrumentation by opting-in like this:
With this setup, you do not need to add e.g.
wrapExpressCreateRequestHandleranymore. Additionally, the quality of thecaptured data improves. The old way to use
@sentry/remixcontinues to work, but it is encouraged to use the new setup.Other Changes
thirdPartyErrorFilterIntegrationfrom@sentry/browser(#12512)tagsfield to any feedback config param (#12197)getDynamicSamplingContextFromSpan(#12522)captureRemixServerExceptionfrom client SDK (#12497)Work in this release was contributed by @AndreyKovanov and @kiliman. Thank you for your contributions!
v8.9.2Compare Source
v8.9.1Important 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 thepackage README for how to use
the SDK.
Other changes
opto Otel-generated lambda function root span (#12430)awslambda-auto(#12392)Work in this release was contributed by @soch4n. Thank you for your contribution!
v8.9.0This release failed to publish correctly, please use
8.9.1instead.v8.8.0Compare Source
This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use
import-in-the-middlev1.8.0.This should fix numerous issues with using OTEL instrumentation with ESM.
High level issues fixed with OTEL + ESM:
tsxor similar libraries.date-fns.openai.ENOENT: no such file or directorybugs that libraries likediscord.jssurface.
If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.
2.18.0(#12381)thirdPartyErrorFilterIntegration(#12267)mgetcommand in caching functionality (#12380)clientTraceMetadataoption (#12323)sentryproperty on Next.js config object (#12366)(#12360)
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)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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.