Repository navigation
fix(deps): update all non-major dependencies - #29
Merged
Merged
Conversation
Codecov ReportAll modified and coverable lines are covered by tests β
Additional details and impacted files@@ Coverage Diff @@
## main #29 +/- ##
=======================================
Coverage 84.63% 84.63%
=======================================
Files 101 101
Lines 3703 3703
Branches 205 205
=======================================
Hits 3134 3134
Misses 564 564
Partials 5 5 β View full report in Codecov by Sentry. |
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
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:
^8.13.0->^8.17.0^8.5.10->^8.5.11^0.37.91->^0.37.92^0.37.91->^0.37.92v6.2.0->v6.4.0v3.3.0->v3.4.020.15.0->20.15.1^3.3.2->^3.3.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!
discordjs/discord-api-types (discord-api-types)
v0.37.92Compare Source
Bug Fixes
docker/build-push-action (docker/build-push-action)
v6.4.0Compare Source
repositoryandghtokenattributes for GitHub Actions cache backend by @βcrazy-max in https://github.com/docker/build-push-action/pull/1133Full Changelog: docker/build-push-action@v6.3.0...v6.4.0
v6.3.0Compare Source
DOCKER_BUILD_RECORD_UPLOADenvironment variable to enable/disable build record upload by @βcrazy-max in https://github.com/docker/build-push-action/pull/1172DOCKER_BUILD_NO_SUMMARYhas been deprecated. SetDOCKER_BUILD_SUMMARYtofalseinstead by @βcrazy-max in https://github.com/docker/build-push-action/pull/1170 https://github.com/docker/build-push-action/pull/1173Full Changelog: docker/build-push-action@v6.2.0...v6.3.0
docker/setup-buildx-action (docker/setup-buildx-action)
v3.4.0Compare Source
Full Changelog: docker/setup-buildx-action@v3.3.0...v3.4.0
nodejs/node (node)
v20.15.1Compare Source
prettier/prettier (prettier)
v3.3.3Compare Source
diff
Add parentheses for nullish coalescing in ternary (#β16391 by @βcdignam-segment)
This change adds clarity to operator precedence.
Add parentheses for decorator expressions (#β16458 by @βy-schneider)
Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.
Support
@letdeclaration syntax (#β16474 by @βsosukesuzuki)Adds support for Angular v18
@letdeclaration syntax.Please see the following code example. The
@letdeclaration allows you to define local variables within the template:For more details, please refer to the excellent blog post by the Angular Team: Introducing @βlet in Angular.
We also appreciate the Angular Team for kindly answering our questions to implement this feature.
Configuration
π Schedule: Branch creation - "before 12pm on Sunday" (UTC), 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.