-
Notifications
You must be signed in to change notification settings - Fork 0
fix(deps): update dependency @sentry/node to v8.55.0 #20
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
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/sentry-javascript-monorepo
base: main
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 hidden or 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
dc7136c
to
e729607
Compare
e729607
to
e40c7ce
Compare
e40c7ce
to
17624cb
Compare
c208433
to
6265aa7
Compare
6265aa7
to
41955a3
Compare
41955a3
to
029a10d
Compare
ac06642
to
114d031
Compare
114d031
to
fa50a51
Compare
fa50a51
to
556b112
Compare
262d1a8
to
239de51
Compare
239de51
to
3e0d0bc
Compare
3e0d0bc
to
c23acc8
Compare
c23acc8
to
28021db
Compare
28021db
to
a8530a8
Compare
a8530a8
to
cf69d9e
Compare
cf69d9e
to
68c65b4
Compare
68c65b4
to
f717b53
Compare
f717b53
to
71b5e88
Compare
23138bc
to
fb0f398
Compare
fb0f398
to
6078392
Compare
4a7911d
to
f5497dc
Compare
f5497dc
to
ef4b7a9
Compare
ef4b7a9
to
fb7273b
Compare
fb7273b
to
cfef52e
Compare
cfef52e
to
79ce640
Compare
79ce640
to
1d36a63
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
8.2.1
->8.55.0
Release Notes
getsentry/sentry-javascript (@sentry/node)
v8.55.0
Compare Source
Important Changes
SentryNodeServerlessSDKv8
(#15351)The
SentryNodeServerlessSDK
AWS Lambda Layer will stop receiving updates.If you intend to stay on
v8
and receive updates useSentryNodeServerlessSDKv8
instead.Other Changes
vercelAIIntegration
export (#15339)enabled
to disable Sentry module (#15337) (#15381)registerEsmLoaderHooks
(#15352)beforeUpdate
call (#15262)Work in this release was contributed by @aryanvdesh. Thank you for your contribution!
Bundle size 📦
v8.54.0
Compare Source
Work in this release was contributed by @nwalters512. Thank you for your contribution!
v8.53.0
Compare Source
url
toSourcemapsUploadOptions
(#15202)fromLocation
can be undefined in Tanstack Router Instrumentation (#15237)Work in this release was contributed by @tannerlinsley. Thank you for your contribution!
v8.52.1
Compare Source
this.name
tonew.target.prototype.constructor.name
(#15222)Work in this release was contributed by @Zen-cronic. Thank you for your contribution!
v8.52.0
Compare Source
Important Changes
withSentry
wrapper for SolidStart config (#15135)To enable the SolidStart SDK, wrap your SolidStart Config with
withSentry
. ThesentrySolidStartVite
plugin is now automaticallyadded by
withSentry
and you can pass the Sentry build-time options like this:With the
withSentry
wrapper, the Sentry server config should not be added to thepublic
directory anymore.Add the Sentry server config in
src/instrument.server.ts
. Then, the server config will be placed inside the server build output asinstrument.server.mjs
.Now, there are two options to set up the SDK:
--import
CLI flag to the start command like this (path depends on your server setup):node --import ./.output/server/instrument.server.mjs .output/server/index.mjs
autoInjectServerSentry: 'top-level-import'
and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)Other Changes
Bun.serve
survives a server reload (#15157)module
intoloadModule
(#15139) (#15166)Work in this release was contributed by @jahands, @jrandolf, and @nathankleyn. Thank you for your contributions!
v8.51.0
Compare Source
Important Changes
feat(v8/node): Add
prismaInstrumentation
option to Prisma integration as escape hatch for all Prisma versions (#15128)This release adds a compatibility API to add support for Prisma version 6.
To capture performance data for Prisma version 6:
Install the
@prisma/instrumentation
package on version 6.Pass a
new PrismaInstrumentation()
instance as exported from@prisma/instrumentation
to theprismaInstrumentation
option:The passed instrumentation instance will override the default instrumentation instance the integration would use, while the
prismaIntegration
will still ensure data compatibility for the various Prisma versions.Remove the
previewFeatures = ["tracing"]
option from the client generator block of your Prisma schema.Other Changes
multiplexedtransport.js
CDN bundle (#15046)fetchProxyScriptNonce
option (#15011)fatal
events should set session as crashed (#15073)Work in this release was contributed by @tjhiggins, and @nwalters512. Thank you for your contributions!
v8.50.0
Compare Source
createMemoryRouter
(#14985)v8.49.0
Compare Source
handled
prop to ErrorBoundary (#14978)require
,__filename
and__dirname
on global object (#14952)Work in this release was contributed by @HHK1 and @mstrokin. Thank you for your contributions!
v8.48.0
Compare Source
Deprecations
feat(v8/core): Deprecate
getDomElement
method (#14799)Deprecates
getDomElement
. There is no replacement.Other changes
continueTrace
implementation in core (#14819)NODE_OPTIONS
is not passed to worker threads (#14825)tagName
when name is not provided toTraceDirective
(#14828)openTelemetrySpanProcessors
option (#14853)Set
as theallRoutes
container. (#14878) (#14884)normalizedRequest
tosamplingContext
(#14903)syncFeedbackIntegration
(#14918)Work in this release was contributed by @arturovt. Thank you for your contribution!
v8.47.0
Compare Source
updateSpanName
helper function (#14736)db.system
in newer Prisma versions (#14772)Work in this release was contributed by @aloisklink and @benjick. Thank you for your contributions!
v8.46.0
Compare Source
Work in this release was contributed by @conor-ob. Thank you for your contribution!
v8.45.1
Compare Source
sendFeedback
promise resolves (#14683)Work in this release was contributed by @antonis. Thank you for your contribution!
v8.45.0
Compare Source
handled
option tocaptureConsoleIntegration
(#14664)HttpClient
events (#14515)captureMessage
withattachStacktrace: true
as synthetic (#14668)captureMessage
withattatchStackTrace: true
as synthetic (#14670)level
in server runtimecaptureException
(#10587)Work in this release was contributed by @anonrig and @Zih0. Thank you for your contributions!
v8.44.0
Compare Source
Deprecations
feat: Deprecate
autoSessionTracking
(#14640)Deprecates
autoSessionTracking
.To enable session tracking, it is recommended to unset
autoSessionTracking
and ensure that either, in browser environmentsthe
browserSessionIntegration
is added, or in server environments thehttpIntegration
is added.To disable session tracking, it is recommended to unset
autoSessionTracking
and to remove thebrowserSessionIntegration
inbrowser environments, or in server environments configure the
httpIntegration
with thetrackIncomingRequestsAsSessions
option set tofalse
.Other Changes
response
context for http.server spans (#14634)Work in this release was contributed by @robinvw1. Thank you for your contribution!
v8.43.0
Compare 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
--import
flag to initialize Sentry on the server-side to leverage full functionality.Example with
--import
:In case you are not able to use the
--import
flag, 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
featureFlagsIntegration
for 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
hideSourceMaps
was 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
RequestSession
s (#14566)The APIs around
RequestSession
s are mostly used internally.Going forward the SDK will not expose concepts around
RequestSession
s.Instead, functionality around server-side Release Health will be managed in integrations.
Other Changes
browserSessionIntegration
(#14551)raw_security
envelope types (#14562)disableAnrDetectionForCallback
function (#14359)trackIncomingRequestsAsSessions
option to http integration (#14567)autoInjectServerSentry
(no defaultimport()
) (#14553)^1.29.0
(#14590)1.28.0
(#14547)filename
andmodule
stack frame properties in Node stack parser (#14544)maxSpanWaitDuration
values (#14632)parseSearch
option in TanStack Router instrumentation (#14328)Work in this release was contributed by @lsmurray. Thank you for your contribution!
v8.42.0
Compare 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
tracingOptions
in favor ofvueIntegration
(#14530)Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:
Sentry.init()
tracingOptions
inSentry.init()
For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported
vueIntegration()
and itstracingOptions
option to configure tracing options in the Nuxt SDK:Other Changes
web-vitals
to v4.2.4 (#14439)vueIntegration
(#14526)v8.41.0
Compare 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
nitropack
dependency to satisfy version^2.10.0
andofetch
to 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
undefined
option handling (#14450)In the next major version we will change how passing
undefined
totracesSampleRate
/tracesSampler
/enableTracing
will behave.Currently, doing the following:
Will result in tracing being enabled (although no spans will be generated) because the
tracesSampleRate
key is present in the options object.In the next major version, this behavior will be changed so that passing
undefined
(or rather having atracesSampleRate
key) will result in tracing being disabled, the same as not passing the option at all.If you are currently relying on
undefined
being passed, and and thus have tracing enabled, it is recommended to update your config to set e.g.tracesSampleRate: 0
instead, which will also enable tracing in v9.The same applies to
tracesSampler
andenableTracing
.feat(core): Log warnings when returning
null
inbeforeSendSpan
(#14433)Currently, the
beforeSendSpan
option inSentry.init()
allows you to drop individual spans from a trace by returningnull
from 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
beforeSendSpan
API 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/utils
package will be merged into the@sentry/core
package.It is therefore no longer recommended to use the
@sentry/utils
package.feat(vue): Deprecate configuring Vue tracing options anywhere else other than through the
vueIntegration
'stracingOptions
option (#14385)Currently it is possible to configure tracing options in various places in the Sentry Vue SDK:
Sentry.init()
tracingOptions
inSentry.init()
vueIntegration()
optionstracingOptions
in thevueIntegration()
optionsBecause this is a bit messy and confusing to document, the only recommended way to configure tracing options going forward is through the
tracingOptions
in thevueIntegration()
.The other means of configuration will be removed in the next major version of the SDK.
feat: Deprecate
registerEsmLoaderHooks.include
andregisterEsmLoaderHooks.exclude
(#14486)Currently it is possible to define
registerEsmLoaderHooks.include
andregisterEsmLoaderHooks.exclude
options 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.onlyIncludeInstrumentedModules
totrue
.Note that
onlyIncludeInstrumentedModules: true
will become the default behavior in the next major version and theregisterEsmLoaderHooks
will 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)addRequestDataToEvent
andextractRequestData
(#14430)Other Changes
sentry-trace
,baggage
and DSC handling (#14364)openTelemetryInstrumentations
option (#14484)NEXT_REDIRECT
from browser (#14440)Work in this release was contributed by @NEKOYASAN and @fmorett. Thank you for your contributions!
v8.40.0
Compare Source
Important Changes
feat(angular): Support Angular 19 (#14398)
The
@sentry/angular
SDK 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_INITIALIZER
token toprovideAppInitializer
.In this case, change the Sentry
TraceService
initialization inapp.config.ts
:feat(core): Deprecate
debugIntegration
andsessionTimingIntegration
(#14363)The
debugIntegration
was deprecated and will be removed in the next major version of the SDK.To log outgoing events, use Hook Options (
beforeSend
,beforeSendTransaction
, ...).The
sessionTimingIntegration
was 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
@WithSentry
in favor of@SentryExceptionCaptured
(#14323)The
@WithSentry
decorator was deprecated. Use@SentryExceptionCaptured
instead. This is a simple renaming and functionality stays identical.feat(nestjs): Deprecate
SentryTracingInterceptor
,SentryService
,SentryGlobalGenericFilter
,SentryGlobalGraphQLFilter
(#14371)The
SentryTracingInterceptor
was deprecated. If you are using@sentry/nestjs
you can safely remove any references to theSentryTracingInterceptor
. If you are using another package migrate to@sentry/nestjs
and remove theSentryTracingInterceptor
afterwards.The
SentryService
was deprecated and its functionality was added toSentry.init
. If you are using@sentry/nestjs
you can safely remove any references to theSentryService
. If you are using another package migrate to@sentry/nestjs
and remove theSentryService
afterwards.The
SentryGlobalGenericFilter
was deprecated. Use theSentryGlobalFilter
instead which is a drop-in replacement.The
SentryGlobalGraphQLFilter
was deprecated. Use theSentryGlobalFilter
instead which is a drop-in replacement.feat(node): Deprecate
nestIntegration
andsetupNestErrorHandler
in favor of using@sentry/nestjs
(#14374)The
nestIntegration
andsetupNestErrorHandler
functions from@sentry/node
were deprecated and will be removed in the next major version of the SDK. If you're using@sentry/node
in a NestJS application, we recommend switching to our new dedicated@sentry/nestjs
package.Other Changes
normalizedRequest
onsdkProcessingMetadata
is merged (#14315)@sentry/utils
into@sentry/core
(#14382)__self
and__source
attributes on feedback nodes (#14356)v8.39.0
Compare Source
Important Changes
The
@sentry/nestjs
SDK will now capture performance data for NestJS Events (@nestjs/event-emitter
)Other Changes
@SentryExceptionCaptured
for@WithSentry
(#14322)SentryService
behaviour into@sentry/nestjs
SDKinit()
(#14321)SentryGlobalFilter
(#14320)childProcessIntegration
forprocessThreadBreadcrumbIntegration
and deprecate it (#14334)_sentryModuleMetadata
is not mangled (#14344)sentry.source
attribute tocustom
when callingspan.updateName
onSentrySpan
(#14251)Request
type in favor ofRequestEventData
(#14317)transaction
inrequestDataIntegration
(#14306)v8.38.0
Compare Source
knex
integration (#13526)tedious
integration (#13486)debug_meta
with ANR events (#14203)Work in this release was contributed by @grahamhency, @Zen-cronic, @gilisho and @phuctm97. Thank you for your contributions!
v8.37.1
Compare Source
v8.37.0
Compare Source
Important Changes
piniaIntegration
(#14138)The Nuxt SDK now allows you to track Pinia state for captured errors. To enable the Pinia plugin, add the
piniaIntegration
to your client config:The Sentry Metrics beta has ended in favour of revisiting metrics in another form at a later date.
This new approach will include different APIs, making the current metrics API unnecessary. This release
deprecates the metrics API with the plan to remove in the next SDK major version. If you currently use the
metrics API in your code, you can safely continue to do so but sent data will no longer be processed by Sentry.
Learn more about the end of the Metrics beta.
Other Changes
http.response_delivery_type
attribute to resource spans (#14056)skipBrowserExtensionCheck
escape hatch option (#14147)asyncFunctionReExports
to define re-exported server functions (#14104)piniaIntegration
(#14138)maybeInstrument
(#14140)modulesIntegration
does not crash esm apps (#14169)Work in this release was contributed by @rexxars. Thank you for your contribution!
v8.36.0
Compare Source
Important Changes
With this release, the Sentry Next.js, and Cloudflare SDKs will now capture performance data based on OpenTelemetry.
Some exceptions apply in cases where Next.js captures inaccurate data itself.
NOTE: You may experience minor differences in transaction names in Sentry.
Most importantly transactions for serverside pages router invocations will now be named
GET /[param]/my/route
instead of/[param]/my/route
.This means that those transactions are now better aligned with the OpenTelemetry semantic conventions.
Other Changes
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 was generated by Mend Renovate. View the repository job log.