search

wydengyre / pgs-to-srt

OCR-based conversion of PGS subtitles to SRT
GNU Affero General Public License v3.0
20 stars 4 forks source link

Bump @sentry/tracing from 7.87.0 to 7.88.0 in /web #145

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 9 months ago

Bumps @sentry/tracing from 7.87.0 to 7.88.0.

Release notes

Sourced from @​sentry/tracing'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/tracing'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 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)
dependabot[bot] commented 8 months ago

A newer version of @​sentry/tracing exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

dependabot[bot] commented 8 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.