New version of all of sentry (7.88.0) broke the build

[depfu]

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
@sentry/node	^7.75.1	7.88.0

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of @sentry/node for this test run.

What changed?

✳️ @​sentry/node (^7.75.1 → 7.88.0) · Repo · Changelog

Release Notes

7.88.0

Important Changes

• feat(browser): Add browser metrics sdk (#9794)

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.

Sentry.init({
  dsn: '__DSN__',
  integrations: [
    new Sentry.metrics.MetricsAggregator(),
  ],
});

Then you'll be able to add counters, sets, distributions, and gauges under the Sentry.metrics namespace.

// Add 4 to a counter named `hits`
Sentry.metrics.increment('hits', 4);
// Add 2 to gauge named parallel_requests, tagged with happy: "no"

Sentry.metrics.gauge('parallel_requests', 2, { tags: { happy: 'no' } });
// Add 4.6 to a distribution named response_time with unit seconds

Sentry.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.)

• feat(deno): Optionally instrument 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 the DenoCron Sentry integration.

// Import from the Deno registry
import * as Sentry from "https://deno.land/x/sentry/index.mjs";
Sentry.init({

dsn: 'DSN',

integrations: [

new Sentry.DenoCron(),

],

});

Other Changes

• feat(replay): Bump rrweb to 2.6.0 (#9847)
• fix(nextjs): Guard against injecting multiple times (#9807)
• ref(remix): Bump Sentry CLI to ^2.23.0 (#9773)

Bundle size 📦

Path	Size
@sentry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped)	75.24 KB
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	66.63 KB
@sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped)	60.22 KB
@sentry/browser (incl. Tracing) - Webpack (gzipped)	31.3 KB
@sentry/browser (incl. Feedback) - Webpack (gzipped)	29.9 KB
@sentry/browser - Webpack (gzipped)	21.56 KB
@sentry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped)	72.58 KB
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	64.31 KB
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	30.58 KB
@sentry/browser - ES6 CDN Bundle (gzipped)	22.61 KB
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	202.5 KB
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	92.65 KB
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	67.63 KB
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	33.47 KB
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	66.97 KB
@sentry/react - Webpack (gzipped)	21.6 KB
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	83.73 KB
@sentry/nextjs Client - Webpack (gzipped)	48.41 KB
@sentry-internal/feedback - Webpack (gzipped)	16.19 KB

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 11 commits:

• release: 7.88.0
• Merge pull request #9849 from getsentry/prepare-release/7.88.0
• meta(changelog): Update changelog for 7.88.0
• feat(replay): Bump `rrweb` to 2.6.0 (#9847)
• feat(browser): Add browser metrics sdk (#9794)
• fix(nextjs): Guard against injecting multiple times (#9807)
• ref(remix): Bump Sentry CLI to ^2.23.0 (#9773)
• ref(core): Refactor core integrations to avoid `setupOnce` (#9813)
• feat(deno): Optionally instrument `Deno.cron` (#9808)
• Merge pull request #9819 from getsentry/master
• Merge branch 'release/7.87.0'

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #252.