forked from getsentry/sentry-react-native
-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): update JavaScript SDK to v10.20.0 #3
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
Open
github-actions
wants to merge
1
commit into
main
Choose a base branch
from
deps/scripts/update-javascript.sh
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
8e7dc05
to
72a8684
Compare
72a8684
to
749b0e2
Compare
23fe7b8
to
097dd1a
Compare
097dd1a
to
f6ac530
Compare
f6ac530
to
8b26284
Compare
8b26284
to
0e75936
Compare
86fb041
to
03f5fec
Compare
03f5fec
to
7e57fa7
Compare
43cb4c4
to
8bcfe56
Compare
89e6bbb
to
4c77f85
Compare
4c77f85
to
d4b2354
Compare
3ef5bca
to
1106330
Compare
1106330
to
f48d930
Compare
f48d930
to
fbd97a7
Compare
fbd97a7
to
991065f
Compare
991065f
to
bf11736
Compare
bf11736
to
e5e79ae
Compare
e5e79ae
to
2e7979e
Compare
2e7979e
to
39e32f4
Compare
39e32f4
to
c6e1d96
Compare
c6e1d96
to
dc9dfd5
Compare
dc9dfd5
to
807081f
Compare
d24204a
to
0704b47
Compare
0704b47
to
8e73779
Compare
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.
Bumps scripts/update-javascript.sh from 8.55.0 to 10.20.0.
Auto-generated by a dependency updater.
Changelog
10.20.0
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://github-redirect.dependabot.com/getsentry/sentry-javascript/pull/17925)) - chore(ci): Update Next.js canary testing ([#17939](https://github-redirect.dependabot.com/getsentry/sentry-javascript/pull/17939)) - chore: Bump size limit ([#17941](https://github-redirect.dependabot.com/getsentry/sentry-javascript/pull/17941)) - test(nextjs): Add next16 e2e test ([#17922](https://github-redirect.dependabot.com/getsentry/sentry-javascript/pull/17922)) - test(nextjs): Update next 15 tests ([#17919](https://github-redirect.dependabot.com/getsentry/sentry-javascript/pull/17919)) - chore: Add external contributor to CHANGELOG.md ([#17915](https://github-redirect.dependabot.com/getsentry/sentry-javascript/pull/17915)) - chore: Add external contributor to CHANGELOG.md ([#17928](https://github-redirect.dependabot.com/getsentry/sentry-javascript/pull/17928)) - chore: Add external contributor to CHANGELOG.md ([#17940](https://github-redirect.dependabot.com/getsentry/sentry-javascript/pull/17940))Work in this release was contributed by seoyeon9888, madhuchavva and thedanchez. Thank you for your contributions!
10.19.0
Internal Changes
10.18.0
Important Changes
feat(node):
pino
integration (#17584)This release adds a new
pino
integration for Node.js, enabling Sentry to capture logs from the Pino logging library.feat: Remove sentry/pino-transport package (#17851)
The
sentry/pino-transport
package has been removed. Please use the newpino
integration insentry/node
instead.feat(node-core): Extend onnhandledrejection with ignore errors option (#17736)
Added support for selectively suppressing specific errors with configurable logging control in onnhandledrejection integration.
Other Changes
sentry.client.config.ts
in nuxt app types (#17830)OriginalHandleRequest
with middleware (#17870)Internal Changes
Work in this release was contributed by stefanvanderwolf. Thank you for your contribution!
10.17.0
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
10.16.0
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-middle1.14.2
due tovercel/nft
incompatibility (#17777)" (#17784)import-in-the-middle1.14.2
due tovercel/nft
incompatibility (#17777)10.15.0
Important Changes
feat(cloudflare): Add honoIntegration with error-filtering function (#17743)
This release adds a
honoIntegration
tosentry/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!
10.14.0
Important Changes
feat(cloudflare,vercel-edge): Add support for Google Gen AI instrumentation (#17723)
The SDK now supports manually instrumenting Google's Gen 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
10.13.0
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
GoogleGenAI
(#17625)The SDK now automatically instruments the
google/genai
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!
10.12.0
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, becauseprisma/instrumentation5
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/instrumentation5
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)10.11.0
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)10.10.0
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)10.9.0
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)10.8.0
Important Changes
feat(sveltekit): Add Compatibility for builtin SvelteKit Tracing (#17423)
This release makes the
sentry/sveltekit
SDK compatible with SvelteKit's native observability support introduced in SvelteKit version2.31.0
.If you enable both, instrumentation and tracing, the SDK will now initialize early enough to set up additional instrumentation like database queries and it will pick up spans emitted from SvelteKit.
We will follow up with docs how to set up the SDK soon.
For now, If you're on SvelteKit version
2.31.0
or newer, you can easily opt into the new feature:Enable experimental tracing and instrumentation support in
svelte.config.js
:Move your
Sentry.init()
call fromsrc/hooks.server.(js|ts)
to the newinstrumentation.server.(js|ts)
file:The rest of your Sentry config in
hooks.server.ts
(sentryHandle
andhandleErrorWithSentry
) should stay the same.If you prefer to stay on the hooks-file based config for now, the SDK will continue to work as previously.
Thanks to the Svelte team and elliott-with-the-longest-name-on-github for implementing observability support and for reviewing our PR!
Other Changes
Internal Changes
10.7.0
Important Changes
instrumentPrototypeMethods
option to instrument RPC methods for DurableObjects (#17424)By default,
Sentry.instrumentDurableObjectWithSentry
will not wrap any RPC methods on the prototype. To enable wrapping for RPC methods, setinstrumentPrototypeMethods
totrue
or, if performance is a concern, a list of only the methods you want to instrument:Other Changes
requestAnimationFrame
for canvas snapshots (#17380)Internal Changes
10.6.0
Important Changes
This release adds support for automatically tracing Anthropic AI SDK requests, providing better observability for AI-powered applications.
ai
v5 (#17395)This release makes the Sentry
vercelAiIntegration
compatible with version 5 of Vercelai
.The Sentry Nuxt SDK is now considered stable and no longer in beta!
Other Changes
DedicatedWorkerGlobalScope
global object type inregisterWebWorker
(#17447)isSentryRequestUrl
(#17393)Internal Changes
10.5.0
SystemError
context and remove paths from message (#17331)Internal Changes
Work in this release was contributed by ha1fstack. Thank you for your contribution!
10.4.0
Important Changes
sendDefaultPii
istrue
This release includes a fix for a behaviour change
that was originally introduced with v9 of the SDK: User IP Addresses should only be added to Sentry events automatically,
if
sendDefaultPii
was set totrue
.However, the change in v9 required further internal adjustment, which should have been included in v10 of the SDK.
Unfortunately, the change did not make it into the initial v10 version but is now applied with
10.4.0
.There is no API breakage involved and hence it is safe to update.
However, after updating the SDK, events (errors, traces, replays, etc.) sent from the browser, will only include
user IP addresses, if you set
sendDefaultPii: true
in yourSentry.init
options.We apologize for any inconvenience caused!
ignoreStaticAssets
(#17370)This release adds a new option to
httpIntegration
to ignore requests for static assets (e.g.favicon.xml
orrobots.txt
). The option defaults totrue
, meaning that going forward, such requests will not be traced by default. You can still enable tracing for these requests by setting the option tofalse
:Other Changes
Internal Changes
10.3.0
skipOpenTelemetrySetup
option (#17349)globalHandlersIntegration
(#17216)handle
(#17277)10.2.0
Important Changes
ignoreSpans
option (#17078)This release adds a new top-level
Sentry.init
option,ignoreSpans
, that can be used as follows:Spans matching the filter criteria will not be recorded. Potential child spans of filtered spans will be re-parented, if possible.
Adds support for OpenAI manual instrumentation in
sentry/cloudflare
andsentry/vercel-edge
.To instrument the OpenAI client, wrap it with
Sentry.instrumentOpenAiClient
and set recording settings.The
startTrace
option is deprecated and will be removed in a future major version. If you want to disable tracing, setSENTRY_TRACES_SAMPLE_RATE
to0.0
. instead. As of today, the flag does not affect traces anymore.Other Changes
gen_ai.invoke_agent
spans from child LLM calls (#17281)sentry.origin
span attribute toSentryTraced
decorator (#17318)openai
to the instrumented fn (#17320)sendBufferedReplayOrFlush
when opening/sending feedback (#17236)10.1.0
diagnoseSdkConnectivity
doesn't create span (#17280)10.0.0
Version
10.0.0
marks a release of the Sentry JavaScript SDKs that contains breaking changes. The goal of this release is to primarily upgrade the underlying OpenTelemetry dependencies to v2 with minimal breaking changes.How To Upgrade
Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 9 to version 10. Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v9-to-v10/