chore(deps): bump @sentry/node from 7.87.0 to 7.88.0 #18

Merged
dependabot[bot] merged 1 commit from dependabot/npm_and_yarn/sentry/node-7.88.0 into main 2023-12-16 06:52:46 +08:00
dependabot[bot] commented 2023-12-15 16:23:57 +08:00 (Migrated from github.com)

Bumps @sentry/node from 7.87.0 to 7.88.0.

Release notes

Sourced from @​sentry/node's releases.

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(), ], }); </tr></table>

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

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: &quot;no&quot; 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(), ], </tr></table>

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps [@sentry/node](https://github.com/getsentry/sentry-javascript) from 7.87.0 to 7.88.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript/releases"><code>@​sentry/node</code>'s releases</a>.</em></p> <blockquote> <h2>7.88.0</h2> <h3>Important Changes</h3> <ul> <li><strong>feat(browser): Add browser metrics sdk (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9794">#9794</a>)</strong></li> </ul> <p>The release adds alpha support for <a href="https://github.com/getsentry/sentry/discussions/58584">Sentry developer metrics</a> in the Browser SDKs (<code>@sentry/browser</code> and related framework SDKs). Via the newly introduced APIs, you can now flush metrics directly to Sentry.</p> <p>To enable capturing metrics, you first need to add the <code>MetricsAggregator</code> integration.</p> <pre lang="js"><code>Sentry.init({ dsn: '__DSN__', integrations: [ new Sentry.metrics.MetricsAggregator(), ], }); </code></pre> <p>Then you'll be able to add <code>counters</code>, <code>sets</code>, <code>distributions</code>, and <code>gauges</code> under the <code>Sentry.metrics</code> namespace.</p> <pre lang="js"><code>// Add 4 to a counter named `hits` Sentry.metrics.increment('hits', 4); <p>// Add 2 to gauge named <code>parallel_requests</code>, tagged with <code>happy: &amp;quot;no&amp;quot;</code> Sentry.metrics.gauge('parallel_requests', 2, { tags: { happy: 'no' } });</p> <p>// Add 4.6 to a distribution named <code>response_time</code> with unit seconds Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });</p> <p>// Add 2 to a set named <code>valuable.ids</code> Sentry.metrics.set('valuable.ids', 2); </code></pre></p> <p>In a future release we'll add support for server runtimes (Node, Deno, Bun, Vercel Edge, etc.)</p> <ul> <li><strong>feat(deno): Optionally instrument <code>Deno.cron</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9808">#9808</a>)</strong></li> </ul> <p>This releases add support for instrumenting <a href="https://deno.com/blog/cron">Deno cron's</a> with <a href="https://docs.sentry.io/product/crons/">Sentry cron monitors</a>. This requires v1.38 of Deno run with the <code>--unstable</code> flag and the usage of the <code>DenoCron</code> Sentry integration.</p> <pre lang="ts"><code>// Import from the Deno registry import * as Sentry from &quot;https://deno.land/x/sentry/index.mjs&quot;; <p>Sentry.init({ dsn: '<strong>DSN</strong>', integrations: [ new Sentry.DenoCron(), ], }); &lt;/tr&gt;&lt;/table&gt; </code></pre></p> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md"><code>@​sentry/node</code>'s changelog</a>.</em></p> <blockquote> <h2>7.88.0</h2> <h3>Important Changes</h3> <ul> <li><strong>feat(browser): Add browser metrics sdk (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9794">#9794</a>)</strong></li> </ul> <p>The release adds alpha support for <a href="https://github.com/getsentry/sentry/discussions/58584">Sentry developer metrics</a> in the Browser SDKs (<code>@sentry/browser</code> and related framework SDKs). Via the newly introduced APIs, you can now flush metrics directly to Sentry.</p> <p>To enable capturing metrics, you first need to add the <code>MetricsAggregator</code> integration.</p> <pre lang="js"><code>Sentry.init({ dsn: '__DSN__', integrations: [ new Sentry.metrics.MetricsAggregator(), ], }); </code></pre> <p>Then you'll be able to add <code>counters</code>, <code>sets</code>, <code>distributions</code>, and <code>gauges</code> under the <code>Sentry.metrics</code> namespace.</p> <pre lang="js"><code>// Add 4 to a counter named `hits` Sentry.metrics.increment('hits', 4); <p>// Add 2 to gauge named <code>parallel_requests</code>, tagged with <code>happy: &amp;quot;no&amp;quot;</code> Sentry.metrics.gauge('parallel_requests', 2, { tags: { happy: 'no' } });</p> <p>// Add 4.6 to a distribution named <code>response_time</code> with unit seconds Sentry.metrics.distribution('response_time', 4.6, { unit: 'seconds' });</p> <p>// Add 2 to a set named <code>valuable.ids</code> Sentry.metrics.set('valuable.ids', 2); </code></pre></p> <p>In a future release we'll add support for server runtimes (Node, Deno, Bun, Vercel Edge, etc.)</p> <ul> <li><strong>feat(deno): Optionally instrument <code>Deno.cron</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9808">#9808</a>)</strong></li> </ul> <p>This releases add support for instrumenting <a href="https://deno.com/blog/cron">Deno cron's</a> with <a href="https://docs.sentry.io/product/crons/">Sentry cron monitors</a>. This requires v1.38 of Deno run with the <code>--unstable</code> flag and the usage of the <code>DenoCron</code> Sentry integration.</p> <pre lang="ts"><code>// Import from the Deno registry import * as Sentry from &quot;https://deno.land/x/sentry/index.mjs&quot;; <p>Sentry.init({ dsn: '<strong>DSN</strong>', integrations: [ new Sentry.DenoCron(), ], &lt;/tr&gt;&lt;/table&gt; </code></pre></p> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-javascript/commit/c828397d2c0e7da7d08e65c2ffdda7b07cf34e66"><code>c828397</code></a> release: 7.88.0</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/b3269ca13214681a5ce786e81b3aff206840acaa"><code>b3269ca</code></a> Merge pull request <a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9849">#9849</a> from getsentry/prepare-release/7.88.0</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/8b6af6f0d10fa95fac2bc6dabcafda4fc0dad9ac"><code>8b6af6f</code></a> meta(changelog): Update changelog for 7.88.0</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/d3bf75d3776cecb7c087c4b1f328e6b8551499cc"><code>d3bf75d</code></a> feat(replay): Bump <code>rrweb</code> to 2.6.0 (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9847">#9847</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/6c000b6d005354206d6b59b81d1e215db0cac96a"><code>6c000b6</code></a> feat(browser): Add browser metrics sdk (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9794">#9794</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/8800d5bd0565c0906099c26c1141855f41047f7b"><code>8800d5b</code></a> fix(nextjs): Guard against injecting multiple times (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9807">#9807</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/9d4393dd56f6bc7048896599fbe55b302d770018"><code>9d4393d</code></a> ref(remix): Bump Sentry CLI to ^2.23.0 (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9773">#9773</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/f3d54ded7822175183b68b6b3585e2cb8f17318c"><code>f3d54de</code></a> ref(core): Refactor core integrations to avoid <code>setupOnce</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9813">#9813</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/41c7782ab9b1e9d4e2101425834975f8f7bb4cea"><code>41c7782</code></a> feat(deno): Optionally instrument <code>Deno.cron</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9808">#9808</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/55ecb4fa769f1ca0a47fd968c6555c4e7ebeb67b"><code>55ecb4f</code></a> Merge pull request <a href="https://redirect.github.com/getsentry/sentry-javascript/issues/9819">#9819</a> from getsentry/master</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-javascript/compare/7.87.0...7.88.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@sentry/node&package-manager=npm_and_yarn&previous-version=7.87.0&new-version=7.88.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
Commenting is not possible because the repository is archived.
No description provided.