Skip to content
This repository was archived by the owner on Jul 11, 2024. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 24, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@sentry/node (source) 6.9.0 -> 8.17.0 age adoption passing confidence dependencies major
@types/i18next-fs-backend (source) 1.0.1 -> 1.1.5 age adoption passing confidence devDependencies minor
@types/jest (source) 26.0.24 -> 29.5.12 age adoption passing confidence devDependencies major
actions/checkout v2 -> v4 age adoption passing confidence action major
canvas 2.8.0 -> 2.11.2 age adoption passing confidence dependencies minor
chalk ^4.1.0 -> ^5.0.0 age adoption passing confidence dependencies major
discord.js (source) 12.5.3 -> 14.15.3 age adoption passing confidence dependencies major
dotenv 10.0.0 -> 16.4.5 age adoption passing confidence dependencies major
eslint (source) 7.31.0 -> 9.6.0 age adoption passing confidence devDependencies major
i18next (source) 20.3.4 -> 23.11.5 age adoption passing confidence dependencies major
i18next-fs-backend 1.1.5 -> 2.3.1 age adoption passing confidence dependencies major
jest (source) 27.0.6 -> 29.7.0 age adoption passing confidence devDependencies major
lerna (source) 4.0.0 -> 8.1.6 age adoption passing confidence devDependencies major
moment (source) 2.29.4 -> 2.30.1 age adoption passing confidence dependencies minor
prettier (source) 2.3.2 -> 3.3.2 age adoption passing confidence devDependencies major
reflect-metadata (source) 0.1.13 -> 0.2.2 age adoption passing confidence dependencies minor
rimraf 3.0.2 -> 6.0.1 age adoption passing confidence devDependencies major
ts-jest (source) 27.0.3 -> 29.2.2 age adoption passing confidence devDependencies major
ts-node-dev 1.1.8 -> 2.0.0 age adoption passing confidence devDependencies major
tsconfig-paths 3.10.1 -> 4.2.0 age adoption passing confidence devDependencies major
tsyringe 4.6.0 -> 4.8.0 age adoption passing confidence dependencies minor
typescript (source) 4.3.5 -> 5.5.3 age adoption passing confidence devDependencies major
webfactory/ssh-agent v0.5.4 -> v0.9.0 age adoption passing confidence action minor

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

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

v8.17.0

Compare Source

  • feat: Upgrade OTEL deps (#​12809)
  • fix(nuxt): Add module to build:transpile script (#​12843)
  • fix(browser): Allow SDK initialization in NW.js apps (#​12846)

v8.16.0

Compare Source

Important Changes
  • feat(nextjs): Use spans generated by Next.js for App Router (#​12729)

Previously, the @sentry/nextjs SDK automatically recorded spans in the form of transactions for each of your top-level
server components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have
a root span, and more importantly, if you had data stream to the client, its duration was not captured because the
server component spans had finished before the data could finish streaming.

With this release, we will capture the duration of App Router requests in their entirety as a single transaction with
server component spans being descendants of that transaction. This means you will get more data that is also more
accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it
has before.

Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no
longer receive server component transactions like Page Server Component (/path/to/route) (unless using the Edge
runtime), and you will instead receive transactions for your App Router SSR requests that look like
GET /path/to/route.

If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.

  • - feat(nestjs): Add nest cron monitoring support (#​12781)

The @sentry/nestjs SDK now includes a @SentryCron decorator that can be used to augment the native NestJS @Cron
decorator to send check-ins to Sentry before and after each cron job run:

import { Cron } from '@​nestjs/schedule';
import { SentryCron, MonitorConfig } from '@​sentry/nestjs';
import type { MonitorConfig } from '@​sentry/types';

const monitorConfig: MonitorConfig = {
  schedule: {
    type: 'crontab',
    value: '* * * * *',
  },
  checkinMargin: 2, // In minutes. Optional.
  maxRuntime: 10, // In minutes. Optional.
  timezone: 'America/Los_Angeles', // Optional.
};

export class MyCronService {
  @​Cron('* * * * *')
  @​SentryCron('my-monitor-slug', monitorConfig)
  handleCron() {
    // Your cron job logic here
  }
}
Other Changes
  • feat(node): Allow to pass instrumentation config to httpIntegration (#​12761)
  • feat(nuxt): Add server error hook (#​12796)
  • feat(nuxt): Inject sentry config with Nuxt addPluginTemplate (#​12760)
  • fix: Apply stack frame metadata before event processors (#​12799)
  • fix(feedback): Add missing h import in ScreenshotEditor (#​12784)
  • fix(node): Ensure autoSessionTracking is enabled by default (#​12790)
  • ref(feedback): Let CropCorner inherit the existing h prop (#​12814)
  • ref(otel): Ensure we never swallow args for ContextManager (#​12798)

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)

Bundle size 📦

Path Size
@​sentry/browser 22.22 KB
@​sentry/browser (incl. Tracing) 33.31 KB
@​sentry/browser (incl. Tracing, Replay) 69.09 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 62.41 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 73.14 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 85.31 KB
@​sentry/browser (incl. Tracing, Replay, Feedback, metrics) 87.17 KB
@​sentry/browser (incl. metrics) 26.5 KB
@​sentry/browser (incl. Feedback) 38.42 KB
@​sentry/browser (incl. sendFeedback) 26.85 KB
@​sentry/browser (incl. FeedbackAsync) 31.42 KB
@​sentry/react 24.96 KB
@​sentry/react (incl. Tracing) 36.35 KB
@​sentry/vue 26.32 KB
@​sentry/vue (incl. Tracing) 35.16 KB
@​sentry/svelte 22.35 KB
CDN Bundle 23.41 KB
CDN Bundle (incl. Tracing) 35.04 KB
CDN Bundle (incl. Tracing, Replay) 69.17 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 74.34 KB
CDN Bundle - uncompressed 68.76 KB
CDN Bundle (incl. Tracing) - uncompressed 103.61 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 214.08 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 226.67 KB
@​sentry/nextjs (client) 36.23 KB
@​sentry/sveltekit (client) 33.95 KB
@​sentry/node 112.99 KB
@​sentry/node - without tracing 90.4 KB
@​sentry/aws-serverless 99.48 KB

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)

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 PR 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 PR. 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
PR 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://examplePu

</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.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/kaelorg/client).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzMi4yMDIuNCIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoiZGV2In0=-->

@renovate renovate bot requested review from KaelBot and pablo1v as code owners July 24, 2021 23:41
@renovate renovate bot changed the title chore(deps): update dependency @sentry/node to v6.10.0 chore(deps): update all dependencies (minor) Jul 30, 2021
@renovate renovate bot force-pushed the renovate/all branch 7 times, most recently from 97f8df7 to b01fba8 Compare August 13, 2021 00:17
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 7f6cd8b to 56c43d4 Compare August 31, 2021 16:07
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from e9e181e to 9d9eab4 Compare September 8, 2021 09:18
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from bab59e3 to 3717d9e Compare September 13, 2021 15:06
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 081a7c1 to 9c1bfb7 Compare September 20, 2021 19:13
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 59ce6c2 to e45aa51 Compare June 7, 2024 10:13
@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from 92f006f to 91f7790 Compare June 16, 2024 16:48
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 1c6fc74 to 76d52a4 Compare June 25, 2024 11:19
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 259ff37 to cc95ff4 Compare July 4, 2024 10:25
@renovate renovate bot force-pushed the renovate/all branch 8 times, most recently from e3c7a57 to f6fbff0 Compare July 10, 2024 13:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant