[Snyk] Upgrade @sentry/nextjs from 7.80.1 to 7.88.0 #536
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @sentry/nextjs from 7.80.1 to 7.88.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.
Release notes
Package name: @sentry/nextjs
Important Changes
The release adds alpha support for Sentry developer metrics in the Browser SDKs (
@ sentry/browser
and related framework SDKs). Via the newly introduced APIs, you can now flush metrics directly to Sentry.To enable capturing metrics, you first need to add the
MetricsAggregator
integration.Then you'll be able to add
counters
,sets
,distributions
, andgauges
under theSentry.metrics
namespace.hits
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named
parallel_requests
, tagged withhappy: "no"
Sentry.metrics.gauge('parallel_requests', 2, { tags: { happy: 'no' } });
// Add 4.6 to a distribution named
response_time
with unit secondsSentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });
// Add 2 to a set named
valuable.ids
Sentry.metrics.set('valuable.ids', 2);
In a future release we'll add support for server runtimes (Node, Deno, Bun, Vercel Edge, etc.)
Deno.cron
(#9808)This releases add support for instrumenting Deno cron's with Sentry cron monitors. This requires v1.38 of Deno run with the
--unstable
flag and the usage of theDenoCron
Sentry integration.import * as Sentry from "https://deno.land/x/sentry/index.mjs";
Sentry.init({
dsn: 'DSN',
integrations: [
new Sentry.Integrations.DenoCron(),
],
});
Other Changes
rrweb
to 2.6.0 (#9847)Bundle size 📦
getCurrentScope()
method (#9800)rrweb
to 2.5.0 (#9803)./exports
(#9775)assetPrefix
is defined (#9766)Bundle size 📦
process.env.NODE_ENV
access in Spotlight integration (#9748)Bundle size 📦
Read more
Read more
Read more
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:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs