-
Notifications
You must be signed in to change notification settings - Fork 4
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
chore(deps): update dependency @sentry/node to v8 #44
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-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 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
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
May 28, 2024 02:17
9438e66
to
7bf8ccc
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
May 31, 2024 14:54
7bf8ccc
to
328baf5
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
June 12, 2024 11:48
dfe9754
to
544f767
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
June 26, 2024 20:27
5a5e80a
to
7b5653c
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
July 5, 2024 02:28
51f39da
to
a1236e3
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
July 11, 2024 05:48
a87fb41
to
14eb33e
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
July 26, 2024 02:41
5857b0b
to
88153b9
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
August 6, 2024 23:48
e06ce69
to
49ad210
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
August 15, 2024 05:52
cd14a08
to
dfbca53
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
August 28, 2024 02:23
dfbca53
to
a45af83
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
3 times, most recently
from
September 10, 2024 20:50
535907f
to
2604ff4
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
September 25, 2024 18:00
327e1e5
to
134d6b5
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 3, 2024 02:21
134d6b5
to
b393a29
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 4, 2024 04:58
b393a29
to
ef1bc52
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 11, 2024 11:30
ef1bc52
to
f7d8edb
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
October 22, 2024 02:39
f7d8edb
to
9ac7115
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
November 6, 2024 20:29
8eee8b4
to
7d16e02
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
2 times, most recently
from
November 19, 2024 20:39
e019105
to
557315c
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 23, 2024 14:41
557315c
to
f353f05
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
November 28, 2024 02:39
f353f05
to
b50ca41
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.42.0
->^8.41.0
Release Notes
getsentry/sentry-javascript (@sentry/node)
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!
Bundle size 📦
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)Bundle size 📦
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)Bundle size 📦
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
The Nuxt SDK now allows you to track Pinia state for captured errors. To enable the Pinia plugin, set the
trackPinia
option totrue
in your client config:Read more about the Pinia plugin in the Sentry Pinia Documentation.
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
child_process
andworker_thread
(#13896).mjs
entry files in rollup (#14060)onError
callback (#14002)v8.35.0
Compare Source
v8.34.0
Compare Source
Important Changes
Relevant for users of the
@sentry/nextjs
package: If you have previously configured aSENTRY_IGNORE_API_RESOLUTION_ERROR
environment variable, it is now safe to unset it.Other Changes
getReplay
in replay CDN bundles(#13881)
(#13914)
globalThis
(#13788)
requestAsyncStorageShim.js
template file(#13928)
(#13920)
_not-found
spans for all HTTP methods(#13906)
(#13929)
(#13769)
dataloader
instrumentation from default integrations(#13873)
(#13909)
replay_id
is removed from frozen DSC when stopped(#13893)
sendBufferedReplayOrFlush
to prevent cycles(#13900)
(#13231)
wrapServerRouteWithSentry
to respect ParamMatchers(#13390)
(#13787) (#13854)
(#13905)
vercelWaitUntil
to utils (#13891)Work in this release was contributed by @trzeciak, @gurpreetatwal, @ykzts and @lizhiyao. Thank you for your
contributions!
Bundle size 📦
v8.33.1
Compare Source
(#13809)
Work in this release was contributed by @soapproject. Thank you for your contribution!
v8.33.0
Compare Source
Important Changes
headers()
,params
,searchParams
)(#13828)
Adds support for new dynamic Next.js APIs.
lru-memoizer
instrumentation(#13796)
Adds integration for lru-memoizer using @opentelemetry/instrumentation-lru-memoizer.
unstable_sentryBundlerPluginOptions
to module options(#13811)
Allows passing other options from the bundler plugins (vite and rollup) to Nuxt module options.
Other Changes
wrap()
only returns functions(#13838)
(#13831)
getTraceData
andgetTraceMetaTags
if SDK is disabled(#13760)
(#13800)
(#13815)
(#13812)
(#13826)
Work in this release was contributed by @joshuajaco. Thank you for your contribution!
Bundle size 📦
v8.32.0
Compare Source
Important Changes
(#13527)
Moves the description of navigation related browser spans into the op, e.g. browser - cache -> browser.cache and sets
the description to the performanceEntry objects' names (in this context it is the URL of the page).
feat(node): Add amqplibIntegration (#13714)
feat(nestjs): Add
SentryGlobalGenericFilter
and allow specifying application ref in global filter(#13673)
Adds a
SentryGlobalGenericFilter
that filters both graphql and http exceptions depending on the context.(#13711)
Sets log levels in breadcrumbs for 5xx to error and 4xx to warning.
Other Changes
sampled
flag from dynamic sampling context in Tracing without Performance mode(#13753)
(#13765)
(#13748)
Work in this release was contributed by @Zen-cronic and @Sjoertjuh. Thank you for your contributions!
v8.31.0
Compare Source
Important Changes
dataloader
integration (#13664)This release adds a new integration for the
dataloader
package. The NodeSDK (and all SDKs that depend on it) will now automatically instrument
dataloader
instances. You can also add itmanually:
Other Changes
activationStart
timestamp to pageload span (#13658)deleteSourcemapsAfterUpload
(#13610)http.server.prefetch
op (#13600)disableInstrumentationWarnings
option (#13693)experimental_basicServerTracing
option to Nuxt module (#13643)onError
callback + other small improvements to debugging (#13721)consoleSandbox
(#13690)lazyLoadIntegration
script parent element lookup (#13717)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 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.