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

fix(deps): update sentry packages to v7.57.0 (minor) #270

Merged
merged 1 commit into from
Jul 10, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 30, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/react (source) 7.53.1 -> 7.57.0 age adoption passing confidence
@sentry/tracing (source) 7.53.1 -> 7.57.0 age adoption passing confidence

Release Notes

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

v7.57.0

Compare Source

Important Changes
  • build: Update typescript from 3.8.3 to 4.9.5 (#​8255)

This release version bumps the internally used typescript version from 3.8.x to 4.9.x.
We use ds-downlevel to generate two versions of our types, one for >=3.8, one for >=4.9.
This means that this change should be fully backwards compatible and not have any noticable user impact,
but if you still encounter issues please let us know.

  • feat(types): Add tracePropagationTargets to top level options (#​8395)

Instead of passing tracePropagationTargets to the BrowserTracing integration, you can now define them on the top level:

Sentry.init({
  tracePropagationTargets: ['api.site.com'],
});
  • fix(angular): Filter out TryCatch integration by default (#​8367)

The Angular and Angular-ivy SDKs will not install the TryCatch integration anymore by default.
This integration conflicted with the SentryErrorHander, sometimes leading to duplicated errors and/or missing data on events.

  • feat(browser): Better event name handling for non-Error objects (#​8374)

When capturing non-errors via Sentry.captureException(), e.g. Sentry.captureException({ prop: "custom object" }),
we now generate a more helpful value for the synthetic exception. Instead of e.g. Non-Error exception captured with keys: currentTarget, isTrusted, target, type, you'll now get messages like:

Object captured as exception with keys: prop1, prop2
Event `MouseEvent` (type=click) captured as exception
Event `ErrorEvent` captured as exception with message `Script error.`
Other Changes
  • feat(browser): Send profiles in same envelope as transactions (#​8375)
  • feat(profiling): Collect timings on profiler stop calls (#​8409)
  • feat(replay): Do not capture replays < 5 seconds (GA) (#​8277)
  • feat(tracing): Add experiment to capture http timings (#​8371)
  • feat(tracing): Add http.response.status_code to span.data (#​8366)
  • fix(angular): Stop routing spans on navigation cancel and error events (#​8369)
  • fix(core): Only start spans in trace if tracing is enabled (#​8357)
  • fix(nextjs): Inject init calls via loader instead of via entrypoints (#​8368)
  • fix(replay): Mark ui.slowClickDetected clickCount as optional (#​8376)
  • fix(serverless): Export autoDiscoverNodePerformanceMonitoringIntegrations from SDK (#​8382)
  • fix(sveltekit): Check for cached requests in client-side fetch instrumentation (#​8391)
  • fix(sveltekit): Only instrument SvelteKit fetch if the SDK client is valid (#​8381)
  • fix(tracing): Instrument Prisma client in constructor of integration (#​8383)
  • ref(replay): More graceful sessionStorage check (#​8394)
  • ref(replay): Remove circular dep in replay eventBuffer (#​8389)

v7.56.0

Compare Source

  • feat(replay): Rework slow click & multi click detection (#​8322)
  • feat(replay): Stop replay when event buffer exceeds max. size (#​8315)
  • feat(replay): Consider window.open for slow clicks (#​8308)
  • fix(core): Temporarily store debug IDs in stack frame and only put them into debug_meta before sending (#​8347)
  • fix(remix): Extract deferred responses correctly in root loaders. (#​8305)
  • fix(vue): Don't call next in Vue router 4 instrumentation (#​8351)

v7.55.2

Compare Source

  • fix(replay): Stop exporting EventType from @sentry-internal/rrweb (#​8334)
  • fix(serverless): Export captureCheckIn (#​8333)

v7.55.1

Compare Source

  • fix(replay): Do not export types from @sentry-internal/rrweb (#​8329)

v7.55.0

Compare Source

  • feat(replay): Capture slow clicks (GA) (#​8298)
  • feat(replay): Improve types for replay recording events (#​8224)
  • fix(nextjs): Strip query params from transaction names of navigations to unknown routes (#​8278)
  • fix(replay): Ignore max session life for buffered sessions (#​8258)
  • fix(sveltekit): Export captureCheckIn (#​8313)
  • ref(svelte): Add Svelte 4 as a peer dependency (#​8280)

v7.54.0

Compare Source

Important Changes
  • feat(core): Add default entries to ignoreTransactions for Healthchecks #​8191

    All SDKs now filter out health check transactions by default.
    These are transactions where the transaction name matches typical API health check calls, such as /^.*healthy.*$/ or /^. *heartbeat.*$/. Take a look at this list to learn which regexes we currently use to match transaction names.
    We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default.
    These filters are implemented as default values for the top level ignoreTransactions option.

    You can disable this filtering by manually specifiying the InboundFilters integration and setting the disableTransactionDefaults option:

    Sentry.init({
      //...
      integrations: [new InboundFilters({ disableTransactionDefaults: true })],
    })
  • feat(replay): Add mutationBreadcrumbLimit and mutationLimit to Replay Options (#​8228)

    The previously experimental options mutationBreadcumbLimit and mutationLimit have been promoted to regular Replay integration options.

    A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers.
    Use mutationBreadcrumbLimit to send a breadcrumb along with your recording if the mutation limit was reached.
    Use mutationLimit to stop recording if the mutation limit was reached.

  • feat(sveltekit): Add source maps support for Vercel (lambda) (#​8256)

    • feat(sveltekit): Auto-detect SvelteKit adapters (#​8193)

    The SvelteKit SDK can now be used if you deploy your SvelteKit app to Vercel.
    By default, the SDK's Vite plugin will detect the used adapter and adjust the source map uploading config as necessary.
    If you want to override the default adapter detection, you can specify the adapter option in the sentrySvelteKit options:

    // vite.config.js
    export default defineConfig({
      plugins: [
        sentrySvelteKit({
          adapter: 'vercel',
        }),
        sveltekit(),
      ],
    });

    Currently, the Vite plugin will configure itself correctly for @sveltejs/adapter-auto, @sveltejs/adapter-vercel and @sveltejs/adapter-node.

    Important: The SvelteKit SDK is not yet compatible with Vercel's edge runtime.
    It will only work for lambda functions.

Other Changes
  • feat(replay): Throttle breadcrumbs to max 300/5s (#​8086)
  • feat(sveltekit): Add option to control handling of unknown server routes (#​8201)
  • fix(node): Strip query and fragment from request URLs without route parameters (#​8213)
  • fix(remix): Don't log missing parameters warning on server-side. (#​8269)
  • fix(remix): Pass loadContext through wrapped document request function (#​8268)
  • fix(replay): Guard against missing key (#​8246)
  • fix(sveltekit): Avoid capturing redirects and 4xx Http errors in request Handlers (#​8215)
  • fix(sveltekit): Bump magicast to support satisfied keyword (#​8254)
  • fix(wasm): Avoid throwing an error when WASM modules are loaded from blobs (#​8263)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC).

🚦 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 Jun 30, 2023
@spaenleh spaenleh merged commit 0cd3de5 into main Jul 10, 2023
@renovate renovate bot deleted the renovate/sentry-packages branch July 10, 2023 20:14
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 v1.0.2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant