chore(deps): update all non-major dependencies #323
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
the
dependencies
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #323 +/- ##
=======================================
Coverage 41.96% 41.96%
=======================================
Files 18 18
Lines 255 255
Branches 61 53 -8
=======================================
Hits 107 107
- Misses 117 148 +31
+ Partials 31 0 -31 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
10 times, most recently
from
f4f3915
to
7d59d54
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
69e2059
to
c4c6e82
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
c523580
to
c19c76c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
8 times, most recently
from
f878737
to
1d5ad47
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
3548629
to
83a9323
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
83a9323
to
0065b27
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:
^19.5.0->^19.6.0^19.5.0->^19.6.0^6.1.0->^6.1.1^3.0.3->^3.0.5^5.2.1->^5.3.1^10.0.1->^10.0.2^7.0.0->^7.0.1^3.17.0->^3.18.1^8.35.0->^8.41.0^1.7.40->^1.9.3^0.2.36->^0.2.37^20.17.1->^20.17.9^9.0.1->^9.1.0^2.1.3->^2.1.4^9.1.6->^9.1.7^3.3.3->^3.4.1^2.8.0->^2.8.1^2.2.3->^2.3.3^6.20.1->^6.21.04.5.1->4.5.3Release Notes
conventional-changelog/commitlint (@commitlint/cli)
v19.6.0Compare Source
Note: Version bump only for package @commitlint/cli
conventional-changelog/commitlint (@commitlint/config-conventional)
v19.6.0Compare Source
Note: Version bump only for package @commitlint/config-conventional
sapphiredev/utilities (@sapphire/decorators)
v6.1.1Compare Source
🏠 Refactor
🐛 Bug Fixes
📝 Documentation
sapphiredev/utilities (@sapphire/fetch)
v3.0.5Compare Source
Changelog
All notable changes to this project will be documented in this file.
v3.0.4Compare Source
🐛 Bug Fixes
sapphiredev/framework (@sapphire/framework)
v5.3.1Compare Source
🐛 Bug Fixes
v5.3.0Compare Source
🐛 Bug Fixes
📝 Documentation
🚀 Features
sapphiredev/plugins (@sapphire/plugin-scheduled-tasks)
v10.0.2Compare Source
🐛 Bug Fixes
bullmqdependency (80d26ac)ScheduledTasksResolvableNoPayload(ec27a29)📝 Documentation
sapphiredev/plugins (@sapphire/plugin-subcommands)
v7.0.1Compare Source
🐛 Bug Fixes
📝 Documentation
getsentry/sentry-javascript (@sentry/node)
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/nestjsand remove theSentryServiceafterwards.The
SentryGlobalGenericFilterwas deprecated. Use theSentryGlobalFilterinstead which is a drop-in replacement.The
SentryGlobalGraphQLFilterwas deprecated. Use theSentryGlobalFilterinstead which is a drop-in replacement.feat(node): Deprecate
nestIntegrationandsetupNestErrorHandlerin favor of using@sentry/nestjs(#14374)The
nestIntegrationandsetupNestErrorHandlerfunctions from@sentry/nodewere deprecated and will be removed in the next major version of the SDK. If you're using@sentry/nodein a NestJS application, we recommend switching to our new dedicated@sentry/nestjspackage.Other Changes
normalizedRequestonsdkProcessingMetadatais merged (#14315)@sentry/utilsinto@sentry/core(#14382)__selfand__sourceattributes on feedback nodes (#14356)Bundle size 📦
v8.39.0Compare Source
Important Changes
The
@sentry/nestjsSDK will now capture performance data for NestJS Events (@nestjs/event-emitter)Other Changes
@SentryExceptionCapturedfor@WithSentry(#14322)SentryServicebehaviour into@sentry/nestjsSDKinit()(#14321)SentryGlobalFilter(#14320)childProcessIntegrationforprocessThreadBreadcrumbIntegrationand deprecate it (#14334)_sentryModuleMetadatais not mangled (#14344)sentry.sourceattribute tocustomwhen callingspan.updateNameonSentrySpan(#14251)Requesttype in favor ofRequestEventData(#14317)transactioninrequestDataIntegration(#14306)Bundle size 📦
v8.38.0Compare Source
knexintegration (#13526)tediousintegration (#13486)debug_metawith ANR events (#14203)Work in this release was contributed by @grahamhency, @Zen-cronic, @gilisho and @phuctm97. Thank you for your contributions!
v8.37.1Compare Source
v8.37.0Compare Source
Important Changes
piniaIntegrationConfiguration
📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.