Sentry

Latest version: v23.7.1

Safety actively analyzes 630305 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 24 of 223

7.53.0

- feat(replay): Add `beforeAddRecordingEvent` Replay option (8124)
- feat(replay): Do not capture replays < 5 seconds (7949)
- fix(nextjs): Guard for non-absolute paths when injecting sentry config (8151)
- fix(nextjs): Import path issue on Windows (8142)
- fix(nextjs): Make `withSentryConfig` isomorphic (8166)
- fix(node): Add debug logging for node checkin (8131)
- fix(node): Add LRU map for tracePropagationTargets calculation (8130)
- fix(node): Remove new URL usage in Undici integration (8147)
- fix(replay): Show the correct Replay config option name `maskFn`
- fix(sveltekit): Avoid double-wrapping load functions (8094)
- fix(tracing): Change where content-length gets added (8139)
- fix(tracing): Use integer for content length (8152)
- fix(utils): Fail silently if the provided Dsn is invalid (8121)
- ref(node): Cache undici trace propagation decisions (8136)
- ref(serverless): Remove relay extension from AWS Layer (8080)

7.52.1

- feat(replay): Capture slow clicks (experimental) (8052)

7.52.0

Important Next.js SDK changes:

This release adds support Vercel Cron Jobs in the Next.js SDK.
The SDK will automatically create [Sentry Cron Monitors](https://docs.sentry.io/product/crons/) for your [Vercel Cron Jobs](https://vercel.com/docs/cron-jobs) configured via `vercel.json` when deployed on Vercel.

You can opt out of this functionality by setting the `automaticVercelMonitors` option to `false`:

js
// next.config.js
const nextConfig = {
sentry: {
automaticVercelMonitors: false,
},
};


(Note: Sentry Cron Monitoring is currently in beta and subject to change. Help us make it better by letting us know what you think. Respond on [GitHub](https://github.com/getsentry/sentry/discussions/42283) or write to us at crons-feedbacksentry.io)

- feat(nextjs): Add API method to wrap API routes with crons instrumentation (8084)
- feat(nextjs): Add automatic monitors for Vercel Cron Jobs (8088)

Other changes

- feat(replay): Capture keyboard presses for special characters (8051)
- fix(build): Don't mangle away global debug ID map (8096)
- fix(core): Return checkin id from client (8116)
- fix(core): Use last error for `ignoreErrors` check (8089)
- fix(docs): Change to `addTracingExtensions` was not documented in MIGRATION.md (8101)
- fix(replay): Check relative URLs correctly (8024)
- fix(tracing-internal): Avoid classifying protocol-relative URLs as same-origin urls (8114)
- ref: Hoist `createCheckinEnvelope` to core package (8082)

7.51.2

- fix(nextjs): Continue traces in data fetchers when there is an already active transaction on the hub (8073)
- fix(sveltekit): Avoid creating the Sentry Vite plugin in dev mode (8065)

7.51.1

- feat(replay): Add event to capture options on checkouts (8011)
- feat(replay): Improve click target detection (8026)
- fix(node): Make sure we use same ID for checkIns (8050)
- fix(replay: Keep session active on key press (8037)
- fix(replay): Move error sampling to before send (8057)
- fix(sveltekit): Wrap `load` when typed explicitly (8049)

**Replay `rrweb` changes:**

`sentry-internal/rrweb` was updated from 1.106.0 to 1.108.0:

- fix: Fix some input masking (esp for radio buttons) ([85](https://github.com/getsentry/rrweb/pull/85))
- fix: Unescaped `:` in CSS rule from Safari ([86](https://github.com/getsentry/rrweb/pull/86))
- feat: Define custom elements (web components) ([87](https://github.com/getsentry/rrweb/pull/87))

Work in this release contributed by sreetamdas. Thank you for your contribution!

7.51.0

Important Changes

- **feat(sveltekit): Auto-wrap `load` functions with proxy module (7994)**

`sentry/sveltekit` now auto-wraps `load` functions in

* `+(page|layout).(ts|js)` files (universal loads)
* `+(page|layout).server.(ts|js)` files (server-only loads)

This means that you don't have to manually add the `wrapLoadWithSentry` and `wrapServerLoadWithSentry` functions around your load functions. The SDK will not interfere with already wrapped `load` functions.

For more details, take a look at the [Readme](https://github.com/getsentry/sentry-javascript/blob/develop/packages/sveltekit/README.md#configure-auto-instrumentation)

- **chore(angular): Upgrade `peerDependencies` to Angular 16 (8035)**

We now officially support Angular 16 in `sentry/angular-ivy`.
Note that `sentry/angular` _does not_ support Angular 16.

- **feat(node): Add ability to send cron monitor check ins (8039)**

**Note: This release contains a bug with generating cron monitors. We recommend you upgrade the JS SDK to 7.51.1 or above to use cron monitoring functionality**

This release adds [Sentry cron monitoring](https://docs.sentry.io/product/crons/) support to the Node SDK.

Check-in monitoring allows you to track a job's progress by completing two check-ins: one at the start of your job and another at the end of your job. This two-step process allows Sentry to notify you if your job didn't start when expected (missed) or if it exceeded its maximum runtime (failed).

ts
const Sentry = require('sentry/node');

// 🟡 Notify Sentry your job is running:
const checkInId = Sentry.captureCheckIn({
monitorSlug: '<monitor-slug>',
status: 'in_progress',
});

// Execute your scheduled task here...

// 🟢 Notify Sentry your job has completed successfully:
Sentry.captureCheckIn({
// make sure you pass in the checkInId generated by the first call to captureCheckIn
checkInId,
monitorSlug: '<monitor-slug>',
status: 'ok',
});


If your job execution fails, you can notify Sentry about the failure:

javascript
// 🔴 Notify Sentry your job has failed:
Sentry.captureCheckIn({
checkInId,
monitorSlug: '<monitor-slug>',
status: 'error',
});


Additional Features and Fixes

- feat(browser): Export makeMultiplexedTransport from browser SDK (8012)
- feat(node): Add `http.method` to node http spans (7991)
- feat(tracing): add body size for fetch requests (7935)
- feat(tracing): Use http.method for span data (7990)
- fix(integrations): Handle windows paths with no prefix or backslash prefix in `RewriteFrames` (7995)
- fix(node): Mark stack frames with url protocol as in-app frames (8008)
- fix(remix): Export `Integration` type declaration as union type (8016)
- fix(replay): Do not add replay_id to DSC while buffering (8020)
- fix(tracing): Don't set method multiple times (8014)
- fix(utils): Normalize `undefined` to `undefined` instead of `"[undefined]"` (8017)

Work in this release contributed by srubin and arjenbrandenburgh. Thank you for your contributions!

Page 24 of 223

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.