-
Notifications
You must be signed in to change notification settings - Fork 111
fix(deps): update sentry sdk (major) #679
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
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-sentry-sdk
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.
Open
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
731bebf
to
e5dfdc6
Compare
2f952ad
to
c5fba93
Compare
f087a6d
to
b8b94df
Compare
d788adf
to
aad30cb
Compare
jmkoenig
added a commit
to cbsi-cmg/sentry-module
that referenced
this pull request
Jun 26, 2024
8cc1854
to
15f81d8
Compare
a70d9d5
to
ccc6956
Compare
a62d957
to
222a240
Compare
f1d9152
to
7b9c8d5
Compare
9498476
to
2de5fd8
Compare
8c98c5c
to
3ed9fca
Compare
5f5b27c
to
54dfeb0
Compare
5329869
to
da642a8
Compare
d2dadca
to
5803dab
Compare
7e26c50
to
c3b8f01
Compare
f004cef
to
81a536d
Compare
5e9be50
to
633d2a4
Compare
e652e7a
to
5efb208
Compare
5e8498a
to
622a6f8
Compare
622a6f8
to
1f4369e
Compare
1f4369e
to
7790305
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
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:
^7.119.0
->^9.14.0
^7.119.0
->^9.14.0
7.119.0
->9.14.0
^7.119.0
->^8.55.0
^7.119.0
->^9.14.0
2.22.3
->3.3.1
Release Notes
getsentry/sentry-javascript (@sentry/core)
v9.14.0
Compare Source
Important Changes
This PR adds Supabase integration to
@sentry/core
, allowing automatic instrumentation of Supabase client operations (database queries and authentication) for performance monitoring and error tracking.SentryGlobalFilter
(#16066)This PR adds better RPC exception handling to
@sentry/nestjs
, preventing application crashes while still capturing errors and warning users when a dedicated filter is needed. The implementation gracefully handles the 'rpc' context type inSentryGlobalFilter
to improve reliability in hybrid applications.This PR adds trace propagation to
@sentry/react-router
by providing utilities to inject trace meta tags into HTML headers and offering a pre-built Sentry-instrumented request handler, improving distributed tracing capabilities across page loads.Other Changes
Bundle size 📦
v9.13.0
Compare Source
Important Changes
feat(node): Add support for winston logger (#15983)
Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like
@sentry/nestjs
). The Logging APIs in the Sentry SDK are still experimental and subject to change.feat(core): Add
wrapMcpServerWithSentry
to instrument MCP servers from@modelcontextprotocol/sdk
(#16032)The Sentry SDK now supports instrumenting MCP servers from the
@modelcontextprotocol/sdk
package. Compatible with versions^1.9.0
of the@modelcontextprotocol/sdk
package.feat(core): Move console integration into core and add to cloudflare/vercel-edge (#16024)
Console instrumentation has been added to
@sentry/cloudflare
and@sentry/nextjs
Edge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.feat(bun): Support new
Bun.serve
APIs (#16035)Bun
1.2.6
and above have a newBun.serve
API, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.Thanks to @Jarred-Sumner for helping us get this supported!
Other Changes
browserTracingIntegration
(#16042)beforeSendLog
after we process log (#16019)unstable_sentryVitePluginOptions
to cli instance (#16033)v9.12.0
Compare Source
v9.11.0
Compare Source
http.redirect_count
attribute tobrowser.redirect
span (#15943)consoleLoggingIntegration
for logs (#15955)turbopack
as tag (#15928)sentryHandleRequest
(#15787)module
instead ofrequire
for CJS check (#15927)ErrorBoundary
wrapper (#15930)sentry.previous_trace
span attribute (#15957)Bundle size 📦
v9.10.1
Compare Source
3.2.4
(#15909)v9.10.0
Compare Source
Important Changes
feat: Add support for logs
beforeSendLog
(#15814)All JavaScript SDKs other than
@sentry/cloudflare
and@sentry/deno
now support sending logs via dedicated methods as part of Sentry's upcoming logging product.Logging is gated by an experimental option,
_experiments.enableLogs
.With server-side SDKs like
@sentry/node
,@sentry/bun
or server-side of@sentry/nextjs
or@sentry/sveltekit
, you can do structured logging without needing thefmt
helper function.To filter logs, or update them before they are sent to Sentry, you can use the
_experiments.beforeSendLog
option.feat(browser): Add
diagnoseSdkConnectivity()
function to programmatically detect possible connectivity issues (#15821)The
diagnoseSdkConnectivity()
function can be used to programmatically detect possible connectivity issues with the Sentry SDK.The result will be an object with the following properties:
"no-client-active"
: There was no active client when the function was called. This possibly means that the SDK was not initialized yet."sentry-unreachable"
: The Sentry SaaS servers were not reachable. This likely means that there is an ad blocker active on the page or that there are other connection issues.undefined
: The SDK is working as expected.SDK Tracing Performance Improvements for Node SDKs
dropUndefinedKeys
(#15796)dropUndefinedKeys
forspanToJSON
calls (#15792)SentryError
for PromiseBuffer control flow (#15822)dropUndefinedKeys
in SpanExporter (#15794)SentryError
for event processing control flow (#15823)dropUndefinedKeys
in Node SDK init (#15797)We've been hard at work making performance improvements to the Sentry Node SDKs (
@sentry/node
,@sentry/aws-serverless
,@sentry/nestjs
, etc.). We've seen that upgrading from9.7.0
to9.10.0
leads to 30-40% improvement in request latency for HTTP web-server applications that use tracing with high sample rates. Non web-server applications and non-tracing applications will see smaller improvements.Other Changes
rrweb
to2.35.0
(#15825)3.2.3
(#15829)v9.9.0
Compare Source
Important Changes
feat(nextjs): Support
instrumentation-client.ts
(#15705)Next.js recently added a feature to support client-side (browser) instrumentation via the
experimental.clientInstrumentationHook
flag and theinstrumentation-client.ts
file.To be forwards compatible, the Sentry Next.js SDK will now pick up
instrumentation-client.ts
files even on older Next.js versions and add them to your client bundles.It is suggested that you either rename your
sentry.client.config.ts
file toinstrumentation-client.ts
, or if you already happen to have ainstrumentation-client.ts
file move the contents ofsentry.client.config.ts
toinstrumentation-client.ts
.feat(browser): Add
previous_trace
span links (#15569)The
@sentry/browser
SDK and SDKs based on@sentry/browser
now emits a link from the first root span of a newly started trace to the root span of a previously started trace. You can control this feature via an option inbrowserTracingIntegration()
:feat(browser): Add
logger.X
methods to browser SDK (#15763)For Sentry's upcoming logging product, the SDK now supports sending logs via dedicated methods.
Please note that the logs product is still in early access. See the link above for more information.
Other Changes
parseStringToURL
method (#15768)dropUndefinedKeys
(#15760)shouldHandleError
(#15771)addNonEnumerableProperty
(#15766)dropUndefinedKeys()
(#15757)dropUndefinedKeys()
(#15781)v9.8.0
Compare Source
res.end
before passing to Proxy (#15776)eventFilters
integration (#15752)v9.7.0
Compare Source
captureLog
method (#15717)sentryHandleError
(#15726)fatal
level for unhandled rejections instrict
mode (#15720)v9.6.1
Compare Source
v9.6.0
Compare Source
Important Changes
feat(tanstackstart): Add
@sentry/tanstackstart-react
package and make@sentry/tanstackstart
package a utility package (#15629)Since TanStack Start is supposed to be a generic framework that supports libraries like React and Solid, the
@sentry/tanstackstart
SDK package was renamed to@sentry/tanstackstart-react
to reflect that the SDK is specifically intended to be used for React TanStack Start applications.Note that the TanStack Start SDK is still in alpha status and may be subject to breaking changes in non-major package updates.
Other Changes
fill
only patches functions (#15632)pageExtensions
when looking for instrumentation file (#15701)options
(#15610)Work in this release was contributed by @angelikatyborska and @nwalters512. Thank you for your contributions!
v9.5.0
Compare Source
Important Changes
We found some issues with the new feedback screenshot annotation where screenshots are not being generated properly. Due to this issue, we are reverting the feature.
Other Changes
4.34.9
(#15589)@sentry/remix/cloudflare
(#15599)Work in this release was contributed by @msurdi-a8c, @namoscato, and @rileyg98. Thank you for your contributions!
v9.4.0
Compare Source
@sentry/cli
from 2.41.1 to 2.42.2 (#15510)@sentry/webpack-plugin
from 3.1.2 to 3.2.1 (#15512)use client
directive to client SDK entrypoints (#15575)AsyncLocalStorage
async context strategy is used in Cloudflare Pages (#15557)@cloudflare/workers-types
an optional peer dependency (#15554)onRequestError
in version 15 (#15553)undefined
transport to be passed in (#15560)Bundle size 📦
v9.3.0
Compare Source
Important Changes
With this release we're publishing two new SDKs in experimental alpha stage:
For details please refer to the README
For details please refer to the README
This PR adds support for Shopify Hydrogen applications running on MiniOxygen runtime.
Other Changes
forceTransaction
to trpc middleware options (#15519)inboundFiltersIntegration
toeventFiltersIntegration
(#15434)allowUrls
anddenyUrls
for linked and aggregate exceptions (#15521)process
check when flushing events (#15516)Work in this release was contributed by @GerryWilko and @leoambio. Thank you for your contributions!
v9.2.0
Compare Source
Important Changes
This release adds full tracing support for Express v5, and improves tracing support for Nest.js 11 (which uses Express v5) in the Nest.js SDK.
This release adds support for deploying SvelteKit applications to Cloudflare Pages.
A docs update with updated instructions will follow shortly.
Until then, you can give this a try by setting up the SvelteKit SDK as usual and then following the instructions outlined in the PR.
Thank you @SG60 for contributing this feature!
Other Changes
addLink(s)
to Sentry span (#15452)enableNitroErrorHandler
to server options (#15444)addLink(s)
to span (#15387)links
to span options (#15403)performance.measure
spans have a positive duration (#15415)gmo
error to Inbound Filters (#15432)http.client
span descriptions don't contain query params or fragments (#15404)@opentelemetry/instrumentation
(#15419)SentryNuxtServerOptions
type for server init (#15441)Work in this release was contributed by @6farer, @dgavranic and @SG60. Thank you for your contributions!
Bundle size 📦
v9.1.0
Compare Source
graphqlClientIntegration
(#13783)vite
import (#15371)Work in this release was contributed by @Zen-cronic and @filips-alpe. Thank you for your contribution!
v9.0.1
Compare Source
v9.0.0
Compare Source
Version
9.0.0
marks a release of the Sentry JavaScript SDKs that contains breaking changes.The goal of this release is to trim down on unused and potentially confusing APIs, prepare the SDKs for future framework versions to build deeper instrumentation, and remove old polyfills to reduce the packages' size.
How To Upgrade
Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 8 to version 9.
Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v8-to-v9/
A comprehensive migration guide outlining all changes for all the frameworks can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md
Breaking Changes
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 becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.