chore(deps): update dependency @sentry/nextjs to v8.55.2 - #1605
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency @sentry/nextjs to v8.55.2#1605renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
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:
8.50.0→8.55.2Release Notes
getsentry/sentry-javascript (@sentry/nextjs)
v8.55.2Compare Source
v8on when publishing to NPM (#19974)v8.55.1Compare Source
gmoerror and Facebook mobile error (#15447)v8.55.0Compare Source
Important Changes
SentryNodeServerlessSDKv8(#15351)The
SentryNodeServerlessSDKAWS Lambda Layer will stop receiving updates.If you intend to stay on
v8and receive updates useSentryNodeServerlessSDKv8instead.Other Changes
vercelAIIntegrationexport (#15339)enabledto disable Sentry module (#15337) (#15381)registerEsmLoaderHooks(#15352)beforeUpdatecall (#15262)Work in this release was contributed by @aryanvdesh. Thank you for your contribution!
Bundle size 📦
v8.54.0Compare Source
Work in this release was contributed by @nwalters512. Thank you for your contribution!
Bundle size 📦
v8.53.0Compare Source
urltoSourcemapsUploadOptions(#15202)fromLocationcan be undefined in Tanstack Router Instrumentation (#15237)Work in this release was contributed by @tannerlinsley. Thank you for your contribution!
Bundle size 📦
v8.52.1Compare Source
this.nametonew.target.prototype.constructor.name(#15222)Work in this release was contributed by @Zen-cronic. Thank you for your contribution!
Bundle size 📦
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 📦
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.