fix(deps): update sentry-javascript monorepo to v7.101.1 #58
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.81.1
->7.101.1
7.81.1
->7.101.1
Release Notes
getsentry/sentry-javascript (@sentry/integrations)
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)Bundle size 📦
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.
Bundle size 📦
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!
Bundle size 📦
v7.98.0
Compare Source
This release primarily fixes some type declaration errors:
IntegrationIndex
type (#10337)Bundle size 📦
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)Bundle size 📦
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!
Bundle size 📦
v7.94.1
Compare Source
This release fixes a publishing issue.
Bundle size 📦
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 jobs with 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!
Bundle size 📦
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 introduced APIs, 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 yourSentry.init
call.Other Changes
getGlobalScope()
method (#9920)getIsolationScope()
method (#9957)span.end()
to replacespan.finish()
(#9954)startSpan
&startSpanManual
fork scope (#9955)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.