Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update sentry-javascript monorepo to v7.92.0 #214

Merged
merged 1 commit into from
Jan 4, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 25, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/integrations (source) 7.86.0 -> 7.92.0 age adoption passing confidence
@sentry/node (source) 7.86.0 -> 7.92.0 age adoption passing confidence
@sentry/tracing (source) 7.86.0 -> 7.92.0 age adoption passing confidence

Release Notes

getsentry/sentry-javascript (@​sentry/integrations)

v7.92.0

Compare Source

Important Changes
Deprecations
  • feat(core): Add span.updateName() and deprecate span.setName() (#​10018)
  • feat(core): Deprecate span.getTraceContext() (#​10032)
  • feat(core): Deprecate span.toTraceparent() in favor of spanToTraceHeader() util (#​10031)
  • feat(core): Deprecate trace in favor of startSpan (#​10012)
  • feat(core): Deprecate span toContext() and updateWithContext() (#​10030)
  • ref: Deprecate deepReadDirSync (#​10016)
  • ref: Deprecate lastEventId() (#​10043)

Please take a look at the Migration docs for more details. These methods will be removed in the upcoming v8 major release.

Cron Monitoring Support for cron and node-cron libraries
  • feat(node): Instrumentation for cron library (#​9999)
  • feat(node): Instrumentation for node-cron library (#​9904)

This release adds instrumentation for the cron and node-cron libraries. This allows you to monitor your cron jobs with Sentry cron monitors.

For cron:

import * as Sentry from '@​sentry/node';
import { CronJob } from 'cron';

const CronJobWithCheckIn = Sentry.cron.instrumentCron(CronJob, 'my-cron-job');

// use the constructor
const job = new CronJobWithCheckIn('* * * * *', () => {
  console.log('You will see this message every minute');
});

// or from
const job = CronJobWithCheckIn.from({
  cronTime: '* * * * *',
  onTick: () => {
    console.log('You will see this message every minute');
  },
});

For node-cron:

import * as Sentry from '@​sentry/node';
import cron from 'node-cron';

const cronWithCheckIn = Sentry.cron.instrumentNodeCron(cron);

cronWithCheckIn.schedule(
  '* * * * *',
  () => {
    console.log('running a task every minute');
  },
  { name: 'my-cron-job' },
);
Other Changes
  • feat(astro): Add enabled option to Astro integration options (#​10007)
  • feat(core): Add attributes to Span (#​10008)
  • feat(core): Add setClient() and getClient() to Scope (#​10055)
  • feat(integrations): Capture error cause with captureErrorCause in ExtraErrorData integration (#​9914)
  • feat(node-experimental): Allow to pass base span options to trace methods (#​10006)
  • feat(node): Local variables via async inspector in node 19+ (#​9962)
  • fix(astro): handle commonjs related issues (#​10042)
  • fix(astro): Handle non-utf8 encoded streams in middleware (#​9989)
  • fix(astro): prevent sentry from externalized (#​9994)
  • fix(core): Ensure withScope sets current scope correctly with async callbacks (#​9974)
  • fix(node): ANR fixes and additions (#​9998)
  • fix(node): Anr should not block exit (#​10035)
  • fix(node): Correctly resolve module name (#​10001)
  • fix(node): Handle inspector already open (#​10025)
  • fix(node): Make NODE_VERSION properties required (#​9964)
  • fix(node): Anr doesn't block exit (#​10064)
  • fix(utils): use correct typeof URL validation (#​10028)
  • perf(astro): reduce unnecessary path resolutions (#​10021)
  • ref(astro): Use astro logger instead of console (#​9995)
  • ref(remix): Isolate Express instrumentation from server auto-instrumentation. (#​9966)

Work in this release contributed by @​joshkel. Thank you for your contribution!

Bundle size 📦

Path Size
@​sentry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped) 76.1 KB
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped) 67.5 KB
@​sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped) 61.1 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped) 32.08 KB
@​sentry/browser (incl. Feedback) - Webpack (gzipped) 30.49 KB
@​sentry/browser - Webpack (gzipped) 22.21 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped) 73.53 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 65.2 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 31.37 KB
@​sentry/browser - ES6 CDN Bundle (gzipped) 23.29 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 204.35 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 94.24 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed) 69.09 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 34.33 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped) 67.91 KB
@​sentry/react - Webpack (gzipped) 22.23 KB
@​sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped) 84.53 KB
@​sentry/nextjs Client - Webpack (gzipped) 49.14 KB
@​sentry-internal/feedback - Webpack (gzipped) 16.73 KB

v7.91.0

Compare Source

Important Changes
  • feat: Add server runtime metrics aggregator (#​9894)

The release adds alpha support for Sentry developer metrics in the server runtime SDKs (@sentry/node, @sentry/deno, @sentry/nextjs server-side, etc.). Via the newly introduced APIs, you can now flush metrics directly to Sentry.

To enable capturing metrics, you first need to add the metricsAggregator experiment to your Sentry.init call.

Sentry.init({
  dsn: '__DSN__',
  _experiments: {
    metricsAggregator: true,
  },
});

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 `type: "a"`
Sentry.metrics.gauge('parallel_requests', 2, { tags: { type: 'a' } });

// 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);
  • feat(node): Rework ANR to use worker script via an integration (#​9945)

The ANR tracking integration for Node has been reworked to use an integration. ANR tracking now requires a minimum Node version of 16 or higher. Previously you had to call Sentry.enableANRDetection before running your application, now you can simply add the Anr integration to your Sentry.init call.

import * as Sentry from '@​sentry/node';

Sentry.init({
  dsn: 'https://[email protected]/1337',
  integrations: [new Sentry.Integrations.Anr({ captureStackTrace: true, anrThreshold: 200 })],
});
Other Changes
  • feat(breadcrumbs): Send component names on UI breadcrumbs (#​9946)
  • feat(core): Add getGlobalScope() method (#​9920)
  • feat(core): Add getIsolationScope() method (#​9957)
  • feat(core): Add span.end() to replace span.finish() (#​9954)
  • feat(core): Ensure startSpan & startSpanManual fork scope (#​9955)
  • feat(react): Send component name on spans (#​9949)
  • feat(replay): Send component names in replay breadcrumbs (#​9947)
  • feat(sveltekit): Add options to configure fetch instrumentation script for CSP (#​9969)
  • feat(tracing): Send component name on interaction spans (#​9948)
  • feat(utils): Add function to extract relevant component name (#​9921)
  • fix(core): Rethrow caught promise rejections in startSpan, startSpanManual, trace (#​9958)

v7.90.0

Compare Source

  • feat(replay): Change to use preset quality values (#​9903)
  • fix(replay): Adjust development hydration error messages (#​9922)
  • fix(sveltekit): Add types field to package.json exports (#​9926)

v7.89.0

Compare Source

Important Changes
Deprecations
  • feat(core): Deprecate configureScope (#​9887)
  • feat(core): Deprecate pushScope & popScope (#​9890)

This release deprecates configureScope, pushScope, and popScope, which will be removed in the upcoming v8 major release.

Hapi Integration
  • feat(node): Add Hapi Integration (#​9539)

This release adds an integration for Hapi. It can be used as follows:

const Sentry = require('@​sentry/node');
const Hapi = require('@​hapi/hapi');

const init = async () => {
    const server = Hapi.server({
      // your server configuration ...
    });

    Sentry.init({
      dsn: '__DSN__',
      tracesSampleRate: 1.0,
      integrations: [
        new Sentry.Integrations.Hapi({ server }),
      ],
    });

    server.route({
      // your route configuration ...
    });

    await server.start();
};
SvelteKit 2.0
  • chore(sveltekit): Add SvelteKit 2.0 to peer dependencies (#​9861)

This release adds support for SvelteKit 2.0 in the @sentry/sveltekit package. If you're upgrading from SvelteKit 1.x to 2.x and already use the Sentry SvelteKit SDK, no changes apart from upgrading to this (or a newer) version are necessary.

Other Changes
  • feat(core): Add type & utility for function-based integrations (#​9818)
  • feat(core): Update withScope to return callback return value (#​9866)
  • feat(deno): Support Deno.CronSchedule for cron jobs (#​9880)
  • feat(nextjs): Auto instrument generation functions (#​9781)
  • feat(nextjs): Connect server component transactions if there is no incoming trace (#​9845)
  • feat(node-experimental): Update to new Scope APIs (#​9799)
  • feat(replay): Add canvas.type setting (#​9877)
  • fix(nextjs): Export createReduxEnhancer (#​9854)
  • fix(remix): Do not capture thrown redirect responses. (#​9909)
  • fix(sveltekit): Add conditional exports (#​9872)
  • fix(sveltekit): Avoid capturing 404 errors on client side (#​9902)
  • fix(utils): Do not use Event type in worldwide (#​9864)
  • fix(utils): Support crypto.getRandomValues in old Chromium versions (#​9251)
  • fix(utils): Update eventFromUnknownInput to avoid scope pollution & getCurrentHub (#​9868)
  • ref: Use addBreadcrumb directly & allow to pass hint (#​9867)

Work in this release contributed by @​adam187, and @​jghinestrosa. Thank you for your contributions!

v7.88.0

Compare Source

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)

v7.87.0

Compare Source

  • feat: Add top level getCurrentScope() method (#​9800)
  • feat(replay): Bump rrweb to 2.5.0 (#​9803)
  • feat(replay): Capture hydration error breadcrumb (#​9759)
  • feat(types): Add profile envelope types (#​9798)
  • fix(astro): Avoid RegExp creation during route interpolation (#​9815)
  • fix(browser): Avoid importing from ./exports (#​9775)
  • fix(nextjs): Catch rejecting flushes (#​9811)
  • fix(nextjs): Fix devserver CORS blockage when assetPrefix is defined (#​9766)
  • fix(node): Capture errors in tRPC middleware (#​9782)

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 25, 2023
@renovate renovate bot changed the title chore(deps): update sentry-javascript monorepo to v7.91.0 chore(deps): update sentry-javascript monorepo to v7.92.0 Jan 4, 2024
@renovate renovate bot force-pushed the renovate/sentry-javascript-monorepo branch from 0b2dca3 to b6309aa Compare January 4, 2024 19:26
@Snazzah Snazzah merged commit 4a1206f into master Jan 4, 2024
2 checks passed
@renovate renovate bot deleted the renovate/sentry-javascript-monorepo branch January 4, 2024 22:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant