Sentry

Latest version: v23.7.1

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

Scan your dependencies

Page 36 of 223

7.12.1

- feat(nextjs): Connect trace between data-fetching methods and pageload (5655)
- feat(react): Support useRoutes hook of React Router 6 (5624)
- feat(remix): Continue transaction from request headers (5600)
- feat(utils): Add function for ensuring input is an array (5668)
- fix(utils): Remove Element dom type (5675)
- fix(node): `contexts` cannot be overridden and `culture` never included (5677)
- chore: Remove typedoc from READMEs (5678)

7.12.0

This release adds an environment check in `sentry/nextjs` for Vercel deployments (using the `VERCEL_ENV` env variable), and only enables `SentryWebpackPlugin` if the environment is `production`. To override this, [setting `disableClientWebpackPlugin` or `disableServerWebpackPlugin` to `false`](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#disable-sentrywebpackplugin) now takes precedence over other checks, rather than being a no-op. Note: Overriding this is not recommended! It can increase build time and clog Release Health data in Sentry with inaccurate noise.

- feat(nextjs): Create transactions in `getInitialProps` and `getServerSideProps` (5593)
- feat(nextjs): Instrument server-side `getInitialProps` of `_app`, `_document` and `_error` (5604)
- feat(node): Populate `event.contexts` for Node.js (5512)
- feat(svelte): Add Component Tracking (5612)
- fix(browser): use valid urls in Request checks (5630)
- fix(integrations): Don't add empty stack trace in `RewriteFrames` (5625)
- fix(nextjs): Start navigation transactions on same-route navigations (5642)
- fix(nextjs): Don't run webpack plugin on non-prod Vercel deployments (5603)
- fix(node): Avoid catching domain errors in request handler (5627)
- fix(serverless): Check for existence of callback in GCP event handler before calling (5608)
- ref(nextjs): Add warning about non-hidden sourcemaps (5649)
- ref(nextjs): Use proxy loader for wrapping all data-fetching functions (5602)
- ref(tracing): Remove mark measurements (5605)
- ref(tracing): Update long task description (5601)
- chore(svelte): Detect and report SvelteKit usage (5594)

Work in this release contributed by lucas-zimerman, GJZwiers, and mohd-akram. Thank you for your contributions!

7.12.0beta.0

Various fixes & improvements

- feat: Add support for profiling on iOS (1652) by armcknight

7.11.1

- fix(remix): Store transaction on express req (5595)

7.11.0

This release introduces updates the [`tracingOrigins` option](https://docs.sentry.io/platforms/javascript/performance/instrumentation/automatic-instrumentation/#tracingorigins) to not attach any headers/create an spans when supplied with an empty array (`[]`). Previously, we would supply the default `tracingOrigins` if an empty array was set as the `tracingOrigins` option.

- fix(core): Suppress stack when `SentryError` isn't an error (5562)
- feat(nextjs): Wrap server-side getInitialProps (5546)
- feat(nextjs): Improve pageload transaction creation (5574)
- feat(nextjs): Add spans and route parameterization in data fetching wrappers (5564)
- feat(nextjs): Create spans and route parameterization in server-side `getInitialProps` (5587)
- fix(remix): Use domains to prevent scope bleed (5570)
- fix(remix): Wrap domains properly on instrumentServer (5590)
- feat(remix): Add route ID to remix routes (5568)
- feat(remix): Export a manual wrapper for custom Express servers (5524)
- feat(tracing): Add long task collection (5529)
- feat(tracing): Allow for setting of an empty array (5583)

7.10.2

- fix: Crash in UIViewControllerSwizzling (1692)

Page 36 of 223

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.