-
Notifications
You must be signed in to change notification settings - Fork 5
Update dependency @sentry/node to v10 #886
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
abee8b4
to
73d8237
Compare
8b35b70
to
50d4a74
Compare
eb444de
to
0624254
Compare
0624254
to
e3e244a
Compare
Here's the code health analysis summary for commits Analysis Summary
|
4a74cc5
to
c6ed005
Compare
c6ed005
to
b0d5eaa
Compare
6a9a3ff
to
644c04d
Compare
644c04d
to
294525c
Compare
d519662
to
883cfca
Compare
f61707f
to
9b496b5
Compare
bc3b796
to
4587196
Compare
f62e871
to
4d84ad0
Compare
3f0b363
to
c4ac212
Compare
6e46b7f
to
f922d63
Compare
f922d63
to
f7961a1
Compare
This PR contains the following updates:
^7.56.0
->^10.0.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
getsentry/sentry-javascript (@sentry/node)
v10.20.0
Compare Source
Important Changes
feat(flags): Add Growthbook integration (#17440)
Adds a new Growthbook integration for feature flag support.
feat(solid): Add support for TanStack Router Solid (#17735)
Adds support for TanStack Router in the Solid SDK, enabling better routing instrumentation for Solid applications.
feat(nextjs): Support native debugIds in turbopack (#17853)
Adds support for native Debug IDs in Turbopack, improving source map resolution and error tracking for Next.js applications using Turbopack. Native Debug ID generation will be enabled automatically for compatible versions.
Other Changes
pino
logger name (#17930)POP
guard for long-runningpageload
spans (#17867)Internal Changes
- chore(nextjs): Add Next.js 16 peer dependency ([#17925](https://redirect.github.com/getsentry/sentry-javascript/pull/17925)) - chore(ci): Update Next.js canary testing ([#17939](https://redirect.github.com/getsentry/sentry-javascript/pull/17939)) - chore: Bump size limit ([#17941](https://redirect.github.com/getsentry/sentry-javascript/pull/17941)) - test(nextjs): Add next@16 e2e test ([#17922](https://redirect.github.com/getsentry/sentry-javascript/pull/17922)) - test(nextjs): Update next 15 tests ([#17919](https://redirect.github.com/getsentry/sentry-javascript/pull/17919)) - chore: Add external contributor to CHANGELOG.md ([#17915](https://redirect.github.com/getsentry/sentry-javascript/pull/17915)) - chore: Add external contributor to CHANGELOG.md ([#17928](https://redirect.github.com/getsentry/sentry-javascript/pull/17928)) - chore: Add external contributor to CHANGELOG.md ([#17940](https://redirect.github.com/getsentry/sentry-javascript/pull/17940))Work in this release was contributed by @seoyeon9888, @madhuchavva and @thedanchez . Thank you for your contributions!
Bundle size 📦
v10.19.0
Compare Source
Internal Changes
Bundle size 📦
v10.18.0
Compare Source
v10.17.0
Compare Source
Important Changes
feat(nuxt): Implement server middleware instrumentation (#17796)
This release introduces instrumentation for Nuxt middleware, ensuring that all middleware handlers are automatically wrapped with tracing and error reporting functionality.
fix(aws-serverless): Take
http_proxy
into account when choosinguseLayerExtension
default (#17817)The default setting for
useLayerExtension
now considers thehttp_proxy
environment variable.When
http_proxy
is set,useLayerExtension
will be off by default.If you use a
http_proxy
but would still like to make use of the Sentry Lambda extension, exemptlocalhost
in ano_proxy
environment variable.Other Changes
beforeSendSpan
(#17815)Internal Changes
v10.16.0
Compare Source
replay_is_buffering
flag (#17752)instrumentAnthropicAiClient
breaking MessageStream api (#17754)Internal Changes
publish_release
command (#17797)import-in-the-middle
when building the Lambda layer (#17780)import-in-the-middle@1.14.2
due to@vercel/nft
incompatibility (#17777)" (#17784)import-in-the-middle@1.14.2
due to@vercel/nft
incompatibility (#17777)v10.15.0
Compare Source
Important Changes
feat(cloudflare): Add honoIntegration with error-filtering function (#17743)
This release adds a
honoIntegration
to@sentry/cloudflare
, which exposes ashouldHandleError
function that lets you define which errors inonError
should be captured.By default, Sentry captures exceptions with
error.status >= 500 || error.status <= 299
.The integration is added by default, and it's possible to modify this behavior like this:
feat(node): Add instrumentation for hono handler (#17428)
This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.
feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)
feat(browser): Add
setActiveSpanInBrowser
to set an active span in the browser (#17714)This PR adds a feature to the browser SDKs only: Making an inactive span active. We do this to enable use cases where having a span only being active in the callback is not practical.
Other Changes
0
andundefined
resource timing values (#17751)Internal Changes
@typescript-eslint/no-unnecessary-type-assertion
rule (#17728)es2020
everywhere (#17709)Work in this release was contributed by @Karibash. Thank you for your contribution!
v10.14.0
Compare Source
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
v10.13.0
Compare Source
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:
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!
v10.12.0
Compare Source
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)v10.11.0
Compare Source
Important Changes
feat(aws): Add experimental AWS Lambda extension for tunnelling events (#17525)
This release adds an experimental Sentry Lambda extension to the existing Sentry Lambda layer. Sentry events are now tunneled through the extension and then forwarded to Sentry. This has the benefit of reducing the request processing time.
To enable it, set
_experiments.enableLambdaExtension
in your Sentry config like this:Other Changes
handleExistingNavigation
(#17534)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)Internal Changes
test-utils
dependency in workspace (#17538)geist
font (#17541)v10.10.0
Compare Source
Important Changes
propagateTraceparent
SDK option (#17509)Adds support for a new browser SDK init option,
propagateTraceparent
for attaching a W3C compliant traceparent header to outgoing fetch and XHR requests, in addition to sentry-trace and baggage headers. More details can be found here.Adds missing tool call attributes, we add gen_ai.response.tool_calls attribute for Anthropic AI, supporting both streaming and non-streaming requests.
Adds a new experimental flag
_experimental.useRunAfterProductionCompileHook
towithSentryConfig
for automatic source maps uploads when building a Next.js app withnext build --turbopack
.When set we:
Other Changes
origin
for OpenAI spans & test auto instrumentation (#17519)Bundle size 📦
v10.9.0
Compare Source
Important Changes
httpIntegration
handling of incoming requests (#17371)This version updates the handling of the Node SDK of incoming requests. Instead of relying on @opentelemetry/instrumentation-http, we now handle incoming request instrumentation internally, ensuring that we can optimize performance as much as possible and avoid interop problems.
This change should not affect you, unless you're relying on very in-depth implementation details. Importantly, this also drops the
_experimentalConfig
option of the integration - this will no longer do anything.Finally, you can still pass
instrumentation.{requestHook,responseHook,applyCustomAttributesOnSpan}
options, but they are deprecated and will be removed in v11. Instead, you can use the newincomingRequestSpanHook
configuration option if you want to adjust the incoming request span.Other Changes
sendFeedback
from CDN bundles (#17495)beforeStartSpan
isn't overwritten (#17500)beforeStartSpan
(#17501)Sentry.close()
(#17499)Internal Changes
changelog
script back to package.json (#17517)Bundle size 📦
| Path | Size |
| ---
Configuration
📅 Schedule: Branch creation - 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 ) in timezone Australia/Sydney, 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.