fix(deps): update sentry-javascript monorepo to v7.73.0 - autoclosed #3745

renovate · 2023-09-13T10:10:58Z

renovate commented

2023-09-13 10:10:58 +00:00

This PR contains the following updates:

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

Release Notes

getsentry/sentry-javascript (@sentry/tracing)

`v7.73.0`

Compare Source

Important Changes

feat(replay): Upgrade to rrweb2

This is fully backwards compatible with prior versions of the Replay SDK. The only breaking change that we will making is to not be masking aria-label by default. The reason for this change is to align with our core SDK which also does not mask aria-label. This change also enables better support of searching by clicks.

Another change that needs to be highlighted is the 13% bundle size increase. This bundle size increase is necessary to bring improved recording performance and improved replay fidelity, especially in regards to web components and iframes. We will be investigating the reduction of the bundle size in this PR.

Here are benchmarks comparing the version 1 of rrweb to version 2

metric	v1	v2
lcp	1486.06 ms	1529.11 ms
cls	0.40 ms	0.40 ms
fid	1.53 ms	1.50 ms
tbt	3207.22 ms	3036.80 ms
memoryAvg	131.83 MB	124.84 MB
memoryMax	324.8 MB	339.03 MB
netTx	282.67 KB	272.51 KB
netRx	8.02 MB	8.07 MB

Other Changes

feat: Always assemble Envelopes (#9101)
feat(node): Rate limit local variables for caught exceptions and enable captureAllExceptions by default (#9102)
fix(core): Ensure tunnel is considered for isSentryUrl checks (#9130)
fix(nextjs): Fix RequestAsyncStorage fallback path (#9126)
fix(node-otel): Suppress tracing for generated sentry spans (#9142)
fix(node): fill in span data from http request options object (#9112)
fix(node): Fixes and improvements to ANR detection (#9128)
fix(sveltekit): Avoid data invalidation in wrapped client-side load functions (#9071)
ref(core): Refactor InboundFilters integration to use processEvent (#9020)
ref(wasm): Refactor Wasm integration to use processEvent (#9019)

Work in this release contributed by @vlad-zhukov. Thank you for your contribution!

`v7.72.0`

Compare Source

Important Changes

feat(node): App Not Responding with stack traces (#9079)

This release introduces support for Application Not Responding (ANR) errors for Node.js applications.
These errors are triggered when the Node.js main thread event loop of an application is blocked for more than five seconds.
The Node SDK reports ANR errors as Sentry events and can optionally attach a stacktrace of the blocking code to the ANR event.

To enable ANR detection, import and use the enableANRDetection function from the @sentry/node package before you run the rest of your application code.
Any event loop blocking before calling enableANRDetection will not be detected by the SDK.

Example (ESM):

import * as Sentry from "@&#8203;sentry/node";

Sentry.init({
  dsn: "___PUBLIC_DSN___",
  tracesSampleRate: 1.0,
});

await Sentry.enableANRDetection({ captureStackTrace: true });
// Function that runs your app
runApp();

Example (CJS):

const Sentry = require("@&#8203;sentry/node");

Sentry.init({
  dsn: "___PUBLIC_DSN___",
  tracesSampleRate: 1.0,
});

Sentry.enableANRDetection({ captureStackTrace: true }).then(() => {
  // Function that runs your app
  runApp();
});

Other Changes

fix(nextjs): Filter RequestAsyncStorage locations by locations that webpack will resolve (#9114)
fix(replay): Ensure replay_id is not captured when session is expired (#9109)

`v7.71.0`

Compare Source

feat(bun): Instrument Bun.serve (#9080)
fix(core): Ensure global event processors are always applied to event (#9064)
fix(core): Run client eventProcessors before global ones (#9032)
fix(nextjs): Use webpack module paths to attempt to resolve internal request async storage module (#9100)
fix(react): Add actual error name to boundary error name (#9065)
fix(react): Compare location against basename-prefixed route. (#9076)
ref(browser): Refactor browser integrations to use processEvent (#9022)

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

`v7.70.0`

Compare Source

Important Changes

feat: Add Bun SDK (#9029)

This release contains the beta version of @sentry/bun, our SDK for the Bun JavaScript runtime! For details on how to use it, please see the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

Note that as of now the Bun runtime does not support global error handlers. This is being actively worked on, see the tracking issue in Bun's GitHub repo.

feat(remix): Add Remix 2.x release support. (#8940)

The Sentry Remix SDK now officially supports Remix v2! See our Remix docs for more details.

Other Changes

chore(node): Upgrade cookie to ^0.5.0 (#9013)
feat(core): Introduce processEvent hook on Integration (#9017)
feat(node): Improve non-error messages (#9026)
feat(vercel-edge): Add Vercel Edge Runtime package (#9041)
fix(remix): Use React.ComponentType instead of React.FC as withSentry's generic type. (#9043)
fix(replay): Ensure replay events go through preprocessEvent hook (#9034)
fix(replay): Fix typo in Replay types (#9028)
fix(sveltekit): Adjust handleErrorWithSentry type (#9054)
fix(utils): Try-catch monkeypatching to handle frozen objects/functions (#9031)

Work in this release contributed by @Dima-Dim, @krist7599555 and @lifeiscontent. Thank you for your contributions!

Special thanks for @isaacharrisholt for helping us implement a Vercel Edge Runtime SDK which we use under the hood for our Next.js SDK.

`v7.69.0`

Compare Source

Important Changes

New Performance APIs
- feat: Update span performance API names (#8971)
- feat(core): Introduce startSpanManual (#8913)

This release introduces a new set of top level APIs for the Performance Monitoring SDKs. These aim to simplify creating spans and reduce the boilerplate needed for performance instrumentation. The three new methods introduced are Sentry.startSpan, Sentry.startInactiveSpan, and Sentry.startSpanManual. These methods are available in the browser and node SDKs.

Sentry.startSpan wraps a callback in a span. The span is automatically finished when the callback returns. This is the recommended way to create spans.

// Start a span that tracks the duration of expensiveFunction
const result = Sentry.startSpan({ name: 'important function' }, () => {
  return expensiveFunction();
});

// You can also mutate the span wrapping the callback to set data or status
Sentry.startSpan({ name: 'important function' }, (span) => {
  // span is undefined if performance monitoring is turned off or if
  // the span was not sampled. This is done to reduce overhead.
  span?.setData('version', '1.0.0');
  return expensiveFunction();
});

If you don't want the span to finish when the callback returns, use Sentry.startSpanManual to control when the span is finished. This is useful for event emitters or similar.

// Start a span that tracks the duration of middleware
function middleware(_req, res, next) {
  return Sentry.startSpanManual({ name: 'middleware' }, (span, finish) => {
    res.once('finish', () => {
      span?.setHttpStatus(res.status);
      finish();
    });
    return next();
  });
}

Sentry.startSpan and Sentry.startSpanManual create a span and make it active for the duration of the callback. Any spans created while this active span is running will be added as a child span to it. If you want to create a span without making it active, use Sentry.startInactiveSpan. This is useful for creating parallel spans that are not related to each other.

const span1 = Sentry.startInactiveSpan({ name: 'span1' });

someWork();

const span2 = Sentry.startInactiveSpan({ name: 'span2' });

moreWork();

const span3 = Sentry.startInactiveSpan({ name: 'span3' });

evenMoreWork();

span1?.finish();
span2?.finish();
span3?.finish();

Other Changes

feat(core): Export BeforeFinishCallback type (#8999)
build(eslint): Enforce that ts-expect-error is used (#8987)
feat(integration): Ensure LinkedErrors integration runs before all event processors (#8956)
feat(node-experimental): Keep breadcrumbs on transaction (#8967)
feat(redux): Add 'attachReduxState' option (#8953)
feat(remix): Accept org, project and url as args to upload script (#8985)
fix(utils): Prevent iterating over VueViewModel (#8981)
fix(utils): uuidv4 fix for cloudflare (#8968)
fix(core): Always use event message and exception values for ignoreErrors (#8986)
fix(nextjs): Add new potential location for Next.js request AsyncLocalStorage (#9006)
fix(node-experimental): Ensure we only create HTTP spans when outgoing (#8966)
fix(node-experimental): Ignore OPTIONS & HEAD requests (#9001)
fix(node-experimental): Ignore outgoing Sentry requests (#8994)
fix(node-experimental): Require parent span for pg spans (#8993)
fix(node-experimental): Use Sentry logger as Otel logger (#8960)
fix(node-otel): Refactor OTEL span reference cleanup (#9000)
fix(react): Switch to props in useRoutes (#8998)
fix(remix): Add glob to Remix SDK dependencies. (#8963)
fix(replay): Ensure handleRecordingEmit aborts when event is not added (#8938)
fix(replay): Fully stop & restart session when it expires (#8834)

Work in this release contributed by @Duncanxyz and @malay44. Thank you for your contributions!

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.68.0` -> `7.73.0`](https://renovatebot.com/diffs/npm/@sentry%2ftracing/7.68.0/7.73.0) | | [@sentry/vue](https://github.com/getsentry/sentry-javascript/tree/master/packages/vue) ([source](https://github.com/getsentry/sentry-javascript)) | dependencies | minor | [`7.68.0` -> `7.73.0`](https://renovatebot.com/diffs/npm/@sentry%2fvue/7.68.0/7.73.0) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/tracing)</summary> ### [`v7.73.0`](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#7730) [Compare Source](https://github.com/getsentry/sentry-javascript/compare/7.72.0...7.73.0) ##### Important Changes - **feat(replay): Upgrade to rrweb2** This is fully backwards compatible with prior versions of the Replay SDK. The only breaking change that we will making is to not be masking `aria-label` by default. The reason for this change is to align with our core SDK which also does not mask `aria-label`. This change also enables better support of searching by clicks. Another change that needs to be highlighted is the 13% bundle size increase. This bundle size increase is necessary to bring improved recording performance and improved replay fidelity, especially in regards to web components and iframes. We will be investigating the reduction of the bundle size in [this PR](https://github.com/getsentry/sentry-javascript/issues/8815). Here are benchmarks comparing the version 1 of rrweb to version 2 | metric | v1 | v2 | | --------- | ---------- | ---------- | | lcp | 1486.06 ms | 1529.11 ms | | cls | 0.40 ms | 0.40 ms | | fid | 1.53 ms | 1.50 ms | | tbt | 3207.22 ms | 3036.80 ms | | memoryAvg | 131.83 MB | 124.84 MB | | memoryMax | 324.8 MB | 339.03 MB | | netTx | 282.67 KB | 272.51 KB | | netRx | 8.02 MB | 8.07 MB | ##### Other Changes - feat: Always assemble Envelopes ([#9101](https://github.com/getsentry/sentry-javascript/issues/9101)) - feat(node): Rate limit local variables for caught exceptions and enable `captureAllExceptions` by default ([#9102](https://github.com/getsentry/sentry-javascript/issues/9102)) - fix(core): Ensure `tunnel` is considered for `isSentryUrl` checks ([#9130](https://github.com/getsentry/sentry-javascript/issues/9130)) - fix(nextjs): Fix `RequestAsyncStorage` fallback path ([#9126](https://github.com/getsentry/sentry-javascript/issues/9126)) - fix(node-otel): Suppress tracing for generated sentry spans ([#9142](https://github.com/getsentry/sentry-javascript/issues/9142)) - fix(node): fill in span data from http request options object ([#9112](https://github.com/getsentry/sentry-javascript/issues/9112)) - fix(node): Fixes and improvements to ANR detection ([#9128](https://github.com/getsentry/sentry-javascript/issues/9128)) - fix(sveltekit): Avoid data invalidation in wrapped client-side `load` functions ([#9071](https://github.com/getsentry/sentry-javascript/issues/9071)) - ref(core): Refactor `InboundFilters` integration to use `processEvent` ([#9020](https://github.com/getsentry/sentry-javascript/issues/9020)) - ref(wasm): Refactor Wasm integration to use `processEvent` ([#9019](https://github.com/getsentry/sentry-javascript/issues/9019)) Work in this release contributed by [@vlad-zhukov](https://github.com/vlad-zhukov). Thank you for your contribution! ### [`v7.72.0`](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#7720) [Compare Source](https://github.com/getsentry/sentry-javascript/compare/7.71.0...7.72.0) ##### Important Changes - **feat(node): App Not Responding with stack traces ([#9079](https://github.com/getsentry/sentry-javascript/issues/9079))** This release introduces support for Application Not Responding (ANR) errors for Node.js applications. These errors are triggered when the Node.js main thread event loop of an application is blocked for more than five seconds. The Node SDK reports ANR errors as Sentry events and can optionally attach a stacktrace of the blocking code to the ANR event. To enable ANR detection, import and use the `enableANRDetection` function from the `@sentry/node` package before you run the rest of your application code. Any event loop blocking before calling `enableANRDetection` will not be detected by the SDK. Example (ESM): ```ts import * as Sentry from "@sentry/node"; Sentry.init({ dsn: "___PUBLIC_DSN___", tracesSampleRate: 1.0, }); await Sentry.enableANRDetection({ captureStackTrace: true }); // Function that runs your app runApp(); ``` Example (CJS): ```ts const Sentry = require("@sentry/node"); Sentry.init({ dsn: "___PUBLIC_DSN___", tracesSampleRate: 1.0, }); Sentry.enableANRDetection({ captureStackTrace: true }).then(() => { // Function that runs your app runApp(); }); ``` ##### Other Changes - fix(nextjs): Filter `RequestAsyncStorage` locations by locations that webpack will resolve ([#9114](https://github.com/getsentry/sentry-javascript/issues/9114)) - fix(replay): Ensure `replay_id` is not captured when session is expired ([#9109](https://github.com/getsentry/sentry-javascript/issues/9109)) ### [`v7.71.0`](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#7710) [Compare Source](https://github.com/getsentry/sentry-javascript/compare/7.70.0...7.71.0) - feat(bun): Instrument Bun.serve ([#9080](https://github.com/getsentry/sentry-javascript/issues/9080)) - fix(core): Ensure global event processors are always applied to event ([#9064](https://github.com/getsentry/sentry-javascript/issues/9064)) - fix(core): Run client eventProcessors before global ones ([#9032](https://github.com/getsentry/sentry-javascript/issues/9032)) - fix(nextjs): Use webpack module paths to attempt to resolve internal request async storage module ([#9100](https://github.com/getsentry/sentry-javascript/issues/9100)) - fix(react): Add actual error name to boundary error name ([#9065](https://github.com/getsentry/sentry-javascript/issues/9065)) - fix(react): Compare location against `basename`-prefixed route. ([#9076](https://github.com/getsentry/sentry-javascript/issues/9076)) - ref(browser): Refactor browser integrations to use `processEvent` ([#9022](https://github.com/getsentry/sentry-javascript/issues/9022)) Work in this release contributed by [@jorrit](https://github.com/jorrit). Thank you for your contribution! ### [`v7.70.0`](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#7700) [Compare Source](https://github.com/getsentry/sentry-javascript/compare/7.69.0...7.70.0) ##### Important Changes - **feat: Add Bun SDK ([#9029](https://github.com/getsentry/sentry-javascript/issues/9029))** This release contains the beta version of `@sentry/bun`, our SDK for the [Bun JavaScript runtime](https://bun.sh/)! For details on how to use it, please see the [README](./packages/bun/README.md). Any feedback/bug reports are greatly appreciated, please [reach out on GitHub](https://github.com/getsentry/sentry-javascript/discussions/7979). Note that as of now the Bun runtime does not support global error handlers. This is being actively worked on, see [the tracking issue in Bun's GitHub repo](https://github.com/oven-sh/bun/issues/5091). - **feat(remix): Add Remix 2.x release support. ([#8940](https://github.com/getsentry/sentry-javascript/issues/8940))** The Sentry Remix SDK now officially supports Remix v2! See [our Remix docs for more details](https://docs.sentry.io/platforms/javascript/guides/remix/). ##### Other Changes - chore(node): Upgrade cookie to ^0.5.0 ([#9013](https://github.com/getsentry/sentry-javascript/issues/9013)) - feat(core): Introduce `processEvent` hook on `Integration` ([#9017](https://github.com/getsentry/sentry-javascript/issues/9017)) - feat(node): Improve non-error messages ([#9026](https://github.com/getsentry/sentry-javascript/issues/9026)) - feat(vercel-edge): Add Vercel Edge Runtime package ([#9041](https://github.com/getsentry/sentry-javascript/issues/9041)) - fix(remix): Use `React.ComponentType` instead of `React.FC` as `withSentry`'s generic type. ([#9043](https://github.com/getsentry/sentry-javascript/issues/9043)) - fix(replay): Ensure replay events go through `preprocessEvent` hook ([#9034](https://github.com/getsentry/sentry-javascript/issues/9034)) - fix(replay): Fix typo in Replay types ([#9028](https://github.com/getsentry/sentry-javascript/issues/9028)) - fix(sveltekit): Adjust `handleErrorWithSentry` type ([#9054](https://github.com/getsentry/sentry-javascript/issues/9054)) - fix(utils): Try-catch monkeypatching to handle frozen objects/functions ([#9031](https://github.com/getsentry/sentry-javascript/issues/9031)) Work in this release contributed by [@Dima-Dim](https://github.com/Dima-Dim), [@krist7599555](https://github.com/krist7599555) and [@lifeiscontent](https://github.com/lifeiscontent). Thank you for your contributions! Special thanks for [@isaacharrisholt](https://github.com/isaacharrisholt) for helping us implement a Vercel Edge Runtime SDK which we use under the hood for our Next.js SDK. ### [`v7.69.0`](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#7690) [Compare Source](https://github.com/getsentry/sentry-javascript/compare/7.68.0...7.69.0) ##### Important Changes - **New Performance APIs** - feat: Update span performance API names ([#8971](https://github.com/getsentry/sentry-javascript/issues/8971)) - feat(core): Introduce startSpanManual ([#8913](https://github.com/getsentry/sentry-javascript/issues/8913)) This release introduces a new set of top level APIs for the Performance Monitoring SDKs. These aim to simplify creating spans and reduce the boilerplate needed for performance instrumentation. The three new methods introduced are `Sentry.startSpan`, `Sentry.startInactiveSpan`, and `Sentry.startSpanManual`. These methods are available in the browser and node SDKs. `Sentry.startSpan` wraps a callback in a span. The span is automatically finished when the callback returns. This is the recommended way to create spans. ```js // Start a span that tracks the duration of expensiveFunction const result = Sentry.startSpan({ name: 'important function' }, () => { return expensiveFunction(); }); // You can also mutate the span wrapping the callback to set data or status Sentry.startSpan({ name: 'important function' }, (span) => { // span is undefined if performance monitoring is turned off or if // the span was not sampled. This is done to reduce overhead. span?.setData('version', '1.0.0'); return expensiveFunction(); }); ``` If you don't want the span to finish when the callback returns, use `Sentry.startSpanManual` to control when the span is finished. This is useful for event emitters or similar. ```js // Start a span that tracks the duration of middleware function middleware(_req, res, next) { return Sentry.startSpanManual({ name: 'middleware' }, (span, finish) => { res.once('finish', () => { span?.setHttpStatus(res.status); finish(); }); return next(); }); } ``` `Sentry.startSpan` and `Sentry.startSpanManual` create a span and make it active for the duration of the callback. Any spans created while this active span is running will be added as a child span to it. If you want to create a span without making it active, use `Sentry.startInactiveSpan`. This is useful for creating parallel spans that are not related to each other. ```js const span1 = Sentry.startInactiveSpan({ name: 'span1' }); someWork(); const span2 = Sentry.startInactiveSpan({ name: 'span2' }); moreWork(); const span3 = Sentry.startInactiveSpan({ name: 'span3' }); evenMoreWork(); span1?.finish(); span2?.finish(); span3?.finish(); ``` ##### Other Changes - feat(core): Export `BeforeFinishCallback` type ([#8999](https://github.com/getsentry/sentry-javascript/issues/8999)) - build(eslint): Enforce that ts-expect-error is used ([#8987](https://github.com/getsentry/sentry-javascript/issues/8987)) - feat(integration): Ensure `LinkedErrors` integration runs before all event processors ([#8956](https://github.com/getsentry/sentry-javascript/issues/8956)) - feat(node-experimental): Keep breadcrumbs on transaction ([#8967](https://github.com/getsentry/sentry-javascript/issues/8967)) - feat(redux): Add 'attachReduxState' option ([#8953](https://github.com/getsentry/sentry-javascript/issues/8953)) - feat(remix): Accept `org`, `project` and `url` as args to upload script ([#8985](https://github.com/getsentry/sentry-javascript/issues/8985)) - fix(utils): Prevent iterating over VueViewModel ([#8981](https://github.com/getsentry/sentry-javascript/issues/8981)) - fix(utils): uuidv4 fix for cloudflare ([#8968](https://github.com/getsentry/sentry-javascript/issues/8968)) - fix(core): Always use event message and exception values for `ignoreErrors` ([#8986](https://github.com/getsentry/sentry-javascript/issues/8986)) - fix(nextjs): Add new potential location for Next.js request AsyncLocalStorage ([#9006](https://github.com/getsentry/sentry-javascript/issues/9006)) - fix(node-experimental): Ensure we only create HTTP spans when outgoing ([#8966](https://github.com/getsentry/sentry-javascript/issues/8966)) - fix(node-experimental): Ignore OPTIONS & HEAD requests ([#9001](https://github.com/getsentry/sentry-javascript/issues/9001)) - fix(node-experimental): Ignore outgoing Sentry requests ([#8994](https://github.com/getsentry/sentry-javascript/issues/8994)) - fix(node-experimental): Require parent span for `pg` spans ([#8993](https://github.com/getsentry/sentry-javascript/issues/8993)) - fix(node-experimental): Use Sentry logger as Otel logger ([#8960](https://github.com/getsentry/sentry-javascript/issues/8960)) - fix(node-otel): Refactor OTEL span reference cleanup ([#9000](https://github.com/getsentry/sentry-javascript/issues/9000)) - fix(react): Switch to props in `useRoutes` ([#8998](https://github.com/getsentry/sentry-javascript/issues/8998)) - fix(remix): Add `glob` to Remix SDK dependencies. ([#8963](https://github.com/getsentry/sentry-javascript/issues/8963)) - fix(replay): Ensure `handleRecordingEmit` aborts when event is not added ([#8938](https://github.com/getsentry/sentry-javascript/issues/8938)) - fix(replay): Fully stop & restart session when it expires ([#8834](https://github.com/getsentry/sentry-javascript/issues/8834)) Work in this release contributed by [@Duncanxyz](https://github.com/Duncanxyz) and [@malay44](https://github.com/malay44). Thank you for your contributions! </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-09-13 10:10:58 +00:00

renovate force-pushed renovate/sentry-javascript-monorepo from 7d07779280 to 8c4895e604

2023-09-20 12:12:33 +00:00

Compare

renovate changed title from ~~fix(deps): update sentry-javascript monorepo to v7.69.0~~ to fix(deps): update sentry-javascript monorepo to v7.70.0

2023-09-20 12:12:35 +00:00

renovate changed title from ~~fix(deps): update sentry-javascript monorepo to v7.70.0~~ to fix(deps): update sentry-javascript monorepo to v7.71.0

2023-09-25 15:12:06 +00:00

renovate force-pushed renovate/sentry-javascript-monorepo from 8c4895e604 to 61c785d415

2023-09-25 15:12:32 +00:00

Compare

renovate force-pushed renovate/sentry-javascript-monorepo from 61c785d415 to af740c45f9

2023-09-26 18:10:54 +00:00

Compare

renovate changed title from ~~fix(deps): update sentry-javascript monorepo to v7.71.0~~ to fix(deps): update sentry-javascript monorepo to v7.72.0

2023-09-26 18:10:58 +00:00

renovate force-pushed renovate/sentry-javascript-monorepo from af740c45f9 to c2c563c636

2023-10-02 12:08:51 +00:00

Compare

renovate changed title from ~~fix(deps): update sentry-javascript monorepo to v7.72.0~~ to fix(deps): update sentry-javascript monorepo to v7.73.0

2023-10-02 12:08:54 +00:00

renovate changed title from ~~fix(deps): update sentry-javascript monorepo to v7.73.0~~ to fix(deps): update sentry-javascript monorepo to v7.73.0 - autoclosed

2023-10-03 13:13:10 +00:00

renovate closed this pull request

2023-10-03 13:13:10 +00:00

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

No reviewers