fix(deps): update dependency @sentry/node to v8.49.0 [security] - autoclosed#3644
fix(deps): update dependency @sentry/node to v8.49.0 [security] - autoclosed#3644renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #3644 +/- ##
========================================
Coverage 66.41% 66.41%
========================================
Files 930 930
Lines 15398 15398
Branches 2109 2113 +4
========================================
Hits 10226 10226
- Misses 4858 4992 +134
+ Partials 314 180 -134 see 62 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
68c12de to
30c9a73
Compare
30c9a73 to
9508e10
Compare
9508e10 to
efd3c4d
Compare
efd3c4d to
77bf8c4
Compare
77bf8c4 to
4681b94
Compare
4681b94 to
a9aa231
Compare
a9aa231 to
7168e4b
Compare
7168e4b to
d524446
Compare
d524446 to
6066211
Compare
6066211 to
ea34419
Compare
ea34419 to
dcb104f
Compare
dcb104f to
f34148d
Compare
f34148d to
b1f8090
Compare
3281fd4 to
72ffb0b
Compare
72ffb0b to
8b44578
Compare
8b44578 to
6118f8c
Compare
6118f8c to
b8057e5
Compare
b8057e5 to
44d1405
Compare
44d1405 to
a34e21e
Compare
a34e21e to
d0f2f9d
Compare
d0f2f9d to
438f04b
Compare
438f04b to
82913cd
Compare
82913cd to
8aa2166
Compare
8aa2166 to
8f51ba5
Compare
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
|
8f51ba5 to
3bf2a8d
Compare
3bf2a8d to
1211e3c
Compare
|



This PR contains the following updates:
8.22.0->8.49.0GitHub Vulnerability Alerts
GHSA-r5w7-f542-q2j4
Impact
The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events.
The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS).
The ContextLines integration is enabled by default in the Node SDK (
@sentry/node) and SDKs that run in Node.js environments (@sentry/astro,@sentry/aws-serverless,@sentry/bun,@sentry/google-cloud-serverless,@sentry/nestjs,@sentry/nextjs,@sentry/nuxt,@sentry/remix,@sentry/solidstart,@sentry/sveltekit).Patches
Users should upgrade to version
8.49.0or higher.Workarounds
To remediate this issue in affected versions without upgrading to version
8.49.0and above you can disable the ContextLines integration. See the docs for more details.If you disable the ContextLines integration, you will lose source context on your error events.
References
Release Notes
getsentry/sentry-javascript (@sentry/node)
v8.49.0Compare Source
handledprop to ErrorBoundary (#14978)require,__filenameand__dirnameon global object (#14952)Work in this release was contributed by @HHK1 and @mstrokin. Thank you for your contribution!
Bundle size 📦
v8.48.0Compare Source
Deprecations
feat(v8/core): Deprecate
getDomElementmethod (#14799)Deprecates
getDomElement. There is no replacement.Other changes
continueTraceimplementation in core (#14819)NODE_OPTIONSis not passed to worker threads (#14825)tagNamewhen name is not provided toTraceDirective(#14828)openTelemetrySpanProcessorsoption (#14853)Setas theallRoutescontainer. (#14878) (#14884)normalizedRequesttosamplingContext(#14903)syncFeedbackIntegration(#14918)Work in this release was contributed by @arturovt. Thank you for your contribution!
Bundle size 📦
v8.47.0Compare Source
updateSpanNamehelper function (#14736)db.systemin newer Prisma versions (#14772)Work in this release was contributed by @aloisklink and @benjick. Thank you for your contributions!
Bundle size 📦
v8.46.0Compare Source
Work in this release was contributed by @conor-ob. Thank you for your contribution!
Bundle size 📦
v8.45.1Compare Source
sendFeedbackpromise resolves (#14683)Bundle size 📦
v8.45.0Compare Source
handledoption tocaptureConsoleIntegration(#14664)HttpClientevents (#14515)captureMessagewithattachStacktrace: trueas synthetic (#14668)captureMessagewithattatchStackTrace: trueas synthetic (#14670)levelin server runtimecaptureException(#10587)Work in this release was contributed by @anonrig and @Zih0. Thank you for your contributions!
v8.44.0Compare Source
Deprecations
feat: Deprecate
autoSessionTracking(#14640)Deprecates
autoSessionTracking.To enable session tracking, it is recommended to unset
autoSessionTrackingand ensure that either, in browser environmentsthe
browserSessionIntegrationis added, or in server environments thehttpIntegrationis added.To disable session tracking, it is recommended to unset
autoSessionTrackingand to remove thebrowserSessionIntegrationinbrowser environments, or in server environments configure the
httpIntegrationwith thetrackIncomingRequestsAsSessionsoption set tofalse.Other Changes
responsecontext for http.server spans (#14634)Work in this release was contributed by @robinvw1. Thank you for your contribution!
v8.43.0Compare Source
Important Changes
feat(nuxt): Add option autoInjectServerSentry (no default import()) (#14553)
Using the dynamic
import()as the default behavior for initializing the SDK on the server-side did not work for every project.The default behavior of the SDK has been changed, and you now need to use the
--importflag to initialize Sentry on the server-side to leverage full functionality.Example with
--import:In case you are not able to use the
--importflag, you can enable auto-injecting Sentry in thenuxt.config.ts(comes with limitations):feat(browser): Adds LaunchDarkly and OpenFeature integrations (#14207)
Adds browser SDK integrations for tracking feature flag evaluations through the LaunchDarkly JS SDK and OpenFeature Web SDK:
feat(browser): Add
featureFlagsIntegrationfor custom tracking of flag evaluations (#14582)Adds a browser integration to manually track feature flags with an API. Feature flags are attached to subsequent error events:
feat(astro): Add Astro 5 support (#14613)
With this release, the Sentry Astro SDK officially supports Astro 5.
Deprecations
feat(nextjs): Deprecate typedef for
hideSourceMaps(#14594)The functionality of
hideSourceMapswas removed in version 8 but was forgotten to be deprecated and removed.It will be completely removed in the next major version.
feat(core): Deprecate APIs around
RequestSessions (#14566)The APIs around
RequestSessions are mostly used internally.Going forward the SDK will not expose concepts around
RequestSessions.Instead, functionality around server-side Release Health will be managed in integrations.
Other Changes
browserSessionIntegration(#14551)raw_securityenvelope types (#14562)disableAnrDetectionForCallbackfunction (#14359)trackIncomingRequestsAsSessionsoption to http integration (#14567)autoInjectServerSentry(no defaultimport()) (#14553)^1.29.0(#14590)1.28.0(#14547)filenameandmodulestack frame properties in Node stack parser (#14544)maxSpanWaitDurationvalues (#14632)parseSearchoption in TanStack Router instrumentation (#14328)Work in this release was contributed by @lsmurray. Thank you for your contribution!
v8.42.0Compare Source
Important Changes
feat(react): React Router v7 support (library) (#14513)
This release adds support for React Router v7 (library mode).
Check out the docs on how to set up the integration: Sentry React Router v7 Integration Docs
Deprecations
feat: Warn about source-map generation (#14533)
In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application.
Currently, the implementation varies a lot between different SDKs and can be difficult to understand.
Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off.
Additionally, if we end up enabling source maps, we will emit a log message that we did so.
With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.
feat(nuxt): Deprecate
tracingOptionsin favor ofvueIntegration(#14530)Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:
Sentry.init()tracingOptionsinSentry.init()For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported
vueIntegration()and itstracingOptionsoption to configure tracing options in the Nuxt SDK:Other Changes
web-vitalsto v4.2.4 (#14439)vueIntegration(#14526)Bundle size 📦
v8.41.0Compare Source
Important Changes
meta(nuxt): Require minimum Nuxt v3.7.0 (#14473)
We formalized that the Nuxt SDK is at minimum compatible with Nuxt version 3.7.0 and above.
Additionally, the SDK requires the implicit
nitropackdependency to satisfy version^2.10.0andofetchto satisfy^1.4.0.It is recommended to check your lock-files and manually upgrade these dependencies if they don't match the version ranges.
Deprecations
We are deprecating a few APIs which will be removed in the next major.
The following deprecations will potentially affect you:
feat(core): Update & deprecate
undefinedoption handling (#14450)In the next major version we will change how passing
undefinedtotracesSampleRate/tracesSampler/enableTracingwill behave.Currently, doing the following:
Will result in tracing being enabled (although no spans will be generated) because the
tracesSampleRatekey is present in the options object.In the next major version, this behavior will be changed so that passing
undefined(or rather having atracesSampleRatekey) will result in tracing being disabled, the same as not passing the option at all.If you are currently relying on
undefinedbeing passed, and and thus have tracing enabled, it is recommended to update your config to set e.g.tracesSampleRate: 0instead, which will also enable tracing in v9.The same applies to
tracesSamplerandenableTracing.feat(core): Log warnings when returning
nullinbeforeSendSpan(#14433)Currently, the
beforeSendSpanoption inSentry.init()allows you to drop individual spans from a trace by returningnullfrom the hook.Since this API lends itself to creating "gaps" inside traces, we decided to change how this API will work in the next major version.
With the next major version the
beforeSendSpanAPI can only be used to mutate spans, but no longer to drop them.With this release the SDK will warn you if you are using this API to drop spans.
Instead, it is recommended to configure instrumentation (i.e. integrations) directly to control what spans are created.
Additionally, with the next major version, root spans will also be passed to
beforeSendSpan.feat(utils): Deprecate
@sentry/utils(#14431)With the next major version the
@sentry/utilspackage will be merged into the@sentry/corepackage.It is therefore no longer recommended to use the
@sentry/utilspackage.feat(vue): Deprecate configuring Vue tracing options anywhere else other than through the
vueIntegration'stracingOptionsoption (#14385)Currently it is possible to configure tracing options in various places in the Sentry Vue SDK:
Sentry.init()tracingOptionsinSentry.init()vueIntegration()optionstracingOptionsin thevueIntegration()optionsBecause this is a bit messy and confusing to document, the only recommended way to configure tracing options going forward is through the
tracingOptionsin thevueIntegration().The other means of configuration will be removed in the next major version of the SDK.
feat: Deprecate
registerEsmLoaderHooks.includeandregisterEsmLoaderHooks.exclude(#14486)Currently it is possible to define
registerEsmLoaderHooks.includeandregisterEsmLoaderHooks.excludeoptions inSentry.init()to only apply ESM loader hooks to a subset of modules.This API served as an escape hatch in case certain modules are incompatible with ESM loader hooks.
Since this API was introduced, a way was found to only wrap modules that there exists instrumentation for (meaning a vetted list).
To only wrap modules that have instrumentation, it is recommended to instead set
registerEsmLoaderHooks.onlyIncludeInstrumentedModulestotrue.Note that
onlyIncludeInstrumentedModules: truewill become the default behavior in the next major version and theregisterEsmLoaderHookswill no longer accept fine-grained options.The following deprecations will most likely not affect you unless you are building an SDK yourself:
arrayify(#14405)flatten(#14454)urlEncode(#14406)validSeverityLevels(#14407)getNumberOfUrlSegments(#14458)memoBuilder,BAGGAGE_HEADER_NAME, andmakeFifoCache(#14434)addRequestDataToEventandextractRequestData(#14430)Other Changes
sentry-trace,baggageand DSC handling (#14364)openTelemetryInstrumentationsoption (#14484)NEXT_REDIRECTfrom browser (#14440)Work in this release was contributed by @NEKOYASAN and @fmorett. Thank you for your contributions!
Bundle size 📦
v8.40.0Compare Source
Important Changes
feat(angular): Support Angular 19 (#14398)
The
@sentry/angularSDK can now be used with Angular 19. If you're upgrading to the new Angular version, you might want to migrate from the now deprecatedAPP_INITIALIZERtoken toprovideAppInitializer.In this case, change the Sentry
TraceServiceinitialization inapp.config.ts:feat(core): Deprecate
debugIntegrationandsessionTimingIntegration(#14363)The
debugIntegrationwas deprecated and will be removed in the next major version of the SDK.To log outgoing events, use Hook Options (
beforeSend,beforeSendTransaction, ...).The
sessionTimingIntegrationwas deprecated and will be removed in the next major version of the SDK.To capture session durations alongside events, use Context (
Sentry.setContext()).feat(nestjs): Deprecate
@WithSentryin favor of@SentryExceptionCaptured(#14323)The
@WithSentrydecorator was deprecated. Use@SentryExceptionCapturedinstead. This is a simple renaming and functionality stays identical.feat(nestjs): Deprecate
SentryTracingInterceptor,SentryService,SentryGlobalGenericFilter,SentryGlobalGraphQLFilter(#14371)The
SentryTracingInterceptorwas deprecated. If you are using@sentry/nestjsyou can safely remove any references to theSentryTracingInterceptor. If you are using another package migrate to@sentry/nestjsand remove theSentryTracingInterceptorafterwards.The
SentryServicewas deprecated and its functionality was added toSentry.init. If you are using@sentry/nestjsyou can safely remove any references to theSentryService. If you are using another package migrate to@sentry/nestjsConfiguration
📅 Schedule: Branch creation - "" in timezone Europe/Paris, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.