-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat(deps): update dependency @sentry/node to v7.31.1 #627
Conversation
Progress☑️ Step 1: ✏️ Write code Options:
Actions:
|
Codecov ReportBase: 65.95% // Head: 65.95% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #627 +/- ##
=======================================
Coverage 65.95% 65.95%
=======================================
Files 18 18
Lines 561 561
Branches 166 166
=======================================
Hits 370 370
Misses 191 191 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
c3ee0e0
to
43e3acd
Compare
43e3acd
to
0d4044c
Compare
3aeb5e6
to
a7003f0
Compare
a7003f0
to
5d1af42
Compare
5d1af42
to
a682212
Compare
a682212
to
b68857a
Compare
b68857a
to
29da692
Compare
29da692
to
f376533
Compare
f376533
to
4f22c51
Compare
4f22c51
to
52b8634
Compare
52b8634
to
300b3ba
Compare
This PR contains the following updates:
7.20.0
->7.31.1
Release Notes
getsentry/sentry-javascript
v7.31.1
Compare Source
v7.31.0
Compare Source
The Next.js SDK now supports error and performance monitoring for Next.js middleware and Edge API routes.
To set it up, add a
sentry.edge.config.js
orsentry.edge.config.ts
file to the root of your project and initialize the SDK:The Next.js will automatically instrument Edge API routes and middleware.
If you want to opt out of automatic instrumentation of middleware can use the
autoInstrumentMiddleware
option in thesentry
object of your Next.js configuration:Middleware can be manually instrumented by using the
wrapMiddlewareWithSentry
function.withSentryConfig
as an alternative to thesentry
property (#6721)checkoutEveryNms
(#6722)isBuild()
andIS_BUILD
(#6727)v7.30.0
Compare Source
addIntegration
method to client (#6651)replay_event
type for events (#6481)LocalVariables
integration to capture local variables to stack frames (#6478)replayType
from tags and intoreplay_event
(#6658)res.json
andres.send
(#6674)res.end
to fixnext export
(#6682)instrumentSever
(#6592)Work in this release contributed by @rjoonas, @Naddiseo, and @theofidry. Thank you for your contributions!
v7.29.0
Compare Source
This update includes a change to the
@sentry/nextjs
SDK that may increase response times of requests in applicationsdeployed to Vercel or AWS lambdas to ensure that error events are sent consistently.
Additionally, Next.js applications deployed to Vercel or AWS lambdas may also see an uptick in sent transactions. (for
more information see #6578)
getSdkMetadata
toClient
(#6643)prepareEvent
util & ensure dropping replays works (#6522)maskAllText
selector (#6637)pageload
transactions early (#6609)v7.28.1
Compare Source
_metadata
in client options (#6600)v7.28.0
Compare Source
index.server.ts
to avoid TS error (#6577)this
through wrappers (#6572)undefined
as possible event type (#6584)v7.27.0
Compare Source
This release exports the Session Replay integration via
@sentry/browser
and all framework SDKs building on top of it.Going forward, the
@sentry/replay
package doesn't have to be installed explicitly to use Replay.Furthermore, this release increases the maximim replay session duration from 30 minutes to 1 hour.
Replay
integration from Browser SDK (#6508)MAX_SESSION_LIFE
to 1 hour (#6561)beforeSend
handling defensive for different event types (#6507)maskAllText
selector more specific (#6544)dsn
in envelope header if tunneling is active (#6568)Work in this release contributed by @theofidry. Thank you for your contribution!
v7.26.0
Compare Source
Work in this release contributed by @theofidry. Thank you for your contribution!
v7.25.0
Compare Source
scope.getLastBreadcrumb()
(#6495)_waitForError
withrecordingMode
(#6489)v7.24.2
Compare Source
reportAllChanges
option (#6456)v7.24.1
Compare Source
This patch corrects an oversight on our end which caused the Sentry Replay integration CDN bundles to be ignored when uploading bundles to our CDN.
If you want to use the Replay CDN bundles, please use version 7.24.1 or newer.
encodeLocation
method (#6439)Work in this release contributed by @theofidry. Thank you for your contribution!
v7.24.0
Compare Source
This release bumps the
@sentry/replay
package from version 0.x to 7.24.0.Along with this version bump, we're introducing a few breaking changes.
Take a look at the Replay migration guide for further information.
The Replay version bump is the result of moving the package into the Sentry JavaScript SDK monorepo which aligns the version with our other JS SDK packages.
Important: If you're using Replay with version 7.24.x or newer, make sure to also upgrade your other
@sentry/*
packages to this version.assetPrefix
option (#6388)basePath
forassetPrefix
if needed (#6424)profilesSampleRate
intoBaseNodeOptions
(#6409)getClientIpAddress
throws error. (#6400)Work in this release contributed by @tomgrossman and @ZachGawlik. Thank you for your contributions!
v7.23.0
Compare Source
__SENTRY_RELEASE__
magic string (#6322)profilesSampleRate
(#6318)sentry_reportAllChanges
tag (#6360)Work in this release contributed by @zhiyan114. Thank you for your contributions!
v7.22.0
Compare Source
event
as third argument torecordDroppedEvent
(#6289)RouteObject
typing. (#6274)normalizeRemixRequest
calls. (#6296)RequestData
. (#6276)v7.21.1
Compare Source
withSentryConfig
from serverless bundles (#6267)v7.21.0
Compare Source
createBrowserRouter
. (#6172)tracePropagationTargets
toinstrumentOutgoingRequests
(#6259)v7.20.1
Compare Source
<unknown>
component name default in TraceDirective (#6222)_sdkProcessingMetadata
when cloning scope (#6218)shouldAttachHeaders
not fall back to default values (#6238)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 has been generated by Mend Renovate. View repository job log here.