fix(deps): update sentry-javascript monorepo to v7.57.0 #3644

renovate · 2023-06-28T16:04:43Z

renovate commented

2023-06-28 16:04:43 +00:00

This PR contains the following updates:

Package	Type	Update	Change
@sentry/tracing (source)	dependencies	minor	`7.56.0` -> `7.57.0`
@sentry/vue (source)	dependencies	minor	`7.56.0` -> `7.57.0`

Release Notes

getsentry/sentry-javascript

`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)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@sentry/tracing](https://github.com/getsentry/sentry-javascript/tree/master/packages/tracing) ([source](https://github.com/getsentry/sentry-javascript)) | dependencies | minor | [`7.56.0` -> `7.57.0`](https://renovatebot.com/diffs/npm/@sentry%2ftracing/7.56.0/7.57.0) | | [@sentry/vue](https://github.com/getsentry/sentry-javascript/tree/master/packages/vue) ([source](https://github.com/getsentry/sentry-javascript)) | dependencies | minor | [`7.56.0` -> `7.57.0`](https://renovatebot.com/diffs/npm/@sentry%2fvue/7.56.0/7.57.0) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript</summary> ### [`v7.57.0`](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#7570) [Compare Source](https://github.com/getsentry/sentry-javascript/compare/7.56.0...7.57.0) ##### Important Changes - **build: Update typescript from 3.8.3 to 4.9.5 ([#8255](https://github.com/getsentry/sentry-javascript/issues/8255))** This release version [bumps the internally used typescript version from 3.8.x to 4.9.x](https://github.com/getsentry/sentry-javascript/pull/8255). 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](https://github.com/getsentry/sentry-javascript/issues/8395))** Instead of passing `tracePropagationTargets` to the `BrowserTracing` integration, you can now define them on the top level: ```js Sentry.init({ tracePropagationTargets: ['api.site.com'], }); ``` - **fix(angular): Filter out `TryCatch` integration by default ([#8367](https://github.com/getsentry/sentry-javascript/issues/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](https://github.com/getsentry/sentry-javascript/issues/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](https://github.com/getsentry/sentry-javascript/issues/8375)) - feat(profiling): Collect timings on profiler stop calls ([#8409](https://github.com/getsentry/sentry-javascript/issues/8409)) - feat(replay): Do not capture replays < 5 seconds (GA) ([#8277](https://github.com/getsentry/sentry-javascript/issues/8277)) - feat(tracing): Add experiment to capture http timings ([#8371](https://github.com/getsentry/sentry-javascript/issues/8371)) - feat(tracing): Add `http.response.status_code` to `span.data` ([#8366](https://github.com/getsentry/sentry-javascript/issues/8366)) - fix(angular): Stop routing spans on navigation cancel and error events ([#8369](https://github.com/getsentry/sentry-javascript/issues/8369)) - fix(core): Only start spans in `trace` if tracing is enabled ([#8357](https://github.com/getsentry/sentry-javascript/issues/8357)) - fix(nextjs): Inject init calls via loader instead of via entrypoints ([#8368](https://github.com/getsentry/sentry-javascript/issues/8368)) - fix(replay): Mark ui.slowClickDetected `clickCount` as optional ([#8376](https://github.com/getsentry/sentry-javascript/issues/8376)) - fix(serverless): Export `autoDiscoverNodePerformanceMonitoringIntegrations` from SDK ([#8382](https://github.com/getsentry/sentry-javascript/issues/8382)) - fix(sveltekit): Check for cached requests in client-side fetch instrumentation ([#8391](https://github.com/getsentry/sentry-javascript/issues/8391)) - fix(sveltekit): Only instrument SvelteKit `fetch` if the SDK client is valid ([#8381](https://github.com/getsentry/sentry-javascript/issues/8381)) - fix(tracing): Instrument Prisma client in constructor of integration ([#8383](https://github.com/getsentry/sentry-javascript/issues/8383)) - ref(replay): More graceful `sessionStorage` check ([#8394](https://github.com/getsentry/sentry-javascript/issues/8394)) - ref(replay): Remove circular dep in replay eventBuffer ([#8389](https://github.com/getsentry/sentry-javascript/issues/8389)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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 [Renovate Bot](https://github.com/renovatebot/renovate).

renovate added the

dependencies

label 2023-06-28 16:04:43 +00:00

renovate added 1 commit 2023-06-28 16:04:44 +00:00

fix(deps): update sentry-javascript monorepo to v7.57.0

continuous-integration/drone/pr Build is passing

Details

continuous-integration/drone/push Build is passing

Details

e5090b117f

frederick commented

2023-06-28 16:10:37 +00:00

Hi renovate!

Thank you for creating a PR!

I've deployed the changes of this PR on a preview environment under this URL: https://3644-renovate-sentry-javascript-monor--vikunja-frontend-preview.netlify.app

You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.

Have a nice day!

Beep boop, I'm a bot.

Hi renovate! Thank you for creating a PR! I've deployed the changes of this PR on a preview environment under this URL: https://3644-renovate-sentry-javascript-monor--vikunja-frontend-preview.netlify.app You can use this url to view the changes live and test them out. You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/. Have a nice day! > Beep boop, I'm a bot.

konrad merged commit e5090b117f into main

2023-06-28 16:54:31 +00:00

konrad deleted branch renovate/sentry-javascript-monorepo

2023-06-28 16:54:32 +00:00

This repo is archived. You cannot comment on pull requests.

No reviewers