chore(deps): update dependency @sentry/nextjs to v8.52.0 #1525
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:
8.37.1->8.52.0Release Notes
getsentry/sentry-javascript (@sentry/nextjs)
v8.52.0Compare Source
Important Changes
withSentrywrapper for SolidStart config (#15135)To enable the SolidStart SDK, wrap your SolidStart Config with
withSentry. ThesentrySolidStartViteplugin is now automaticallyadded by
withSentryand you can pass the Sentry build-time options like this:With the
withSentrywrapper, the Sentry server config should not be added to thepublicdirectory anymore.Add the Sentry server config in
src/instrument.server.ts. Then, the server config will be placed inside the server build output asinstrument.server.mjs.Now, there are two options to set up the SDK:
--importCLI flag to the start command like this (path depends on your server setup):node --import ./.output/server/instrument.server.mjs .output/server/index.mjsautoInjectServerSentry: 'top-level-import'and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)Other Changes
Bun.servesurvives a server reload (#15157)moduleintoloadModule(#15139) (#15166)Work in this release was contributed by @jahands, @jrandolf, and @nathankleyn. Thank you for your contributions!
Bundle size 📦
v8.51.0Compare Source
Important Changes
feat(v8/node): Add
prismaInstrumentationoption 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:
Install the
@prisma/instrumentationpackage on version 6.Pass a
new PrismaInstrumentation()instance as exported from@prisma/instrumentationto theprismaInstrumentationoption:The passed instrumentation instance will override the default instrumentation instance the integration would use, while the
prismaIntegrationwill still ensure data compatibility for the various Prisma versions.Remove the
previewFeatures = ["tracing"]option from the client generator block of your Prisma schema.Other Changes
multiplexedtransport.jsCDN bundle (#15046)fetchProxyScriptNonceoption (#15011)fatalevents should set session as crashed (#15073)Work in this release was contributed by @tjhiggins, and @nwalters512. Thank you for your contributions!
Bundle size 📦
v8.50.0Compare Source
createMemoryRouter(#14985)Bundle size 📦
v8.49.0Compare Source
handledprop to ErrorBoundary (#14978)require,__filenameand__dirnameon global object (#14952)Work in this release was contributed by @HHK1 and @mstrokin. Thank you for your contribution!
Bundle size 📦
v8.48.0Compare Source
Deprecations
feat(v8/core): Deprecate
getDomElementmethod (#14799)Deprecates
getDomElement. There is no replacement.Other changes
continueTraceimplementation in core (#14819)NODE_OPTIONSis not passed to worker threads (#14825)tagNamewhen name is not provided toTraceDirective(#14828)openTelemetrySpanProcessorsoption (#14853)Setas theallRoutescontainer. (#14878) (#14884)normalizedRequesttosamplingContext(#14903)syncFeedbackIntegration(#14918)Work in this release was contributed by @arturovt. Thank you for your contribution!
Bundle size 📦
v8.47.0Compare Source
updateSpanNamehelper function (#14736)db.systemin newer Prisma versions (#14772)Work in this release was contributed by @aloisklink and @benjick. Thank you for your contributions!
Bundle size 📦
v8.46.0Compare Source
Work in this release was contributed by @conor-ob. Thank you for your contribution!
Bundle size 📦
v8.45.1Compare Source
sendFeedbackpromise resolves (#14683)Bundle size 📦
v8.45.0Compare Source
handledoption tocaptureConsoleIntegration(#14664)HttpClientevents (#14515)captureMessagewithattachStacktrace: trueas synthetic (#14668)captureMessagewithattatchStackTrace: trueas synthetic (#14670)levelin server runtimecaptureException(#10587)Work in this release was contributed by @anonrig and @Zih0. Thank you for your contributions!
v8.44.0Compare Source
Deprecations
feat: Deprecate
autoSessionTracking(#14640)Deprecates
autoSessionTracking.To enable session tracking, it is recommended to unset
autoSessionTrackingand ensure that either, in browser environmentsthe
browserSessionIntegrationis added, or in server environments thehttpIntegrationis added.To disable session tracking, it is recommended to unset
autoSessionTrackingand to remove thebrowserSessionIntegrationinbrowser environments, or in server environments configure the
httpIntegrationwith thetrackIncomingRequestsAsSessionsoption set tofalse.Other Changes
responsecontext for http.server spans (#14634)Work in this release was contributed by @robinvw1. Thank you for your contribution!
v8.43.0Compare Source
Important Changes
feat(nuxt): Add option autoInjectServerSentry (no default import()) (#14553)
Using the dynamic
import()as the default behavior for initializing the SDK on the server-side did not work for every project.The default behavior of the SDK has been changed, and you now need to use the
--importflag to initialize Sentry on the server-side to leverage full functionality.Example with
--import:In case you are not able to use the
--importflag, you can enable auto-injecting Sentry in thenuxt.config.ts(comes with limitations):feat(browser): Adds LaunchDarkly and OpenFeature integrations (#14207)
Adds browser SDK integrations for tracking feature flag evaluations through the LaunchDarkly JS SDK and OpenFeature Web SDK:
feat(browser): Add
featureFlagsIntegrationfor custom tracking of flag evaluations (#14582)Adds a browser integration to manually track feature flags with an API. Feature flags are attached to subsequent error events:
feat(astro): Add Astro 5 support (#14613)
With this release, the Sentry Astro SDK officially supports Astro 5.
Deprecations
feat(nextjs): Deprecate typedef for
hideSourceMaps(#14594)The functionality of
hideSourceMapswas removed in version 8 but was forgotten to be deprecated and removed.It will be completely removed in the next major version.
feat(core): Deprecate APIs around
RequestSessions (#14566)The APIs around
RequestSessions are mostly used internally.Going forward the SDK will not expose concepts around
RequestSessions.Instead, functionality around server-side Release Health will be managed in integrations.
Other Changes
browserSessionIntegration(#14551)raw_securityenvelope types (#14562)disableAnrDetectionForCallbackfunction (#14359)trackIncomingRequestsAsSessionsoption to http integration (#14567)autoInjectServerSentry(no defaultimport()) (#14553)^1.29.0(#14590)1.28.0(#14547)filenameandmodulestack frame properties in Node stack parser (#14544)maxSpanWaitDurationvalues (#14632)parseSearchoption in TanStack Router instrumentation (#14328)Work in this release was contributed by @lsmurray. Thank you for your contribution!
v8.42.0Compare Source
Important Changes
feat(react): React Router v7 support (library) (#14513)
This release adds support for React Router v7 (library mode).
Check out the docs on how to set up the integration: Sentry React Router v7 Integration Docs
Deprecations
feat: Warn about source-map generation (#14533)
In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application.
Currently, the implementation varies a lot between different SDKs and can be difficult to understand.
Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off.
Additionally, if we end up enabling source maps, we will emit a log message that we did so.
With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.
feat(nuxt): Deprecate
tracingOptionsin favor ofvueIntegration(#14530)Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:
Sentry.init()tracingOptionsinSentry.init()For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported
vueIntegration()and itstracingOptionsoption to configure tracing options in the Nuxt SDK:Other Changes
web-vitalsto v4.2.4 (#14439)vueIntegration(#14526)Bundle size 📦
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 was generated by Mend Renovate. View the repository job log.