[Snyk] Upgrade @sentry/sveltekit from 10.12.0 to 10.14.0 #2494
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.
Snyk has created this PR to upgrade @sentry/sveltekit from 10.12.0 to 10.14.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 2 versions ahead of your current version.
The recommended version was released 22 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-COOKIE-8163060
SNYK-JS-SIRV-12558119
SNYK-JS-VITE-12558116
Release notes
Package name: @sentry/sveltekit
Important Changes
feat(cloudflare,vercel-edge): Add support for Google Gen AI instrumentation (#17723)
The SDK now supports manually instrumenting Google's Generative AI operations in Cloudflare Workers and Vercel Edge Runtime environments, providing insights into your AI operations. You can use
const wrappedClient = Sentry.instrumentGoogleGenAIClient(genAiClient)
to get an instrumented client.Other Changes
WeakRef
when storing it on spans (#17712)Internal Changes
Bundle size 📦
Important Changes
feat(browser): Add option to explicitly end pageload span via
reportPageLoaded()
(#17697)With this release you can take manual control of ending the pageload span. Usually this span is ended automatically by the SDK, based on a period of inactivity after the initial page was loaded in the browser. If you want full control over the pageload duration, you can tell Sentry, when your page was fully loaded:
//...
integrations: [
// 1. Enable manual pageload reporting
Sentry.browserTracingIntegration({ enableReportPageLoaded: true }),
],
});
// 2. Whenever you decide the page is loaded, call:
Sentry.reportPageLoaded();
Note that if
Sentry.reportPageLoaded()
is not called within 30 seconds of the initial pageload (or whatever value thefinalTimeout
option is set to), the pageload span will be ended automatically.feat(core,node): Add instrumentation for
GoogleGenerativeAI
(#17625)The SDK now automatically instruments the
@ google/generative-ai
package to provide insights into your AI operations.feat(nextjs): Promote
useRunAfterProductionCompileHook
to non-experimental build option (#17721)The
useRunAfterProductionCompileHook
option is no longer experimental and is now a stable build option for Next.js projects.feat(nextjs): Use
afterProductionCompile
hook for webpack builds (#17655)Next.js projects using webpack can opt-in to use the
useRunAfterProductionCompileHook
hook for source map uploads.feat(nextjs): Flip default value for
useRunAfterProductionCompileHook
for Turbopack builds (#17722)The
useRunAfterProductionCompileHook
option is now enabled by default for Turbopack builds, enabling automated source map uploads.feat(node): Do not drop 300 and 304 status codes by default (#17686)
HTTP transactions with 300 and 304 status codes are now captured by default, providing better visibility into redirect and caching behavior.
Other Changes
onSuccess
tohandleCallbackErrors
(#17679)consoleLoggingIntegration
(#17703)os
context (#17720)thirdPartyErrorFilterIntegration
(#17693)this
context for vercel AI instrumentation (#17681)Internal Changes
reportPageLoaded
(#17724)getTestMatrix
(#17673)SyncPromise
where not needed (#17641)ignoreSpans
(#17692)module_metadata
assignment and cleanup functions (#17696)HandleDocumentRequestFunction
(#17680)Work in this release was contributed by @ Olexandr88. Thank you for your contribution!
Bundle size 📦
Important Changes
ref: Add and Adjust error event
mechanism
valuesThis release includes a variety of changes aimed at setting the
mechanism
field on errors captured automatically by the Sentry SDKs. The intention is to clearly mark which instrumentation captured an error. In addition, some instrumentations previously did not yet annotate the error as handled or unhandled which this series of PRs corrects as well.Relevant PRs
Released in
10.12.0
:mechanism
on error events captured by astro middleware (#17613)mechanism
of errors captured in Bun.serve (#17616)mechanisms
and durable object origin (#17618)mechanism
incaptureConsoleIntegration
(#17633)mechanism
(#17622)linkedErrors
mechanism logic (#17600)mechanism
of errors caught byglobalHandlersIntegration
(#17635)mechanism
s (#17543)mechanism
to cron instrumentations (#17544)mechanism.type
to worker thread errors fromchildProcessIntegration
(#17578)mechanism
ofonUnhandledRejection
andonUnhandledException
integrations (#17636)mechanism.type
in error events (#17599)reactErrorHandler
and adjust mechanism inErrorBoundary
(#17602)captureRemixServerException
(#17629)replayIntegration
in debug mode (#17606)mechanism
to error captured bywithSentryErrorBoundary
(#17607)mechanism
of error events (#17646)Released in
10.11.0
:mechanism.type
to errors captured byhttpClientIntegration
(#17254)mechanism.type
inbrowserApiErrorsIntergation
(#17251)mechanism.type
totrpcMiddleware
errors (#17287)mechanism
s and span origins toopenAiIntegration
(#17288)mechanism
to captured errors (#17312)prismaIntegration
works with Prisma 5 (#17595)We used to require to pass in the v5 version of
@ prisma/instrumentation
intoprismaIntegration({ prismaInstrumentation: new PrismaInstrumentation() })
, if you wanted to get full instrumentation for Prisma v5. However, it turns out this does not work on v10 of the SDK anymore, because@ prisma/instrumentation@5
requires OTEL v1.With this release, we dropped the requirement to configure anything to get v5 support of Prisma. You do not need to configure anything in the integration anymore, and can remove the dependency on
@ prisma/instrumentation@5
if you had it in your application. You only need to configure thetracing
preview feature according to our docs.Other Changes
TracesSamplerSamplingContext
type (#17523)prismaIntegration
works with Prisma v5 (#17595)parentSpanId
stays consistent during trace in TwP mode (#17526)step.do
(#17582)_platform
properties in Nitro 2.11.7+ (#17596)shimmer
(#17597) - ref(nuxt): Add and adjustmechanism.type
in error events (#17599)fetchTransport
error handling (#17661)Internal Changes
.claude/settings.local.json
to.claude/settings.json
(#17591)flushIfServerless
test (#17610)Bundle size 📦
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: