fix(deps): update dependency @sentry/node to v7.110.1 #30
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/sentry-javascript-monorepo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
7.83.0
->7.110.1
Release Notes
getsentry/sentry-javascript (@sentry/node)
v7.110.1
Compare Source
tunnelRoute
matching logic for hybrid cloud (#11577)Bundle size 📦
v7.110.0
Compare Source
Important Changes
You can now use a
interactionsSampleRate
to control the sample rate of INP spans.interactionsSampleRate
is appliedon top of the global
tracesSampleRate
. Therefore ifinteractionsSampleRate
is0.5
andtracesSampleRate
is0.1
,then the actual sample rate for interactions is
0.05
.This release deprecates the
Hub
class, as well as theaddRequestDataToTransaction
method. ThetrpcMiddleware
method is no longer on the
Handlers
export, but instead is a standalone export.Please see the detailed Migration docs on how to migrate to the new APIs.
trpcMiddleware
(#11389)Hub
class (#11528)Hub
interface (#11530)addRequestDataToTransaction
(#11368)Other Changes
OPTIONS
andHEAD
request. (#11485)statsd
tometric_bucket
(#11505)Bundle size 📦
v7.109.0
Compare Source
This release deprecates some exports from the
@sentry/replay
package. These exports have been moved to the browser SDK(or related framework SDKs like
@sentry/react
).rrweb
to 2.12.0 (#11317)@sentry/replay
exports (#11242)Work in this release contributed by @soerface. Thank you for your contribution!
Bundle size 📦
v7.108.0
Compare Source
This release fixes issues with Time to First Byte (TTFB) calculation in the SDK that was introduced with
7.95.0
. Italso fixes some bugs with Interaction to First Paint (INP) instrumentation. This may impact your Sentry Performance
Score calculation.
ResizeObserver
andgoogletag
default filters (#11210)cron
(#11225)sampled
type onTransaction
(#11146)Work in this release contributed by @quisido and @joshkel. Thank you for your contributions!
v7.107.0
Compare Source
This release fixes issues with INP instrumentation with the Next.js SDK and adds support for the
enableInp
option inthe deprecated
BrowserTracing
integration for backwards compatibility.handled
value in ErrorBoundary depending on fallback [v7] (#11037)v7.106.1
Compare Source
createReduxEnhancer
on server (#11010)v7.106.0
Compare Source
tunnelRoute
option (#10958)setTransactionName
global
(#10925)AttachmentType
and use for envelopeattachment_type
property (#10946)Work in this release contributed by @jessezhang91 and @bfontaine. Thank you for your contributions!
v7.105.0
Compare Source
Important Changes
withActiveSpan
is exported everywhere (#10877)You can use the
withActiveSpan
method to ensure a certain span is the active span in a given callback. This can beused to create a span as a child of a specific span with the
startSpan
API methods:v7.104.0
Compare Source
Important Changes
This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support
is released with the upcoming
24.3.0
release of self-hosted.To opt-in to this feature, you can use the
enableInp
option in thebrowserTracingIntegration
:Other Changes
nodeProfilingIntegration
(#10864)errorHandler
for replayCanvas integration (#10796)v7.103.0
Compare Source
Important Changes
forceTransaction
tostartSpan()
APIs (#10819)You can now pass
forceTransaction: true
tostartSpan()
,startSpanManual()
andstartInactiveSpan()
. This allowsyou to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to
the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if
possible, ensuring it shows up as a transaction throughout the system.
Please note that setting this to
true
does not guarantee that this will be sent as a transaction, but that the SDKwill try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it
in the Sentry UI.
Other Changes
v7.102.1
Compare Source
window.location
(#10659)@remix-run/router
a dependency (v7) (#10779)v7.102.0
Compare Source
captureContext
function (#10737)v7.101.1
Compare Source
In version 7.101.0 the
@sentry/hub
package was missing due to a publishing issue. This release contains the packageagain.
webpack://
prefix more broadly from source mapsources
field (#10641)v7.101.0
Compare Source
Hub
constructor (#10584)getReplay
utility function (#10510)exports
field topackage.json
(#10569)v7.100.1
Compare Source
This release contains build fixes for profiling-node.
v7.100.0
Compare Source
Important Changes
Deprecations
This release includes some deprecations. For more details please look at our
migration guide.
The deprecation most likely to affect you is the one of
BrowserTracing
. Instead ofnew BrowserTracing()
, you shouldnow use
browserTracingIntegration()
, which will also handle framework-specific instrumentation out of the box foryou - no need to pass a custom
routingInstrumentation
anymore. For@sentry/react
, we expose dedicated integrationsfor the different react-router versions:
reactRouterV6BrowserTracingIntegration()
reactRouterV5BrowserTracingIntegration()
reactRouterV4BrowserTracingIntegration()
reactRouterV3BrowserTracingIntegration()
See the
migration guide
for details.
browserTracingIntegration()
(#10353)BrowserTracing
integration (#10493)browserProfilingIntegration
(#10438)bunServerIntegration()
(#10439)browserTracingIntegration
(#10397)reactRouterV3BrowserTracingIntegration
for react router v3 (#10489)reactRouterV4/V5BrowserTracingIntegration
for react router v4 & v5 (#10488)reactRouterV6BrowserTracingIntegration
for react router v6 & v6.4 (#10491)browserTracingIntegration
(#10442)WinterCGFetch
withwinterCGFetchIntegration
(#10436)continueTrace
(#10301)new VueIntegration()
(#10440)browserTracingIntegration()
(#10477)browserTracingIntegration()
(#10450)Profiling Node
@sentry/profiling-node
has been ported into the monorepo. Future development for it will happen here!Other Changes
setHttpStatus
from all packages (#10475)Sentry
namespace (#10452)name
&attributes
totracesSampler
(#10426)system-ui
to start of font family (#10464)rrweb
to 2.10.0 (#10445)propagationContextFromHeaders
(#10313)startSpan
,startSpanManual
andstartInactiveSpan
pick up the scopes at time of creation instead oftermination (#10492)
require
call to import Undici (#10388)v7.99.0
Compare Source
Important Changes
Deprecations
This release includes some deprecations for span related methods and integrations in our Deno SDK,
@sentry/deno
. Formore details please look at our
migration guide.
Span.setHttpStatus
in favor ofsetHttpStatus
(#10268)spanStatusfromHttpCode
in favour ofgetSpanStatusFromHttpCode
(#10361)StartSpanOptions.origin
in favour of passing attribute (#10274)Other Changes
@sentry/node
re-exports (#10396)afterAllSetup
hook for integrations (#10345)startSpan()
can handle spans that require parent (#10386)startSpan
APIs (#10300)@sentry/node
functions (#10385, #10391)@sentry/node
re-exports (#10390)@sentry/node
re-exports (#10392)browserTracingIntegration
(#10351)afterAllSetup
is called when usingaddIntegration()
(#10372)spanToTraceContext
function from span utils (#10364)FunctionToString
integration use SETUP_CLIENTS weakmap (#10358)Work in this release contributed by @AleshaOleg. Thank you for your contribution!
v7.98.0
Compare Source
This release primarily fixes some type declaration errors:
IntegrationIndex
type (#10337)v7.97.0
Compare Source
Note: The 7.96.0 release was incomplete. This release is partially encompassing changes from
7.96.0
.stripBasename
option for React Router 6 (#10314)v7.96.0
Compare Source
Note: This release was incomplete. Not all Sentry SDK packages were released for this version. Please upgrade to 7.98.0
directly.
Important Changes
Deprecations
This release includes some deprecations for integrations in
@sentry/browser
and frontend framework SDKs(
@sentry/react
,@sentry/vue
, etc.). Please take a look at ourmigration guide for more details.
Web Vitals Fix for LCP and CLS
This release fixes an issue with the Web Vitals integration where LCP and CLS were not being captured correctly,
increasing capture rate by 10-30% for some apps. LCP and CLS capturing issues were introduced with version
7.75.0
.Other Changes
node-cron
types and add test (#10315)Work in this release contributed by @Shubhdeep12. Thank you for your contribution!
v7.95.0
Compare Source
Important Changes
Deprecations
This release includes some deprecations in preparation for v8.
Most notably, it deprecates the
Replay
&Feedback
classes in favor of a functional replacement:Span.origin
in favor ofsentry.origin
attribute (#10260)Span.parentSpanId
(#10244)isInitialized()
to replace checking viagetClient
(#10296)Replay
,ReplayCanvas
,Feedback
classes (#10270)Wasm
integration class (#10230)Other Changes
parameterize
function available through browser and node API (#10085)addOrUpdateIntegration
(#10263)Work in this release contributed by @AleshaOleg. Thank you for your contribution!
v7.94.1
Compare Source
This release fixes a publishing issue.
v7.93.0
Compare Source
Important Changes
Deprecations
As we're moving closer to the next major version of the SDK, more public APIs were deprecated.
To get a head start on migrating to the replacement APIs, please take a look at our
migration guide.
getActiveTransaction()
&scope.getTransaction()
(#10098)Hub.shouldSendDefaultPii
(#10062)new Transaction()
(#10125)scope.getSpan()
&scope.setSpan()
(#10114)scope.setTransactionName()
(#10113)span.startChild()
(#10091)startTransaction()
(#10073)Transaction.getDynamicSamplingContext
in favor ofgetDynamicSamplingContextFromSpan
(#10094)startSpan()
(#10101)Scope
(#10039)name
anddescription
(#10056)tags
,data
,context
& setters (#10053)span.sampled
in favor ofspan.isRecording()
(#10034)lastEventId
on scope (#10093)Cron Monitoring Support for
node-schedule
libraryThis release adds auto instrumented check-ins for the
node-schedule
library.node-schedule
library (#10086)Other Changes
span.spanContext()
(#10037)spanToJSON()
method to get span properties (#10074)scope
tostartSpan
APIs (#10076)getModuleFromFilename
compatible with ESM (#10061)parameterize
function (#9145)setup
for integration on client multiple times (#10116)LocalVariables
integration should have correct name (#10084)event_id
(#10068)LocalVariables
(#10077)v7.92.0
Compare Source
Important Changes
Deprecations
span.updateName()
and deprecatespan.setName()
(#10018)span.getTraceContext()
(#10032)span.toTraceparent()
in favor ofspanToTraceHeader()
util (#10031)trace
in favor ofstartSpan
(#10012)toContext()
andupdateWithContext()
(#10030)deepReadDirSync
(#10016)lastEventId()
(#10043)Please take a look at the Migration docs for more details. These methods will be removed in the
upcoming v8 major release.
Cron Monitoring Support for
cron
andnode-cron
librariescron
library (#9999)node-cron
library (#9904)This release adds instrumentation for the
cron
andnode-cron
libraries. This allows you to monitor your cron jobswith Sentry cron monitors.
For
cron
:For
node-cron
:Other Changes
enabled
option to Astro integration options (#10007)attributes
toSpan
(#10008)setClient()
andgetClient()
toScope
(#10055)captureErrorCause
inExtraErrorData
integration (#9914)withScope
sets current scope correctly with async callbacks (#9974)NODE_VERSION
properties required (#9964)Work in this release contributed by @joshkel. Thank you for your contribution!
v7.91.0
Compare Source
Important Changes
The release adds alpha support for Sentry developer metrics in
the server runtime SDKs (
@sentry/node
,@sentry/deno
,@sentry/nextjs
server-side, etc.). Via the newly introducedAPIs, you can now flush metrics directly to Sentry.
To enable capturing metrics, you first need to add the
metricsAggregator
experiment to yourSentry.init
call.Then you'll be able to add
counters
,sets
,distributions
, andgauges
under theSentry.metrics
namespace.The ANR tracking integration for Node
has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously
you had to call
Sentry.enableANRDetection
before running your application, now you can simply add theAnr
integration to your
Sentry.init
call.Other Changes
getGlobalScope()
method (#9920)getIsolationScope()
method (#9957)span.end()
to replacespan.finish()
(#9954)startSpan
&startSpanManual
fork scope (#9955)startSpan
,startSpanManual
,trace
(#9958)v7.90.0
Compare Source
types
field to package.jsonexports
(#9926)v7.89.0
Compare Source
Important Changes
Deprecations
configureScope
(#9887)pushScope
&popScope
(#9890)This release deprecates
configureScope
,pushScope
, andpopScope
, which will be removed in the upcoming v8 majorrelease.
Hapi Integration
This release adds an integration for Hapi. It can be used as follows:
SvelteKit 2.0
This release adds support for SvelteKit 2.0 in the
@sentry/sveltekit
package. If you're upgrading from SvelteKit 1.xto 2.x and already use the Sentry SvelteKit SDK, no changes apart from upgrading to this (or a newer) version are
necessary.
Other Changes
withScope
to return callback return value (#9866)Deno.CronSchedule
for cron jobs (#9880)canvas.type
setting (#9877)createReduxEnhancer
(#9854)Event
type in worldwide (#9864)eventFromUnknownInput
to avoid scope pollution &getCurrentHub
(#9868)addBreadcrumb
directly & allow to pass hint (#9867)Work in this release contributed by @adam187, and @jghinestrosa. Thank you for your contributions!
v7.88.0
Compare Source
Important Changes
The release adds alpha support for Sentry developer metrics in
the Browser SDKs (
@sentry/browser
and related framework SDKs). Via the newly introduced APIs, you can now flushmetrics directly to Sentry.
To enable capturing metrics, you first need to add the
MetricsAggregator
integration.Then you'll be able to add
counters
,sets
,distributions
, andgauges
under theSentry.metrics
namespace.In a future release we'll add support for server runtimes (Node, Deno, Bun, Vercel Edge, etc.)
Deno.cron
(#9808)This releases add support for instrumenting Deno cron's with
Sentry cron monitors. This requires v1.38 of Deno run with the
--unstable
flag and the usage of the
DenoCron
Sentry integration.Other Changes
rrweb
to 2.6.0 (#9847)v7.87.0
Compare Source
getCurrentScope()
method (#9800)rrweb
to 2.5.0 (#9803)./exports
(#9775)assetPrefix
is defined (#9766)v7.86.0
Compare Source
process.env.NODE_ENV
access in Spotlight integration (#9748)v7.85.0
Compare Source
addEventProcessor
method (#9554)box-shadow
to use CSS var (#9630)v7.84.0
Compare Source
Important Changes
automaticVercelMonitors
to befalse
by default (#9697)From this version onwards the default for the
automaticVercelMonitors
option in the Next.js SDK is set to false.Previously, if you made use of Vercel Crons the SDK automatically instrumented the relevant routes to create Sentry
monitors. Because this feature will soon be generally available, we are now flipping the default to avoid situations
where quota is used unexpectedly.
If you want to continue using this feature, make sure to set the
automaticVercelMonitors
flag totrue
in yournext.config.js
Sentry settings.Other Changes
astro
peer dependency range (#9696)middleware
in node_modules (#9686)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.
This PR has been generated by Renovate Bot.
24c55e974b
to0c87667d4f
fix(deps): update dependency @sentry/node to v7.84.0to fix(deps): update dependency @sentry/node to v7.85.00c87667d4f
to0f8735379e
fix(deps): update dependency @sentry/node to v7.85.0to fix(deps): update dependency @sentry/node to v7.91.00f8735379e
to25e04e4220
fix(deps): update dependency @sentry/node to v7.91.0to fix(deps): update dependency @sentry/node to v7.92.025e04e4220
to950c21e415
fix(deps): update dependency @sentry/node to v7.92.0to fix(deps): update dependency @sentry/node to v7.93.0950c21e415
to551a9078e8
551a9078e8
to4646e291cb
fix(deps): update dependency @sentry/node to v7.93.0to fix(deps): update dependency @sentry/node to v7.94.14646e291cb
to8d782661e4
fix(deps): update dependency @sentry/node to v7.94.1to fix(deps): update dependency @sentry/node to v7.99.08d782661e4
to3009bd1110
fix(deps): update dependency @sentry/node to v7.99.0to fix(deps): update dependency @sentry/node to v7.100.13009bd1110
to4e660fb0c7
fix(deps): update dependency @sentry/node to v7.100.1to fix(deps): update dependency @sentry/node to v7.101.04e660fb0c7
toc71af96df3
fix(deps): update dependency @sentry/node to v7.101.0to fix(deps): update dependency @sentry/node to v7.101.1c71af96df3
tocf7c114732
fix(deps): update dependency @sentry/node to v7.101.1to fix(deps): update dependency @sentry/node to v7.105.0cf7c114732
to85efb05316
85efb05316
tof90466e517
fix(deps): update dependency @sentry/node to v7.105.0to fix(deps): update dependency @sentry/node to v7.108.0f90466e517
to35a8e27cc0
fix(deps): update dependency @sentry/node to v7.108.0to fix(deps): update dependency @sentry/node to v7.109.035a8e27cc0
to0d8fbe146c
fix(deps): update dependency @sentry/node to v7.109.0to fix(deps): update dependency @sentry/node to v7.110.10d8fbe146c
tob9801ff046
b9801ff046
to62b03c7f6c
62b03c7f6c
to4d72211956
4d72211956
toc7b6daa78d
Checkout
From your project repository, check out a new branch and test the changes.