chore(deps): update JavaScript SDK to v7.93.0 #529
Closed
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.
Bumps scripts/update-javascript.sh from 7.81.1 to 7.93.0.
Auto-generated by a dependency updater.
Changelog
7.93.0
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)7.92.0
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!
7.91.0
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)7.90.0
types
field to package.jsonexports
(#9926)7.89.0
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!
7.88.0
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)7.87.0
getCurrentScope()
method (#9800)rrweb
to 2.5.0 (#9803)./exports
(#9775)assetPrefix
is defined (#9766)7.86.0
process.env.NODE_ENV
access in Spotlight integration (#9748)7.85.0
addEventProcessor
method (#9554)box-shadow
to use CSS var (#9630)7.84.0
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)7.83.0
assets
option to source maps upload options (#9668)exactOptionalPropertyTypes
onErrorBoundary
(#9098)types
(#9682)7.82.0
setup
hook to integrations (#9556)getClient()
method (#9638)mechanism
as event hint (#9590)continueTrace
without callback (#9615)addInstrumentationHandler
to dedicated methods (#9542)BODY_PARSE_ERROR
warning & time out fetch response load (#9622)RequestData
integration tosentry/core
(#9597)Work in this release contributed by arya-s. Thank you for your contribution!