-
Notifications
You must be signed in to change notification settings - Fork 113
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
fix(deps): update sentry sdk #604
Merged
Merged
Conversation
This file contains 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
size-limit report 📦
|
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
from
July 31, 2023 17:20
6e72eb9
to
efeaecc
Compare
renovate
bot
changed the title
fix(deps): update sentry sdk to ^7.60.1
fix(deps): update sentry sdk to ^7.61.0
Jul 31, 2023
renovate
bot
changed the title
fix(deps): update sentry sdk to ^7.61.0
fix(deps): update sentry sdk to ^7.61.1
Aug 4, 2023
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
2 times, most recently
from
August 9, 2023 15:34
f8736c3
to
6084a93
Compare
renovate
bot
changed the title
fix(deps): update sentry sdk to ^7.61.1
fix(deps): update sentry sdk to ^7.62.0
Aug 9, 2023
renovate
bot
changed the title
fix(deps): update sentry sdk to ^7.62.0
fix(deps): update sentry sdk to ^7.63.0
Aug 10, 2023
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
2 times, most recently
from
August 11, 2023 12:21
37f2bc2
to
f7988dd
Compare
renovate
bot
changed the title
fix(deps): update sentry sdk to ^7.63.0
fix(deps): update sentry sdk to ^7.63.0 - autoclosed
Aug 11, 2023
renovate
bot
changed the title
fix(deps): update sentry sdk to ^7.63.0 - autoclosed
fix(deps): update sentry sdk to ^7.63.0
Aug 14, 2023
renovate
bot
changed the title
fix(deps): update sentry sdk to ^7.63.0
fix(deps): update sentry sdk to ^7.64.0
Aug 14, 2023
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
from
August 14, 2023 13:05
f7988dd
to
287f5f7
Compare
renovate
bot
changed the title
fix(deps): update sentry sdk to ^7.64.0
fix(deps): update sentry sdk to ^7.65.0
Aug 28, 2023
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
2 times, most recently
from
August 28, 2023 16:32
d3c6495
to
e0f363d
Compare
renovate
bot
changed the title
fix(deps): update sentry sdk to ^7.65.0
fix(deps): update sentry sdk
Aug 28, 2023
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
4 times, most recently
from
September 5, 2023 19:20
dcc24fc
to
6c9be5f
Compare
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
2 times, most recently
from
September 13, 2023 10:03
4df1ee7
to
f4f70d2
Compare
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
2 times, most recently
from
September 25, 2023 16:32
fcebb94
to
546ed94
Compare
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
2 times, most recently
from
October 2, 2023 12:34
c99f0e7
to
bbc4c64
Compare
renovate
bot
force-pushed
the
renovate/sentry-sdk
branch
from
October 5, 2023 10:43
bbc4c64
to
2b38204
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.
This PR contains the following updates:
^7.63.0
->^7.73.0
^7.63.0
->^7.73.0
^7.63.0
->^7.73.0
^1.1.2
->^1.2.1
^7.63.0
->^7.73.0
^7.63.0
->^7.73.0
Release Notes
getsentry/sentry-javascript (@sentry/core)
v7.73.0
Compare Source
Important Changes
This is fully backwards compatible with prior versions of the Replay SDK. The only breaking change that we will making is to not be masking
aria-label
by default. The reason for this change is to align with our core SDK which also does not maskaria-label
. This change also enables better support of searching by clicks.Another change that needs to be highlighted is the 13% bundle size increase. This bundle size increase is necessary to bring improved recording performance and improved replay fidelity, especially in regards to web components and iframes. We will be investigating the reduction of the bundle size in this PR.
Here are benchmarks comparing the version 1 of rrweb to version 2
Other Changes
captureAllExceptions
by default (#9102)tunnel
is considered forisSentryUrl
checks (#9130)RequestAsyncStorage
fallback path (#9126)load
functions (#9071)InboundFilters
integration to useprocessEvent
(#9020)processEvent
(#9019)Work in this release contributed by @vlad-zhukov. Thank you for your contribution!
Bundle size 📦
v7.72.0
Compare Source
Important Changes
This release introduces support for Application Not Responding (ANR) errors for Node.js applications.
These errors are triggered when the Node.js main thread event loop of an application is blocked for more than five seconds.
The Node SDK reports ANR errors as Sentry events and can optionally attach a stacktrace of the blocking code to the ANR event.
To enable ANR detection, import and use the
enableANRDetection
function from the@sentry/node
package before you run the rest of your application code.Any event loop blocking before calling
enableANRDetection
will not be detected by the SDK.Example (ESM):
Example (CJS):
Other Changes
RequestAsyncStorage
locations by locations that webpack will resolve (#9114)replay_id
is not captured when session is expired (#9109)v7.71.0
Compare Source
basename
-prefixed route. (#9076)processEvent
(#9022)Work in this release contributed by @jorrit. Thank you for your contribution!
v7.70.0
Compare Source
Important Changes
This release contains the beta version of
@sentry/bun
, our SDK for the Bun JavaScript runtime! For details on how to use it, please see the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.Note that as of now the Bun runtime does not support global error handlers. This is being actively worked on, see the tracking issue in Bun's GitHub repo.
The Sentry Remix SDK now officially supports Remix v2! See our Remix docs for more details.
Other Changes
processEvent
hook onIntegration
(#9017)React.ComponentType
instead ofReact.FC
aswithSentry
's generic type. (#9043)preprocessEvent
hook (#9034)handleErrorWithSentry
type (#9054)Work in this release contributed by @Dima-Dim, @krist7599555 and @lifeiscontent. Thank you for your contributions!
Special thanks for @isaacharrisholt for helping us implement a Vercel Edge Runtime SDK which we use under the hood for our Next.js SDK.
Bundle size 📦
v7.69.0
Compare Source
Important Changes
This release introduces a new set of top level APIs for the Performance Monitoring SDKs. These aim to simplify creating spans and reduce the boilerplate needed for performance instrumentation. The three new methods introduced are
Sentry.startSpan
,Sentry.startInactiveSpan
, andSentry.startSpanManual
. These methods are available in the browser and node SDKs.Sentry.startSpan
wraps a callback in a span. The span is automatically finished when the callback returns. This is the recommended way to create spans.If you don't want the span to finish when the callback returns, use
Sentry.startSpanManual
to control when the span is finished. This is useful for event emitters or similar.Sentry.startSpan
andSentry.startSpanManual
create a span and make it active for the duration of the callback. Any spans created while this active span is running will be added as a child span to it. If you want to create a span without making it active, useSentry.startInactiveSpan
. This is useful for creating parallel spans that are not related to each other.Other Changes
BeforeFinishCallback
type (#8999)LinkedErrors
integration runs before all event processors (#8956)org
,project
andurl
as args to upload script (#8985)ignoreErrors
(#8986)pg
spans (#8993)useRoutes
(#8998)glob
to Remix SDK dependencies. (#8963)handleRecordingEmit
aborts when event is not added (#8938)Work in this release contributed by @Duncanxyz and @malay44. Thank you for your contributions!
v7.68.0
Compare Source
BroadcastChannel
andSharedWorker
to TryCatch EventTargets (#8943)name
toSpan
(#8949)ServerRuntimeClient
(#8930)span.finish()
works as expected (#8947)v7.67.0
Compare Source
Important Changes
TryCatch
integration as unhandled (#8890)HttpClient
andCaptureConsole
integrations as unhandled (#8891)This release fixes inconsistent behaviour of when our SDKs classify captured errors as unhandled.
Previously, some of our instrumentations correctly set unhandled, while others set handled.
Going forward, all errors caught automatically from our SDKs will be marked as unhandled.
If you manually capture errors (e.g. by calling
Sentry.captureException
), your errors will continue to be reported as handled.This change might lead to a decrease in reported crash-free sessions and consequently in your release health score.
If you have concerns about this, feel free to open an issue.
Other Changes
maxReplayDuration
(#8769)BrowserClientOptions
(#8921)wrap
function (#8927)Work in this release contributed by @SorsOps. Thank you for your contribution!
v7.66.0
Compare Source
package.json
exports (#8895)origin
to spans (#8765)v7.65.0
Compare Source
@sentry/vite-plugin
(#8877)Sentry.startActiveSpan
andSentry.startSpan
(#8803)AsyncLocalStorage
instance (#8831)requestAsyncStorageShim
path resolution on windows (#8875)OnUncaughtException
(#8876)wrapServerLoadWithSentry
(#8801)tracePropagationTargets
inBrowserTracing
(#8874)v7.64.0
Compare Source
getsentry/profiling-node (@sentry/profiling-node)
v1.2.1
Compare Source
Various fixes & improvements
v1.2.0
Compare Source
Various fixes & improvements
v1.1.3
Compare Source
Various fixes & improvements
cc74b6e
) by @JonasBaConfiguration
📅 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 has been generated by Mend Renovate. View repository job log here.