Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nuxt/icon	1.4.5 -> 1.5.1
@nuxtjs/supabase	1.3.5 -> 1.4.0
@supabase/realtime-js	2.10.2 -> 2.10.6
@total-typescript/ts-reset (source)	0.5.1 -> 0.6.1
@types/node (source)	20.14.15 -> 20.16.5
@vercel/speed-insights (source)	1.0.10 -> 1.0.12
@vite-pwa/nuxt	0.9.1 -> 0.10.5
esbuild	0.23.0 -> 0.24.0
nuxt (source)	3.12.4 -> 3.13.2
nuxt-security (source)	2.0.0-rc.9 -> 2.0.0
ofetch	1.3.4 -> 1.4.0
pino (source)	9.3.2 -> 9.4.0
pino-http	10.2.0 -> 10.3.0
pnpm (source)	9.7.0 -> 9.11.0
typescript (source)	5.3.3 -> 5.6.2
vue (source)	3.4.37 -> 3.5.7
vue-tsc (source)	2.0.29 -> 2.1.6

---

Release Notes

nuxt/icon (@​nuxt/icon)

v1.5.1

Compare Source

• fix: remove i- prefix in clientBundle.icons automatically (ef77a4f)
• chore: update deps (c8850af)
• fix: import server utils from #imports (#​249) (76b9ec4)
• docs: corretc jsdocs, close #​247, close #​248 (840fb5d)
• docs: fix typos (#​246) (8d72560)

v1.5.0

Compare Source

• feat: introduce clientBundle.scan (#​243) (bad9e0d)
• chore: update deps (1b81fab)

v1.4.10

Compare Source

• fix: correct cache key (19fd5cd)

v1.4.9

Compare Source

• chore: improve caching key for api route (0aa42c9)
• chore: fix lint (49721d2)

v1.4.8

Compare Source

• fix: Promise.race logic (de721b2)
• fix: use onServerPrefetch for css icons (7560ffe)
• fix: improve ssr performance for loading bad ids, add fetchTimeout option (3d07357)
• chore: setup nuxt hub for the playground (e6c87b5)
• chore: update deps (23d9ebd)

v1.4.7

Compare Source

• fix: serverBundle mode detection with NuxtHub (341e6e5)

v1.4.6

Compare Source

• fix: improve serverBundle preset detection (486ae5d)
• chore: update ci (9f9c1f4)
• docs: setup test for playground, close #​197 (5724416)
• chore: rename variables (f116b7c)
• fix: error when customize is provided in module options instead of app config (3bb5957)
• fix: add option customize to app.config and nuxt.config (#​238) (0accdcb)
• docs: fix customize function file to app.config.ts (#​237) (f4b135b)
• refactor: simplify client bundle codegen (2ef7a74)
• docs: use of the customize option (#​232) (91acea7)

nuxt-community/supabase-module (@​nuxtjs/supabase)

v1.4.0

Compare Source

Bug Fixes

• types: add explicit type annotations for plugins (#​408) (09bff84)
• types: add explicit types for composables & remove baseUrl from tsconfig (#​404) (596ece2)
• types: nullable composable types (#​407) (cbbfd86)

Features

• client: add retries to fetch (#​382) (98ca959)

1.3.5 (2024-07-15)

Bug Fixes

• types: generate (671295a)

1.3.4 (2024-07-10)

1.3.3 (2024-07-10)

Bug Fixes

• vite: optimize order (663bd73)

1.3.2 (2024-07-05)

Bug Fixes

• vite: optimize postgrest (2a6d91a)

Features

• ci: nightly (298e608)

1.3.1 (2024-07-05)

Features

• types: automatically pass database typings to clients (#​366) (132307a)

supabase/realtime-js (@​supabase/realtime-js)

v2.10.6

Compare Source

Bug Fixes

• Remove Module type from package.json (#​425) (0189a69)

v2.10.5

Compare Source

Bug Fixes

• Add type to system messages (#​422) (c1b27e1)

v2.10.4

Compare Source

Bug Fixes

• Broadcast endpoint includes private param in request body (#​414) (3058d0f)

v2.10.3

Compare Source

Bug Fixes

• Update dependencies (#​413) (176623d)

total-typescript/ts-reset (@​total-typescript/ts-reset)

v0.6.1

Patch Changes

• 757be40: Fixed a bug where creating an empty map would no longer infer types correctly.

v0.6.0

Minor Changes

• 6574858: Added a rule, /map-constructor, to default Map to Map<unknown, unknown> when no arguments are passed to the constructor.

  Before, you'd get any for both key and value types. Now, the result of Map.get is unknown instead of any:

  const userMap = new Map();
  
  const value = userMap.get("matt"); // value: unknown

  This now is part of the recommended rules.

• 5bf3a15: Added a rule, /promise-catch, to change the catch method to take unknown instead of any as an argument.

  const promise = Promise.reject("error");
  
  // BEFORE
  
  promise.catch((error) => {
    console.error(error); // error is any!
  });
  
  // AFTER
  
  promise.catch((error) => {
    console.error(error); // error is unknown!
  });

Patch Changes

• 53cee4f: author: @​none23

  Fixed a bug where running .filter on a union of arrays would not work.

vercel/speed-insights (@​vercel/speed-insights)

v1.0.12

Compare Source

What's Changed

• fix(#​56,#​72): useSearchParams might return null and break script insertion by @​feugy in https://github.com/vercel/speed-insights/pull/73

Full Changelog: vercel/speed-insights@1.0.11...1.0.12

v1.0.11

Compare Source

What's Changed

• fix: nextjs parallel routes with catchall isn't supported by @​feugy in https://github.com/vercel/speed-insights/pull/69
• fix(#​68): postinstall is failing with no error

Full Changelog: vercel/speed-insights@1.0.10...1.0.11

vite-pwa/nuxt (@​vite-pwa/nuxt)

v0.10.5

Compare Source

   🐞 Bug Fixes

• Dev sw stop working when using generateSW strategy  -  by @​userquin in https://github.com/vite-pwa/nuxt/issues/162 (d9fd3)

    View changes on GitHub

v0.10.4

Compare Source

   🐞 Bug Fixes

• Remove unused imports in icons plugin  -  by @​userquin in https://github.com/vite-pwa/nuxt/issues/161 (f391b)

    View changes on GitHub

v0.10.3

Compare Source

No significant changes: add git+ prefix to repository url, bump vite pwa to 0.20.3

    View changes on GitHub

v0.10.2

Compare Source

   🐞 Bug Fixes

• Remove @nuxt/schema module augmentation  -  by @​userquin in https://github.com/vite-pwa/nuxt/issues/159 (ac19c)

    View changes on GitHub

v0.10.1

Compare Source

   🐞 Bug Fixes

• Upgrade @nuxt/module-builder  -  by @​danielroe in https://github.com/vite-pwa/nuxt/issues/156 (8c231)

    View changes on GitHub

v0.10.0

Compare Source

   🚨 Breaking Changes

• Augment vue rather than @vue/runtime-core  -  by @​userquin in https://github.com/vite-pwa/nuxt/issues/151 (a0a1d)

    View changes on GitHub

evanw/esbuild (esbuild)

v0.24.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

• Drop support for older platforms (#​3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

  This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#​3913)

  Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#​3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#​3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#​3917)

  This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

  This fix was contributed by @​Joshix-1.

v0.23.1

Compare Source

• Allow using the node: import prefix with es* targets (#​3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open
  
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#​3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#​3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#​3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#​3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

nuxt/nuxt (nuxt)

v3.13.2

Compare Source

3.13.2 is the next regularly scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

npx nuxi@latest upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🔥 Performance

• nuxt: Remove interop default for dynamic components (#​28912)

🩹 Fixes

• nuxt: Fix ssr log querySelector (#​28864)
• schema: Enable propsDestructure by default (#​28830)
• nuxt: Ensure injected route has enumerable keys (#​28841)
• nuxt: Don't override vue instance with legacy asyncData (#​28842)
• nuxt: Render server errors with ssr: false (#​28834)
• nuxt: Resolve full component paths (#​28843)
• nuxt: Improve accuracy of module resolution conditions (#​28846)
• nuxt: Log more context of prerendering errors (#​28895)
• nuxt: Enable injectAtEnd to reduce circular auto-imports (#​28822)
• nuxt: Ensure we process files in buildDir for unimport (#​28899)
• nuxt: Do not accept attrs on <NuxtErrorBoundary> (#​28901)
• nuxt,schema: Accept any module in inline modules array (#​28922)
• nuxt: Fall back to original component filePath (#​28925)
• nuxt: Make runWithContext generic (#​28926)
• nuxt: Set inheritAttrs: false for fragment components (#​28939)
• nuxt: Use case-insensitive regexp for <script> blocks (4fd24381c)
• nuxt: Ensure component imports are injected last (#​28944)
• nuxt: Catch chunk errors directly in navigation (820908696)
• nuxt: Add missing isNuxtMajorVersion export (#​29016)
• nuxt: Correct type for useError (#​28996)

💅 Refactors

• nuxt: Use vite:preloadError event (#​28862)

📖 Documentation

• Add known limitations for app.config.ts (#​28875)
• Typo fixed missing closing angle bracket (#​28880)
• Update useFetch troubleshooting section (#​28918)
• Capitalize text (#​28972)
• Fix typo (#​28983)
• Add clarity to useFetch parameter signature (#​28993)
• Remove confusing reference to 'SPA' (#​28991)

🏡 Chore

• Use consola to log out compatibility info (#​28854)
• vite: Use correct type import (3f508d521)
• Enable noUncheckedSideEffectImports (#​28903)
• Add pending triage to blank issues (#​28923)
• Correct comment style (c4181b5a2)
• Fix typos (462380d45)
• Refresh lockfile, use htmlnano + pin workflow deps (#​28946)
• Pin dep + workflow by hash (4d81334c9)
• ui-templates: Use class-selector (043329f52)

✅ Tests

• Collect bundle sizes in parallel (1ce81069d)
• Add regression test for using route in template (#​28967)
• Convert set to array (6ee3b3adc)
• Switch inline snapshot to object comparison (ae5135363)

🤖 CI

• Access issue number from payload (8e4585c14)
• Configure codeql to ignore tests (d5f98a757)
• Add default permissions for workflows (3ede01cd4)
• Scan source files with codeql (#​28943)
• Skip setting up node before codeql scan (c4d7c92e9)

❤️ Contributors

• Daniel Roe (@​danielroe)
• Artem Maslov (@​Twocram)
• Paulo Ricardo Severo (@​prsevero)
• Nishant Aanjaney Jalan (@​cybercoder-naj)
• @​beer (@​iiio2)
• Julien Huang (@​huang-julien)
• Liran Tal (@​lirantal)
• Anthony Fu (@​antfu)
• Osama Abdallah Essa Haikal (@​OsamaHaikal)

v3.13.1

Compare Source

3.12.4 is the next regularly scheduled patch release.

👀 Highlights

Although this is a patch release, there are two features I'd love to draw your attention to.

1. 🆔 useId now uses a built-in Vue composable for stable ids between server + client! https://github.com/nuxt/nuxt/pull/28285
2. 🔥 a new experimental.buildCache feature now allows for quicker app rebuilds https://github.com/nuxt/nuxt/pull/28726

As always, feedback is appreciated 🙏 ❤️

✅ Upgrading

As usual, our recommendation for upgrading is to run:

npx nuxi@latest upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🔥 Performance

• nuxt: Cache vue app build outputs (#​28726)
• nuxt: Use ServerPlaceholder for ssr client components (#​28563)
• nuxt: Use reducer array + handle modified proto (#​28768)

🩹 Fixes

• schema: Resolve user-provided serverDir relative to root (#​28700)
• nuxt: Handle mismatching declaration/plugin extensions (#​28709)
• nuxt: Do not accept arbitrary strings for MiddlewareKey (#​28676)
• nuxt: Do not pass listeners to custom NuxtLink (#​28738)
• nuxt: Generate basic jsdoc for module config entry (#​27689)
• nuxt: Augment NuxtOptions as well as config (#​28747)
• nuxt: Improve error logging in import protections (#​28753)
• nuxt: Handle deleted cookies from CookieStore events (#​28760)
• nuxt: Allow updating appConfig with non-iterable objects (#​28773)
• nuxt: Improve isNuxtError type inference (#​28814)

💅 Refactors

• nuxt: Update to vue v3.5 + native useId (#​28285)

📖 Documentation

• Fix typo (#​28724)
• Update broken/redirected links (#​28739)
• Capitalize text (#​28734)
• Updated line number for nuxt build-time hooks (#​28746)
• Add missing query returned value from useRoute() (#​28743)
• Persist package manager choice in code blocks (#​28514)
• Fix postcss codeblock typo (#​28801)
• Include --frozen-lockfile when installing dependencies (#​28794)

🏡 Chore

• Use tinyexec internally (#​28684)
• Use tinyglobby internally (#​28686)
• Trim tag (#​28687)
• Fix ci typo (#​28721)
• Tidying workflows + add sherif workflow (#​28793)
• Ignore eslint warnings about console logging (#​28795)

✅ Tests

• Update bundle size (99df4c222)

❤️ Contributors

• Gianluca Di Francesco (@​gianlucadifrancesco)
• Daniel Roe (@​danielroe)
• Joaquín Sánchez (@​userquin)
• Heb (@​Hebilicious)
• Eckhardt (Kaizen) Dreyer (@​Eckhardt-D)
• Gustav Odinger (@​gustavwilliam)
• Julien Huang (@​huang-julien)
• Ismail Sabet (@​ismailsabet)
• Max (@​onmax)
• Anthony Fu (@​antfu)
• @​beer (@​iiio2)
• riskrole (@​riskrole)
• Thimo Sietsma (@​th1m0)

v3.13.0

Compare Source

👀 Highlights

I'm pretty excited about this release - we've ported some features we had planned for Nuxt v4 back to v3, as well as a raft of bug fixes and performance improvements - as usual.

Here are a few of things I'm most excited about.

🏘️ Route Groups

We now support naming directories with parentheses/brackets to organise your routes without affecting the path.

For example:

-| pages/
---| index.vue
---| (marketing)/
-----| about.vue
-----| contact.vue

This will produce /, /about and /contact pages in your app. The marketing group is ignored for purposes of your URL structure.

Read more in the original PR.

🏝️ Islands and Head Metadata

It's now possible for server component islands to manipulate the head, such as by adding SEO metadata when rendering.

Read more in #​27987.

🪝 Custom Prefetch Triggers

We now support custom prefetch triggers for NuxtLink (#​27846).

For example:

<template>
  <div>
    <NuxtLink prefetch-on="interaction">
      This will prefetch when hovered or when it gains focus
    </NuxtLink>
    <!-- note that you probably don't want both enabled! -->
    <NuxtLink :prefetch-on="{ visibility: true, interaction: true }">
      This will prefetch when hovered/focus - or when it becomes visible
    </NuxtLink>
  </div>
</template>

It's also possible to enable/disable these globally for your app and override them per link.

For example:

export default defineNuxtConfig({
  experimental: {
    defaults: {
      nuxtLink: {
        prefetch: true,
        prefetchOn: { visibility: false, interaction: true }
      }
    }
  }
})

🗺️ Better Server Source Maps

When running with node --enable-source-maps, you may have noticed that the source maps for the Vue files in your server build pointed to the Vite build output (something like .nuxt/dist/server/_nuxt/index-O15BBwZ3.js).

Now, even after your Nitro build, your server source maps will reference your original source files (#​28521).

Note that one of the easiest ways of improving your build performance is to turn off source maps if you aren't using them, which you can do easily in your nuxt.config:

export default defineNuxtConfig({
  sourcemap: {
    server: false,
    client: true,
  },
})

🎁 New Features for Module Authors

In the run-up to Nuxt v4, we're working on adding some key functionality for module authors, including a new isNuxtMajorVersion utility where required (#​27579) and better inferred typing for merged module options using the new defineNuxtModule().with() method (#​27520).

✨ Improved Dev Warnings

We no longer warn when using data fetching composables in middleware (#​28604) and we warn when user components' names begin with Lazy (#​27838).

🚨 Vue TypeScript Changes

For a while, in the Vue ecosystem, we've been augmenting @vue/runtime-core to add custom properties and more to vue. However, this inadvertently breaks the types for projects that augment vue - which is now the officially recommended in the docs way to augment these interfaces (for example, ComponentCustomProperties, GlobalComponents and so on).

This means all libraries must update their code (or it will break the types of libraries that augment vue instead).

We've updated our types in Nuxt along these lines but you may experience issues with the latest vue-router when used with libraries which haven't yet done so.

Please create an issue with a reproduction - I'll happily help create a PR to resolve in the upstream library in question. Or you may be able to work around the issue by creating a declarations.d.ts in the root of your project with the following code (credit):

import type {
  ComponentCustomOptions as _ComponentCustomOptions,
  ComponentCustomProperties as _ComponentCustomProperties,
} from 'vue';

declare module '@​vue/runtime-core' {
  interface ComponentCustomProperties extends _ComponentCustomProperties {}
  interface ComponentCustomOptions extends _ComponentCustomOptions {}
}

✅ Upgrading

As usual, our recommendation for upgrading is to run:

npx nuxi@latest upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🚀 Enhancements

• nuxt: Await custom routes function in router.options (#​27644)
• kit: Add new isNuxtMajorVersion compatibility util (#​27579)
• kit,schema: Add .with for better module options types (#​27520)
• nuxt: Warn when user components' names begin with Lazy (#​27838)
• nuxt: Allow specifying app id when creating a nuxt app (#​28392)
• nuxt: Custom enable/disable hooks for usePreviewMode (#​28371)
• kit: Add prepend option to addRouteMiddleware (#​28496)
• nuxt: Allow organising pages within route groups (#​28276)
• vite: Preserve vite sourcemaps for nitro build (#​28521)
• nuxt: Allow defining triggers for prefetching links (#​27846)
• nuxt: Namespace __NUXT__ when using multi-app (#​27263)
• nuxt: Allow server islands to manipulate head (#​27987)

🔥 Performance

• nuxt: Call cookie decode function only for named cookie (#​28215)
• nuxt: Avoid making client-only component setup async (#​28334)
• nuxt: Avoid multiple calls to getCachedData (#​28472)

🩹 Fixes

• nuxt: Don't warn for definePageMeta in client-only pages (#​28246)
• kit: Include module dist/runtime/ in tsconfig includes (#​28237)
• schema: Support absolute/relative paths for assetsDir (59f0099f4)
• schema: Do not override user serverDir (#​28249)
• schema: Use new options syntax for vite-plugin-vue (#​28307)
• schema: Export new module return types (c0ad8db93)
• kit: Add missing type import (1a60b4541)
• vite,webpack: Handle local postcss plugins (#​28481)
• nuxt: Handle scroll-padding-top: auto in scrollBehavior (#​28320)
• nuxt: Ensure runtimeConfig.public is reactive on client (#​28443)
• nuxt: Update renamed stub composables from nuxt/scripts (#​28449)
• nuxt: Augment @vue/runtime-core and @vue/runtime-dom (#​28446)
• nuxt: Scan jsx pages for page metadata (#​28479)
• nuxt: Handle plugin type extensions more correctly (#​28480)
• vite: Respect baseURL for public assets in dev (#​28482)
• vite: Add transformation result to log for parse errors (#​28508)
• vite: Include module symbols in generated code (#​28509)
• nuxt: Add reason when aborting request in useFetch (#​28517)
• nuxt: Only augment vue, not sub-packages (#​28542)
• nuxt: Avoid stripping js extensions in plugin injections (#​28593)
• nuxt: Preserve route-specific metadata on route.meta (#​28441)
• nuxt: Don't warn when data fetching in middleware (#​28604)
• nuxt: Extract route rules/page meta in 2+ script blocks ([#​286

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.