fix(deps): update dependency @sentry/browser to v10 #3220
+37
−37
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.33.0
->^10.0.0
Release Notes
getsentry/sentry-javascript (@sentry/browser)
v10.1.0
Compare Source
diagnoseSdkConnectivity
doesn't create span (#17280)v10.0.0
Compare Source
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/
A comprehensive migration guide outlining all changes can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md
Breaking Changes
BaseClient
(#17071)enableLogs
andbeforeSendLog
experimental options (#17063)hasTracingEnabled
(#17072)_experiments.autoFlushOnFeedback
option as default (#17220)Other Changes
SentryNodeServerlessSDKv10
v10 AWS Lambda Layer (#17069)flushIfServerless
function (#17177)strictTraceContinuation
(#16313)@sentry-internal/node-native-stacktrace
to0.2.2
(#17207)shouldHandleError
option tofastifyIntegration
(#16845)createSentryHandleError
(#17235)fastifyIntegration
error handler (#17208)vercelAiIntegration
have correct trace connected (#17132)handleErrorWithSentry
(#17157)Work in this release was contributed by @richardjelinek-fastest. Thank you for your contribution!
Bundle size 📦
v9.45.0
Compare Source
openai
to the instrumented fn (#17353)Bundle size 📦
v9.44.2
Compare Source
This release is publishing the AWS Lambda Layer under
SentryNodeServerlessSDKv9
. The previous release9.44.1
accidentally published the layer underSentryNodeServerlessSDKv10
.v9.44.1
Compare Source
v9.44.0
Compare Source
_experiments.autoFlushOnFeedback
(#17219)flushIfServerless
function (#17239)@sentry-internal/node-native-stacktrace
to0.2.2
(#17256)createSentryHandleError
(#17244)Bundle size 📦
v9.43.0
Compare Source
fastifyIntegration
error handler (#17211)Bundle size 📦
v9.42.1
Compare Source
globalThis
(#17185)handleErrorWithSentry
(#17174)Bundle size 📦
v9.42.0
Compare Source
Bundle size 📦
v9.41.0
Compare Source
v9.40.0
Compare Source
Important Changes
This release adds two Browser SDK APIs to let the main thread know about debugIds of worker files:
webWorkerIntegration({worker})
to be used in the main threadregisterWebWorker({self})
to be used in the web workerThe internal SDK
logger
export from@sentry/core
has been deprecated in favor of thedebug
export.debug
only exposeslog
,warn
, anderror
methods but is otherwise identical tologger
. Note that this deprecation does not affect thelogger
export from other packages (like@sentry/browser
or@sentry/node
) which is used for Sentry Logging.This release adds official support for instrumenting OpenAI SDK calls in with Sentry tracing, following OpenTelemetry semantic conventions for Generative AI. It instruments:
client.chat.completions.create()
- For chat-based completionsclient.responses.create()
- For the responses APIOther Changes
@opentelemetry/instrumentation
range to cover0.203.0
(#17043)Work in this release was contributed by @0xbad0c0d3 and @tommy-gilligan. Thank you for your contributions!
Bundle size 📦
v9.39.0
Compare Source
Important Changes
afterStartPageloadSpan
hook to improve spanId assignment on web vital spans (#16893)This PR adds a new afterStartPageloadSpan lifecycle hook to more robustly assign the correct pageload span ID to web vital spans, replacing the previous unreliable "wait for a tick" approach with a direct callback that fires when the pageload span becomes available.
This PR implements client-side parameterized routes for Next.js by leveraging an injected manifest within the existing app-router instrumentation to automatically parameterize all client-side transactions (e.g.
users/123
andusers/456
now become becomeusers/:id
).This PR changes the default behavior in the Node SDK to drop HTTP spans with 401-404 and 3xx status codes by default to reduce noise in tracing data.
Other Changes
vercel.ai.X
(#16908)disableSentryWebpackConfig
flag (#17013)tracing/errors.ts
(#16888)beforeSendLog
inconsoleSandbox
(#16968)source=route
(#16984)Work in this release was contributed by @janpapenbrock. Thank you for your contribution!
Bundle size 📦
v9.38.0
Compare Source
Important Changes
This release publishes the
@sentry/node-native
SDK.Other Changes
debug
to replacelogger
(#16906)nextHopProtocol
when adding resource spans (#16900)Bundle size 📦
v9.37.0
Compare Source
Important Changes
feat(nuxt): Parametrize SSR routes (#16843)
When requesting dynamic or catch-all routes in Nuxt, those will now be shown as parameterized routes in Sentry.
For example,
/users/123
will be shown as/users/:userId()
in Sentry. This will make it easier to identify patterns and make grouping easier.Other Changes
beforeStartNavigationSpan
lifecycle hook (#16863)wrapRequestHandler
(#16852)instrumentation-client.ts|js
(#16855)redirect()
calls as errors in Cloudflare (#16853)deleteSourcemapsAfterUpload
jsdoc default value (#16867)Work in this release was contributed by @zachkirsch. Thank you for your contribution!
Bundle size 📦
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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.