Skip to content

Update dependency @sentry/node --> v8

FW Serviceworker requested to merge dependencies/sentry-node-8.x into main

This MR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/node (source) ^7.64.0 -> ^8.0.0 age adoption passing confidence

Release Notes

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

v8.15.0

Compare Source

  • feat(core): allow unregistering callback through on (#​11710)
  • feat(nestjs): Add function-level span decorator to nestjs (#​12721)
  • feat(otel): Export & use spanTimeInputToSeconds for otel span exporter (#​12699)
  • fix(core): Pass origin as referrer for lazyLoadIntegration (#​12766)
  • fix(deno): Publish from build directory (#​12773)
  • fix(hapi): Specify error channel to filter boom errors (#​12725)
  • fix(react): Revert back to jsxRuntime: 'classic' to prevent breaking react 17 (#​12775)
  • fix(tracing): Report dropped spans for transactions (#​12751)
  • ref(scope): Delete unused public getStack() (#​12737)

Work in this release was contributed by @​arturovt and @​jaulz. Thank you for your contributions!

v8.14.0

Compare Source

Important Changes
  • feat(nestjs): Filter 4xx errors (#​12695)

The @sentry/nestjs SDK no longer captures 4xx errors automatically.

Other Changes

Work in this release was contributed by @​quisido. Thank you for your contribution!

v8.13.0

Compare Source

Important Changes
  • feat(nestjs): Add Nest SDK This release adds a dedicated SDK for NestJS (@sentry/nestjs) in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (@sentry/node) supporting the same set of features. See the docs for how to use the SDK.
Other Changes

v8.12.0

Compare Source

Important Changes
  • feat(solid): Remove need to pass router hooks to solid integration (breaking)

This release introduces breaking changes to the @sentry/solid package (which is currently out in alpha).

We've made it easier to get started with the solid router integration by removing the need to pass use* hooks explicitly to solidRouterBrowserTracingIntegration. Import solidRouterBrowserTracingIntegration from @sentry/solid/solidrouter and add it to Sentry.init

import * as Sentry from '@​sentry/solid';
import { solidRouterBrowserTracingIntegration, withSentryRouterRouting } from '@​sentry/solid/solidrouter';
import { Router } from '@​solidjs/router';

Sentry.init({
  dsn: '__PUBLIC_DSN__',
  integrations: [solidRouterBrowserTracingIntegration()],
  tracesSampleRate: 1.0, //  Capture 100% of the transactions
});

const SentryRouter = withSentryRouterRouting(Router);
  • feat(core): Return client from init method (#​12585)

Sentry.init() now returns a client directly, so you don't need to explicitly call getClient() anymore:

const client = Sentry.init();
  • feat(nextjs): Add deleteSourcemapsAfterUpload option (#​12457)

This adds an easy way to delete sourcemaps immediately after uploading them:

module.exports = withSentryConfig(nextConfig, {
  sourcemaps: {
    deleteSourcemapsAfterUpload: true,
  },
});
  • feat(node): Allow to configure maxSpanWaitDuration (#​12610)

Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However, if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early. In this case, you can increase this duration to a value that fits your expected data.

Other Changes
  • feat(feedback): Extra check for iPad in screenshot support (#​12593)
  • fix(bundle): Ensure CDN bundles do not overwrite window.Sentry (#​12580)
  • fix(feedback): Inject preact from feedbackModal into feedbackScreenshot integration (#​12535)
  • fix(node): Re-throw errors from koa middleware (#​12609)
  • fix(remix): Mark isRemixV2 as optional in exposed types. (#​12614)
  • ref(node): Add error message to NodeFetch log (#​12612)

Work in this release was contributed by @​n4bb12. Thank you for your contribution!

v8.11.0

Compare Source

Important Changes
  • feat(core): Add parentSpan option to startSpan* APIs (#​12567)

We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to explicitly manage the parent-child relationship of your spans better.

Sentry.startSpan({ name: 'root' }, parent => {
  const span = Sentry.startInactiveSpan({ name: 'xxx', parentSpan: parent });

  Sentry.startSpan({ name: 'xxx', parentSpan: parent }, () => {});

  Sentry.startSpanManual({ name: 'xxx', parentSpan: parent }, () => {});
});
Other Changes
  • feat(node): Detect release from more providers (#​12529)
  • fix(profiling-node): Use correct getGlobalScope import (#​12564)
  • fix(profiling-node) sample timestamps need to be in seconds (#​12563)
  • ref: Align @sentry/node exports from framework SDKs. (#​12589)

v8.10.0

Compare Source

Important Changes
  • feat(remix): Migrate to opentelemetry-instrumentation-remix. (#​12110)

You can now simplify your remix instrumentation by opting-in like this:

const Sentry = require('@​sentry/remix');

Sentry.init({
  dsn: YOUR_DSN
  // opt-in to new auto instrumentation
  autoInstrumentRemix: true,
});

With this setup, you do not need to add e.g. wrapExpressCreateRequestHandler anymore. Additionally, the quality of the captured data improves. The old way to use @sentry/remix continues to work, but it is encouraged to use the new setup.

Other Changes
  • feat(browser): Export thirdPartyErrorFilterIntegration from @sentry/browser (#​12512)
  • feat(feedback): Allow passing tags field to any feedback config param (#​12197)
  • feat(feedback): Improve screenshot quality for retina displays (#​12487)
  • feat(feedback): Screenshots don't resize after cropping (#​12481)
  • feat(node) add max lineno and colno limits (#​12514)
  • feat(profiling) add global profile context while profiler is running (#​12394)
  • feat(react): Add React version to events (#​12390)
  • feat(replay): Add url to replay hydration error breadcrumb type (#​12521)
  • fix(core): Ensure standalone spans respect sampled flag (#​12533)
  • fix(core): Use maxValueLength in extra error data integration (#​12174)
  • fix(feedback): Fix scrolling after feedback submission (#​12499)
  • fix(feedback): Send feedback rejects invalid responses (#​12518)
  • fix(nextjs): Update @​rollup/plugin-commonjs (#​12527)
  • fix(node): Ensure status is correct for http server span errors (#​12477)
  • fix(node): UnifygetDynamicSamplingContextFromSpan (#​12522)
  • fix(profiling): continuous profile chunks should be in seconds (#​12532)
  • fix(remix): Add nativeFetch support for accessing request headers (#​12479)
  • fix(remix): Export no-op as captureRemixServerException from client SDK (#​12497)
  • ref(node) refactor contextlines to use readline (#​12221)

Work in this release was contributed by @​AndreyKovanov and @​kiliman. Thank you for your contributions!

v8.9.2

Compare Source

  • fix(profiling): Update exports so types generate properly (#​12469)

v8.9.1

Important changes
  • feat(solid): Add Solid SDK

    This release adds a dedicated SDK for Solid JS in alpha state with instrumentation for Solid Router and a custom ErrorBoundary. See the package README for how to use the SDK.

Other changes

Work in this release was contributed by @​soch4n. Thank you for your contribution!

v8.9.0

This release failed to publish correctly, please use 8.9.1 instead.

v8.8.0

Compare Source

  • feat: Upgrade OTEL dependencies (#​12388)

This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use import-in-the-middle v1.8.0. This should fix numerous issues with using OTEL instrumentation with ESM.

High level issues fixed with OTEL + ESM:

  • incompatibilities with using multiple loaders, commonly encountered while using tsx or similar libraries.
  • incompatibilities with libraries that use duplicate namespace exports like date-fns.
  • incompatibilities with libraries that use self-referencing namespace imports like openai.
  • incompatibilities with dynamic export patterns like exports with function calls.
  • ENOENT: no such file or directory bugs that libraries like discord.js surface.

If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.

  • deps: Bump Sentry bundler plugins to version 2.18.0 (#​12381)
  • feat: Add thirdPartyErrorFilterIntegration (#​12267)
  • feat(core): Filter out error events with exception values and no stacktraces, values, or types (#​12387)
  • feat(core): Ignore additional common but inactionable errors (#​12384)
  • feat(deps): Bump @​opentelemetry/propagator-aws-xray from 1.3.1 to 1.24.1 (#​12333)
  • feat(deps): Bump @​sentry/cli from 2.31.2 to 2.32.1 (#​12332)
  • feat(redis): Support mget command in caching functionality (#​12380)
  • feat(vercel-edge): Export core integrations from Vercel edge SDK (#​12308)
  • fix(browser): Fix idle span ending (#​12306)
  • fix(browser): Fix parenthesis parsing logic for chromium (#​12373)
  • fix(browser): Fix types export path for CJS (#​12305)
  • fix(feedback): Override TriggerLabel Option (#​12316)
  • fix(feedback): Wait for document to be ready before doing autoinject (#​12294)
  • fix(nextjs): Fix memory leak (#​12335)
  • fix(nextjs): Fix version detection and option insertion logic for clientTraceMetadata option (#​12323)
  • fix(nextjs): Update argument name in log message about sentry property on Next.js config object (#​12366)
  • fix(node): Do not manually finish / update root Hapi spans. (#​12287)
  • fix(node): Fix virtual parent span ID handling & update create-next-app E2E test (#​12368)
  • fix(node): Skip capturing Hapi Boom responses v8. (#​12288)
  • fix(performance): Fix LCP not getting picked up on initial pageload transaction by setting reportAllChanges to true (#​12360)
  • fix(replay): Avoid infinite loop of logs (#​12309)
  • fix(replay): Ignore old events when manually starting replay (#​12349)
  • ref(browser): Ensure idle span ending is consistent (#​12310)
  • ref(profiling): unref timer (#​12340)

Work in this release contributed by @​dohooo, @​mohd-akram, and @​ykzts. Thank you for your contributions!

v8.7.0

Important Changes
  • feat(react): Add TanStack Router integration (#​12095)

    This release adds instrumentation for TanStack router with a new tanstackRouterBrowserTracingIntegration in the @sentry/react SDK:

    import * as Sentry from '@​sentry/react';
    import { createRouter } from '@​tanstack/react-router';
    
    const router = createRouter({
      // Your router options...
    });
    
    Sentry.init({
      dsn: '___PUBLIC_DSN___',
      integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)],
      tracesSampleRate: 1.0,
    });
    
Other Changes
  • fix(nextjs): Do not hide sourceMappingURL comment on client when nextConfig.productionBrowserSourceMaps: true is set (#​12278)

v8.6.0

Important Changes
  • feat(metrics): Add timings method to metrics (#​12226)

    This introduces a new method, metrics.timing(), which can be used in two ways:

    1. With a numeric value, to simplify creating a distribution metric. This will default to second as unit:
    Sentry.metrics.timing('myMetric', 100);
    
    1. With a callback, which will wrap the duration of the callback. This can accept a sync or async callback. It will create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:
    const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction);
    
  • feat(react): Add Sentry.reactErrorHandler (#​12147)

    This MR introduces Sentry.reactErrorHandler, which you can use in React 19 as follows:

    import * as Sentry from '@​sentry/react';
    import { hydrateRoot } from 'react-dom/client';
    
    ReactDOM.hydrateRoot(
      document.getElementById('root'),
      <React.StrictMode>
        <App />
      </React.StrictMode>,
      {
        onUncaughtError: Sentry.reactErrorHandler(),
        onCaughtError: Sentry.reactErrorHandler((error, errorInfo) => {
          // optional callback if users want custom config.
        }),
      },
    );
    

    For more details, take a look at the MR. Our documentation will be updated soon!

Other Changes
  • feat(sveltekit): Add request data to server-side events (#​12254)
  • fix(core): Pass in cron monitor config correctly (#​12248)
  • fix(nextjs): Don't capture suspense errors in server components (#​12261)
  • fix(tracing): Ensure sent spans are limited to 1000 (#​12252)
  • ref(core): Use versioned carrier on global object (#​12206)

v8.5.0

Compare Source

Important Changes
  • feat(react): Add React 19 to peer deps (#​12207)

This release adds support for React 19 in the @sentry/react SDK package.

  • feat(node): Add @sentry/node/preload hook (#​12213)

This release adds a new way to initialize @sentry/node, which allows you to use the SDK with performance instrumentation even if you cannot call Sentry.init() at the very start of your app.

First, run the SDK like this:

node --require @&#8203;sentry/node/preload ./app.js

Now, you can initialize and import the rest of the SDK later or asynchronously:

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

const dsn = await getSentryDsn();
Sentry.init({ dsn });

For more details, head over to the MR Description of the new feature. Our docs will be updated soon with a new guide.

Other Changes
  • feat(browser): Do not include metrics in base CDN bundle (#​12230)
  • feat(core): Add startNewTrace API (#​12138)
  • feat(core): Allow to pass custom scope to captureFeedback() (#​12216)
  • feat(core): Only allow SerializedSession in session envelope items (#​11979)
  • feat(nextjs): Use Vercel's waitUntil to defer freezing of Vercel Lambdas (#​12133)
  • feat(node): Ensure manual OTEL setup works (#​12214)
  • fix(aws-serverless): Avoid minifying Module._resolveFilename in Lambda layer bundle (#​12232)
  • fix(aws-serverless): Ensure lambda layer uses default export from ImportInTheMiddle (#​12233)
  • fix(browser): Improve browser extension error message check (#​12146)
  • fix(browser): Remove optional chaining in INP code (#​12196)
  • fix(nextjs): Don't report React postpone errors (#​12194)
  • fix(nextjs): Use global scope for generic event filters (#​12205)
  • fix(node): Add origin to redis span (#​12201)
  • fix(node): Change import of @prisma/instrumentation to use default import (#​12185)
  • fix(node): Only import inspector asynchronously (#​12231)
  • fix(replay): Update matcher for hydration error detection to new React docs (#​12209)
  • ref(profiling-node): Add warning when using non-LTS node (#​12211)

v8.4.0

Compare Source

Important Changes
  • feat(nextjs): Trace pageloads in App Router (#​12157)

If you are using Next.js version 14.3.0-canary.64 or above, the Sentry Next.js SDK will now trace clientside pageloads with React Server Components. This means, that client-side errors like Error: An error occurred in the Server Components render., which previously didn't give you much information on how that error was caused, can now be traced back to a specific error in a server component.

  • feat(angular): Add Support for Angular 18 (#​12183)

This release guarantees support for Angular 18 with @sentry/angular.

Other Changes

v8.3.0

Compare Source

Important Changes
  • Better Node Framework Span Data

This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi.

When using Sentry in ESM mode, you can now use Sentry without manually calling init like this:

 SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --import=@&#8203;sentry/node/init app.mjs

When using CommonJS, you can do:

 SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --require=@&#8203;sentry/node/init app.js
Other Changes
  • chore: Align and update MIT license dates (#​12143)
  • chore: Resolve or postpone a random assortment of TODOs (#​11977)
  • doc(migration): Add entry for runWithAsyncContext (#​12153)
  • docs: Add migration docs to point out that default import does not work (#​12100)
  • docs(sveltekit): process.env.SENTRY_AUTH_TOKEN (#​12118)
  • feat(browser): Ensure browserProfilingIntegration is published to CDN (#​12158)
  • feat(google-cloud): Expose ESM build (#​12149)
  • feat(nextjs): Ignore Prisma critical dependency warnings (#​12144)
  • feat(node): Add app.free_memory info to events (#​12150)
  • feat(node): Do not create GraphQL resolver spans by default (#​12097)
  • feat(node): Use node: prefix for node built-ins (#​11895)
  • feat(replay): Use unwrapped setTimeout to avoid e.g. angular change detection (#​11924)
  • fix(core): Add dsn to span envelope header (#​12096)
  • fix(feedback): Improve feedback border color in dark-mode, and prevent auto-dark mode when a theme is picked (#​12126)
  • fix(feedback): Set optionOverrides to be optional in TS definition (#​12125)
  • fix(nextjs): Don't put undefined values in props (#​12131)
  • fix(nextjs): Fix legacy configuration method detection for emitting warning (#​12136)
  • fix(node): Ensure fetch/http breadcrumbs are created correctly (#​12137)
  • fix(node): Update @prisma/instrumentation from 5.13.0 to 5.14.0 (#​12081)
  • ref(node): Add log for running in ESM/CommonJS mode (#​12134)
  • ref(node): Handle failing hook registration gracefully (#​12135)
  • ref(node): Only show instrumentation warning when tracing is enabled (#​12141)

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

v8.2.1

Compare Source

  • fix(aws-serverless): Fix build of lambda layer (#​12083)
  • fix(nestjs): Broaden nest.js type (#​12076)

v8.2.0

Compare Source

  • feat(redis-cache): Create cache-span with prefixed keys (get/set commands) (#​12070)
  • feat(core): Add beforeSendSpan hook (#​11886)
  • feat(browser): Improve idle span handling (#​12065)
  • fix(node): Set transactionName for unsampled spans in httpIntegration (#​12071)
  • fix(core): Export Scope interface as Scope (#​12067)
  • fix(core): Avoid looking up client for hasTracingEnabled() if possible (#​12066)
  • fix(browser): Use consistent timestamps (#​12063)
  • fix(node): Fix check for performance integrations (#​12043)
  • ref(sveltekit): Warn to delete source maps if Sentry plugin enabled source maps generation (#​12072)

v8.1.0

Compare Source

This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we updated some initially missed points in our migration guides and documentation.

  • feat(aws-serverless): Fix tree-shaking for aws-serverless package (#​12017)
  • feat(node): Bump opentelemetry instrumentation to latest version (#​12028)
  • feat(scope): Bring back lastEventId on isolation scope (#​11951) (#​12022)
  • fix(aws-serverless): Export awslambda-auto
  • fix(node): Do not warn for missing instrumentation if SDK is disabled (#​12041)
  • fix(react): Set dependency-injected functions as early as possible (#​12019)
  • fix(react): Warn and fall back gracefully if dependency injected functions are not available (#​12026)
  • ref(core): Streamline parseSampleRate utility function (#​12024)
  • ref(feedback): Make eventId optional and use lastEventId in report dialog (#​12029)

v8.0.0

Compare Source

The Sentry JS SDK team is proud to announce the release of version 8.0.0 of Sentry's JavaScript SDKs - it's been a long time coming! Thanks to everyone for your patience and a special shout out to the brave souls testing preview builds and reporting issues - we appreciate your support!


How to Upgrade to Version 8:

We recommend reading the migration guide docs to find out how to address any breaking changes in your code for your specific platform or framework.

To automate upgrading to v8 as much as possible, use our migration codemod @sentry/migr8:

npx @&#8203;sentry/migr8@&#8203;latest

All deprecations from the v7 cycle, with the exception of getCurrentHub(), have been removed and can no longer be used in v8. If you have an advanced Sentry SDK setup, we additionally recommend reading the in-depth migration guide in our repo which highlights all changes with additional details and information.

The rest of this changelog highlights the most important (breaking) changes and links to more detailed information.

Version Support

With v8, we dropped support for several old runtimes and browsers

Node SDKs: The Sentry JavaScript SDK v8 now supports Node.js 14.8.0 or higher. This applies to @sentry/node and all of our node-based server-side sdks (@sentry/nextjs, @sentry/remix, etc.). Furthermore, version 8 now ships with full support for ESM-based node apps using Node.js 18.19.0 or higher.

Browser SDKs: The browser SDKs now require ES2018+ compatible browsers. New minimum browser versions:

  • Chrome 63
  • Edge 79
  • Safari/iOS Safari 12
  • Firefox 58
  • Opera 50
  • Samsung Internet 8.2

For more details, please see the version support section in our migration guide.

Initializing Server-side SDKs (Node, Bun, Deno, Serverless):

In v8, we support a lot more node-based packages than before. In order to ensure auto-instrumentation works, the SDK now needs to be imported and initialized before any other import in your code.

We recommend creating a new file (e.g. instrumentation.js) to import and initialize the SDK. Then, import the file on top of your entry file or detailed instructions, check our updated SDK setup docs initializing the SDK in v8.

Performance Monitoring Changes

The API around performance monitoring and tracing has been streamlined, and we've added support for more integrations out of the box.

Functional Integrations

Integrations are now simple functions instead of classes. Class-based integrations have been removed:

// old (v7)
Sentry.init({
  integrations: [new Sentry.BrowserTracing()],
});

// new (v8)
Sentry.init({
  integrations: [Sentry.browserTracingIntegration()],
});
Package removal

The following packages have been removed or replaced and will no longer be published:

Changes since 8.0.0-rc.3
  • feat(nextjs): Remove transpileClientSDK (#​11978)

    As we are dropping support for Internet Explorer 11 and other other older browser versions wih version 8.0.0, we are also removing the transpileClientSDK option from the Next.js SDK. If you need to support these browser versions, please configure Webpack and Next.js to down-compile the SDK.

  • feat(serverless): Do not include performance integrations by default (#​11998)

    To keep Lambda bundle size reasonable, the SDK no longer ships with all performance (database) integrations by default. Add the Sentry integrations of the databases and other tools you're using manually to your Sentry.init call by following this guide. Note that this change does not apply if you use the SDK with the Sentry AWS Lambda layer.

  • feat(feedback): Simplify public css configuration for feedback (#​11985)

  • fix(feedback): Check for empty user (#​11993)

  • fix(replay): Fix type for replayCanvasIntegration (#​11995)

  • fix(replay): Fix user activity not being updated in start() (#​12001)

v7.118.0

Compare Source

  • fix(v7/bundle): Ensure CDN bundles do not overwrite window.Sentry (#​12579)

Bundle size 📦

Path Size
@​sentry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped) 80.83 KB
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped) 71.77 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) - Webpack (gzipped) 76.02 KB
@​sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped) 65.38 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped) 35.64 KB
@​sentry/browser (incl. browserTracingIntegration) - Webpack (gzipped) 35.53 KB
@​sentry/browser (incl. Feedback) - Webpack (gzipped) 31.6 KB
@​sentry/browser (incl. sendFeedback) - Webpack (gzipped) 31.61 KB
@​sentry/browser - Webpack (gzipped) 22.78 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped) 79.05 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 70.38 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 36.06 KB
@​sentry/browser - ES6 CDN Bundle (gzipped) 25.29 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 221.51 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 109.1 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed) 75.83 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 39.34 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped) 72.27 KB
@​sentry/react - Webpack (gzipped) 22.81 KB
@​sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped) 90.03 KB
@​sentry/nextjs Client - Webpack (gzipped) 54.15 KB
@​sentry-internal/feedback - Webpack (gzipped) 17.34 KB

v7.117.0

Compare Source

  • feat(browser/v7): Publish browserprofling CDN bundle (#​12224)
  • fix(v7/publish): Add v7 tag to @sentry/replay (#​12304)

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 MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.


  • [ ] If you want to rebase/retry this MR, check this box
Edited by FW Serviceworker

Merge request reports

Loading