[Snyk] Upgrade @sentry/react from 8.15.0 to 8.17.0 #370
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.
Snyk has created this PR to upgrade @sentry/react from 8.15.0 to 8.17.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 2 versions ahead of your current version.
The recommended version was released on 22 days ago.
Release notes
Package name: @sentry/react
Bundle size 📦
Important Changes
Previously, the
@ sentry/nextjs
SDK 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/nestjs
SDK now includes a@ SentryCron
decorator that can be used to augment the native NestJS@ Cron
decorator to send check-ins to Sentry before and after each cron job run:
import { SentryCron, MonitorConfig } from '@ sentry/nestjs';
import type { MonitorConfig } from '@ sentry/types';
const monitorConfig: MonitorConfig = {
schedule: {
type: 'crontab',
value: '* * * * *',
},
checkinMargin: 2, // In minutes. Optional.
maxRuntime: 10, // In minutes. Optional.
timezone: 'America/Los_Angeles', // Optional.
};
export class MyCronService {
@Cron('* * * * *')
@SentryCron('my-monitor-slug', monitorConfig)
handleCron() {
// Your cron job logic here
}
}
Other Changes
httpIntegration
(#12761)addPluginTemplate
(#12760)h
import inScreenshotEditor
(#12784)autoSessionTracking
is enabled by default (#12790)Bundle size 📦
on
(#11710)spanTimeInputToSeconds
for 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!
Bundle size 📦
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: