-
Notifications
You must be signed in to change notification settings - Fork 0
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 dependency @sentry/node to v7.41.0 #83
Open
remedyrenovate
wants to merge
1
commit into
dev
Choose a base branch
from
renovate/sentry-javascript-monorepo
base: dev
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 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
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 4, 2023 14:11
ef11a22
to
f09d16b
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.28.1
fix(deps): update dependency @sentry/node to v7.29.0
Jan 4, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 10, 2023 13:28
f09d16b
to
4205f28
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.29.0
fix(deps): update dependency @sentry/node to v7.30.0
Jan 10, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 16, 2023 16:01
4205f28
to
aa22607
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.30.0
fix(deps): update dependency @sentry/node to v7.31.0
Jan 16, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 17, 2023 15:20
aa22607
to
822fcc3
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.31.0
fix(deps): update dependency @sentry/node to v7.31.1
Jan 17, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 23, 2023 10:34
822fcc3
to
ef821b7
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.31.1
fix(deps): update dependency @sentry/node to v7.32.0
Jan 23, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 23, 2023 16:24
ef821b7
to
09952d3
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.32.0
fix(deps): update dependency @sentry/node to v7.32.1
Jan 23, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 24, 2023 16:29
09952d3
to
e6229dc
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.32.1
fix(deps): update dependency @sentry/node to v7.33.0
Jan 24, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
January 27, 2023 03:23
e6229dc
to
360ae29
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.33.0
fix(deps): update dependency @sentry/node to v7.34.0
Jan 27, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 1, 2023 12:30
360ae29
to
eb13a99
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.34.0
fix(deps): update dependency @sentry/node to v7.35.0
Feb 1, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 2, 2023 13:52
eb13a99
to
101687f
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.35.0
fix(deps): update dependency @sentry/node to v7.36.0
Feb 2, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 9, 2023 16:22
101687f
to
326ab78
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.36.0
fix(deps): update dependency @sentry/node to v7.37.0
Feb 9, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 10, 2023 15:51
326ab78
to
9f04aea
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.37.0
fix(deps): update dependency @sentry/node to v7.37.1
Feb 10, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 13, 2023 15:39
9f04aea
to
5b9f717
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.37.1
fix(deps): update dependency @sentry/node to v7.37.2
Feb 13, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 17, 2023 14:16
5b9f717
to
65e92fa
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.37.2
fix(deps): update dependency @sentry/node to v7.38.0
Feb 17, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
February 27, 2023 15:11
65e92fa
to
7ca85ae
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.38.0
fix(deps): update dependency @sentry/node to v7.39.0
Feb 27, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 1, 2023 18:47
7ca85ae
to
20c2b9e
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.39.0
fix(deps): update dependency @sentry/node to v7.40.0
Mar 1, 2023
remedyrenovate
bot
force-pushed
the
renovate/sentry-javascript-monorepo
branch
from
March 6, 2023 12:41
20c2b9e
to
5405f3b
Compare
remedyrenovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7.40.0
fix(deps): update dependency @sentry/node to v7.41.0
Mar 6, 2023
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.14.2
->7.41.0
Release Notes
getsentry/sentry-javascript
v7.41.0
Compare Source
environment
everywhere (#7327)routeLabel: 'path'
to opt-out of using name (#7326)X-Forwarded-For
Http header (#7329)Work in this release contributed by @OliverJAsh. Thank you for your contribution!
v7.40.0
Compare Source
v7.39.0
Compare Source
This release adds a new package,
@sentry/angular-ivy
, which is our Angular SDK with full support for Angular's rendering engine, Ivy.This release also adds a new
enableTracing
option, which can be used instead oftracesSampleRate
for an easier setup.Related to this, the
hasTracingEnabled
utility function was moved from@sentry/tracing
to@sentry/core
.The old export from
@sentry/tracing
has been deprecated and will be removed in v8.debug_meta
(#7168)VERCEL_ENV
as environment (#7227)enableTracing
option (#7238)Replay
rrweb
changes:@sentry-internal/rrweb
was updated from 1.103.0 to 1.104.1 (#7238):typings/types
(#60)autoplay
attribute from audio/video tags (#59)modulepreload
as well (#52)maskAllInputs:false
(#61)rootShadowHost
check (#50)v7.38.0
Compare Source
abs_path
into stack frame object (#7167)Offline
integration (#7063)PerformanceResourceTiming.renderBlockingStatus
(#7127)maxWait
(#7207, #7208)Work in this release contributed by @lucas-zimermann. Thank you for your contribution!
v7.37.2
Compare Source
This release includes changes and fixes around text masking and blocking in Replay's
rrweb
dependency. See versions 1.102.0 and 1.103.0.blockSelector
for blocking elements as wellaria-label
textarea
maskAllText
optionSDK Changes:
v7.37.1
Compare Source
async
in stack frame urls (#7131)this
in http integration (#7135)defaultStackParser
from tracing CDN bundles (#7116)v7.37.0
Compare Source
LocalVariables
, Improve frame matching for ESM (#7049)Work in this release contributed by @JamesHenry. Thank you for your contribution!
v7.36.0
Compare Source
This Release re-introduces the accidentally removed but still deprecated
maskInputOptions
option for Session Replay.Furthermore, replays are now stopped instead of paused when a rate limit is encountered.
maskInputOptions
(#6981)BaseClient
integrations added after init (#7011)v7.35.0
Compare Source
Session Replay is deprecating privacy options in favor of a more streamlined API. Please see the Replay migration guide for further information.
Additionally, the following configuration options will no longer be configurable:
slimDOMOptions
,recordCanvas
,inlineStylesheet
,collectFonts
,inlineImages
.ErrorBoundary
,withErrorBoundary
andshowReportDialog
(#6987)_app
instead ofmain
(#7009)scope.getLastBreadcrumb
if available (#6969)Work in this release contributed by @boblauer. Thank you for your contribution!
v7.34.0
Compare Source
This release adds automatic injection of the Next.js SDK into serverside
app
directory bundles, allowing users to call the Sentry SDK in server components.app
directory (#6927)\
(#6932)Work in this release contributed by @mdtro. Thank you for your contribution!
v7.33.0
Compare Source
With this release, the sample rate for Session Replays will default to 0. We recommend explicitly setting the sample rate via the
replaysSessionSampleRate
andreplaysOnErrorSampleRate
options.v7.32.1
Compare Source
v7.32.0
Compare Source
app
directory browser bundle (#6812)includeLocalVariables
option to enableLocalVariables
integration (#6874)flush
method to integration (#6776)enableLongTask
to option ofBrowserTracing
(#6837)initialFlushDelay
option (#6867)Work in this release contributed by @h3rmanj. Thank you for your contribution!
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)v7.20.0
Compare Source
excludeServerRoutes
config option (#6207)Http
integration (#6191)distDir
in webpack plugin options (#6214)v7.19.0
Compare Source
This release adds a new SDK, @sentry/opentelemetry-node,
which is available as an alpha release to integrate OpenTelemetry performance tracing with Sentry.
Give it a try and let us know if you have any feedback or problems with using it. (#6000)
This release also deprecates the
tracingOrigins
option in favor of usingshouldCreateSpanForRequest
andtracePropagationTargets
.See #6176 for details.
transaction.setContext
method (#6154)instrumenter
on Span & Transaction (#6136)tracingOrigins
(#6176)v7.18.0
Compare Source
This release adds the
beforeSendTransaction
callback to all JS SDKs, letting you make changes to or drop transactions before they're sent to Sentry. This callback works identically tobeforeSend
, just for transactions.beforeSendTransaction
(#6121)OnUncaughtException
integration that allows mimicking native uncaught error exit behaviour (#6137)tracePropagationTargets
option to browser routing instrumentation (#6080)onUncaughtException
integration to remain excluded (#6148)uncaughtException
-handlers are registered (#6138)v7.17.4
Compare Source
getServerRequestHandler
(#6072)v7.17.3
Compare Source
onCLS()
(#6091)v7.17.2
Compare Source
tracingOrigins
not applying (#6079)v7.17.1
Compare Source
This release standardizes our SDKs to use the MIT License, which is our standard license for Sentry SDKs. We were previously using the BSD 3-Clause License in
@sentry/browser
,@sentry/core
,@sentry/gatsby
,@sentry/hub
,@sentry/integrations
,@sentry/node
,@sentry/react
,@sentry/types
,@sentry/typescript
, and@sentry/utils
.This release also updates the behaviour of
tracingOrigins
to no longer affect span creation.tracingOrigins
will only affect ifsentry-trace
andbaggage
headers are attached to outgoing requests. To control span creation, use theshouldCreateSpanForRequest
option.RequestData
integration for server-side requests (#6007)[Symbol.toStringTag]: 'Module'
to CJS files (#6043)tracingOrigins
when creating spans (#6039)WINDOW
from utils (#6024)RequestData
integration default (#5980)RequestData
integration in express handlers (#5990)Work in this release contributed by @philipatkinson, @Rockergmail, @ys-zhifu, and @koenpunt. Thank you for your contributions!
Special shoutout to @Tofandel who helped fix a bug in Jest that was affecting the Sentry JavaScript SDKs!
v7.17.0
Compare Source
Please do not use this version - the release is broken. Upgrade to
7.17.1
instead.v7.16.0
Compare Source
This release adds the
withSentryConfig
feature to the Svelte SDK. It replaces the now deprecated SveltecomponentTrackingPreprocessor
which will be removed in the next major release.@sentry/types
(#5982)withSentryConfig
function to wrap User Svelte Configuration (#5936)src
folder (#5984)withSentryConfig
andNextConfig
(#5967)global.ts
->worldwide.ts
(#5969)constToVarPlugin
(#5970)pageProps
in_app
(#5945)getGlobalObject
as it's no longer used (#5949)Work in this release contributed by @jeengbe. Thank you for your contribution!
v7.15.0
Compare Source
This release deprecates
@sentry/hub
and all of it's exports. All of the@sentry/hub
exports have moved to@sentry/core
.@sentry/hub
will be removed in the next major release.autoInstrumentServerFunctions
per default (#5919)react-router-dom
(#5897)@sentry/hub
code to@sentry/core
(#5823)Work in this release contributed by @outsideris and @JonasKruckenberg. Thank you for your contributions!
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.