chore(deps): update all non-major dependencies #136
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
archive/dbh-utils!136
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/all-minor-patch"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
8.10.0->8.17.08.10.0->8.17.020.14.6->20.14.108.4.3->8.5.15.4.5->5.5.3Release Notes
getsentry/sentry-javascript (@sentry/node)
v8.17.0Compare Source
v8.16.0Compare Source
Important Changes
Previously, the
@sentry/nextjsSDK automatically recorded spans in the form of transactions for each of your top-levelserver components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have
a root span, and more importantly, if you had data stream to the client, its duration was not captured because the
server component spans had finished before the data could finish streaming.
With this release, we will capture the duration of App Router requests in their entirety as a single transaction with
server component spans being descendants of that transaction. This means you will get more data that is also more
accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it
has before.
Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no
longer receive server component transactions like
Page Server Component (/path/to/route)(unless using the Edgeruntime), and you will instead receive transactions for your App Router SSR requests that look like
GET /path/to/route.If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.
The
@sentry/nestjsSDK now includes a@SentryCrondecorator that can be used to augment the native NestJS@Crondecorator to send check-ins to Sentry before and after each cron job run:
Other Changes
httpIntegration(#12761)addPluginTemplate(#12760)himport inScreenshotEditor(#12784)autoSessionTrackingis enabled by default (#12790)v8.15.0Compare Source
on(#11710)spanTimeInputToSecondsfor otel span exporter (#12699)lazyLoadIntegration(#12766)jsxRuntime: 'classic'to prevent breaking react 17 (#12775)getStack()(#12737)Work in this release was contributed by @arturovt and @jaulz. Thank you for your contributions!
v8.14.0Compare Source
Important Changes
The
@sentry/nestjsSDK no longer captures 4xx errors automatically.Other Changes
JSX(#12691)registerEsmLoaderHooksoption (#12684)afterAllSetupinstead of next tick (#12709)Work in this release was contributed by @quisido. Thank you for your contribution!
v8.13.0Compare Source
Important Changes
@sentry/nestjs)in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (
@sentry/node) supporting the same set offeatures. See the docs for how to use the SDK.
Other Changes
2.20.1(#12641)v8.12.0Compare Source
Important Changes
This release introduces breaking changes to the
@sentry/solidpackage (which is currently out in alpha).We've made it easier to get started with the solid router integration by removing the need to pass use* hooks
explicitly to
solidRouterBrowserTracingIntegration. ImportsolidRouterBrowserTracingIntegrationfrom@sentry/solid/solidrouterand add it toSentry.initSentry.init()now returns a client directly, so you don't need to explicitly callgetClient()anymore:deleteSourcemapsAfterUploadoption (#12457)This adds an easy way to delete sourcemaps immediately after uploading them:
maxSpanWaitDuration(#12610)Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before
discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is
necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However,
if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early.
In this case, you can increase this duration to a value that fits your expected data.
Other Changes
window.Sentry(#12580)isRemixV2as optional in exposed types. (#12614)Work in this release was contributed by @n4bb12. Thank you for your contribution!
v8.11.0Compare Source
Important Changes
parentSpanoption tostartSpan*APIs (#12567)We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to
explicitly manage the parent-child relationship of your spans better.
Other Changes
@sentry/nodeexports from framework SDKs. (#12589)Bundle size 📦
Automattic/mongoose (mongoose)
v8.5.1Compare Source
==================
v8.5.0Compare Source
==================
v8.4.5Compare Source
==================
v8.4.4Compare Source
==================
Microsoft/TypeScript (typescript)
v5.5.3Compare Source
v5.5.2Compare Source
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.