You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(ci/v8): Switch lambda layer name to SentryNodeServerlessSDKv8 (#15351)
The SentryNodeServerlessSDK AWS Lambda Layer will stop receiving updates.
If you intend to stay on v8 and receive updates use SentryNodeServerlessSDKv8 instead.
feat(solidstart): Add withSentry wrapper for SolidStart config (#15135)
To enable the SolidStart SDK, wrap your SolidStart Config with withSentry. The sentrySolidStartVite plugin is now automatically
added by withSentry and you can pass the Sentry build-time options like this:
import{defineConfig}from'@​solidjs/start/config';import{withSentry}from'@​sentry/solidstart';exportdefaultdefineConfig(withSentry({/* Your SolidStart config options... */},{// Options for setting up source mapsorg: process.env.SENTRY_ORG,project: process.env.SENTRY_PROJECT,authToken: process.env.SENTRY_AUTH_TOKEN,},),);
With the withSentry wrapper, the Sentry server config should not be added to the public directory anymore.
Add the Sentry server config in src/instrument.server.ts. Then, the server config will be placed inside the server build output as instrument.server.mjs.
Now, there are two options to set up the SDK:
(recommended) Provide an --import CLI flag to the start command like this (path depends on your server setup): node --import ./.output/server/instrument.server.mjs .output/server/index.mjs
Add autoInjectServerSentry: 'top-level-import' and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)
withSentry({/* Your SolidStart config options... */},{// Optional: Install Sentry with a top-level importautoInjectServerSentry: 'top-level-import',},);
Other Changes
feat(v8/core): Add client outcomes for breadcrumbs buffer (#15149)
feat(v8/core): Improve error formatting in ZodErrors integration (#15155)
fix(v8/bun): Ensure instrumentation of Bun.serve survives a server reload (#15157)
fix(v8/core): Pass module into loadModule (#15139) (#15166)
feat(v8/node): Add prismaInstrumentation option 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/instrumentation package on version 6.
Pass a new PrismaInstrumentation() instance as exported from @prisma/instrumentation to the prismaInstrumentation option:
import{PrismaInstrumentation}from'@​prisma/instrumentation';Sentry.init({integrations: [prismaIntegration({// Override the default instrumentation that Sentry usesprismaInstrumentation: newPrismaInstrumentation(),}),],});
The passed instrumentation instance will override the default instrumentation instance the integration would use, while the prismaIntegration will still ensure data compatibility for the various Prisma versions.
Remove the previewFeatures = ["tracing"] option from the client generator block of your Prisma schema.
📅 Schedule: Branch creation - On day 1 of the month ( * * 1 * * ) (UTC), Automerge - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) (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.
If you want to rebase/retry this PR, check this box
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.113.0
fix(deps): update dependency @sentry/react to v7.114.0
May 8, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.114.0
fix(deps): update dependency @sentry/react to v7.115.0
May 16, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.115.0
fix(deps): update dependency @sentry/react to v7.116.0
May 17, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.116.0
fix(deps): update dependency @sentry/react to v7.117.0
Jun 11, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.117.0
fix(deps): update dependency @sentry/react to v7.118.0
Jun 21, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.118.0
fix(deps): update dependency @sentry/react to v7.119.0
Aug 14, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.119.0
fix(deps): update dependency @sentry/react to v7.119.1
Oct 4, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.119.1
fix(deps): update dependency @sentry/react to v7.119.2
Oct 10, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.119.2
fix(deps): update dependency @sentry/react to v7.120.0
Nov 13, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.120.0
fix(deps): update dependency @sentry/react to v7.120.1
Dec 5, 2024
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.120.1
fix(deps): update dependency @sentry/react to v7.120.2
Dec 13, 2024
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.120.2
fix(deps): update dependency @sentry/react to v7.120.3
Jan 10, 2025
renovatebot
changed the title
fix(deps): update dependency @sentry/react to v7.120.3
fix(deps): update dependency @sentry/react to v8.55.0
Jun 19, 2025
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
dependenciesPull requests that update a dependency file
0 participants
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.20.0→8.55.0Release Notes
getsentry/sentry-javascript (@sentry/react)
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 📦
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 📦
Configuration
📅 Schedule: Branch creation - On day 1 of the month ( * * 1 * * ) (UTC), Automerge - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) (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.