chore(deps): update non-major dependencies by renovate[bot] · Pull Request #214 · bounda-dev/bounda

renovate · 2026-10-26T00:26:09Z

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/check (source)	`0.9.11` → `0.9.12`
@astrojs/starlight (source)	`0.42.6` → `0.42.7`
@biomejs/biome (source)	`2.6.2` → `2.6.3`
@cloudflare/vite-plugin (source)	`1.64.0` → `1.65.0`
@cloudflare/vitest-plugin (source)	`1.4.6` → `1.4.9`
@cloudflare/workers-types	`5.20261021.1` → `5.20261028.1`
@react-router/dev (source)	`8.5.0` → `8.5.1`
@react-router/node (source)	`8.5.0` → `8.5.1`
@react-router/serve (source)	`8.5.0` → `8.5.1`
@stryker-mutator/core (source)	`10.0.0` → `10.1.1`
@stryker-mutator/vitest-runner (source)	`10.0.0` → `10.1.1`
astro (source)	`7.4.1` → `7.4.2`
pnpm (source)	`12.15.0` → `12.16.1`
pnpm (source)	`12.15.0` → `12.16.1`
react-router (source)	`8.5.0` → `8.5.1`
tsdown (source)	`0.23.1` → `0.23.3`
wrangler (source)	`4.151.3` → `4.154.0`

Release Notes

withastro/astro (@astrojs/check)

`v0.9.12`

Compare Source

Patch Changes

#18455 7af66fc Thanks @astro-factory! - Fixes the astro-check binary ignoring its first two command-line arguments, so flags such as --help, --root, --watch, and --tsconfig are respected again. If your scripts padded the arguments to work around this (for example, astro-check -- -- --tsconfig ./tsconfig.app.json), remove the padding.
Updated dependencies [044148d]:
- @astrojs/language-server@2.17.3

withastro/starlight (@astrojs/starlight)

`v0.42.7`

Compare Source

Patch Changes

#4264 94e0985 Thanks @chrispezza! - Fixes a layout shift where the table of contents could be painted at the start of the content area and then jump to the end when a page's HTML arrived in several chunks
#4285 6f22edd Thanks @tunetheweb! - Improves hero image loading by adding fetchpriority="high" hint for browsers

biomejs/biome (@biomejs/biome)

`v2.6.3`

Compare Source

Patch Changes

#12275 807e616 Thanks @dyc3! - Added the new nursery rule noArraySortForMinMax, which reports sorting an array only to read its smallest or largest value. Use Math.min() or Math.max() instead.
```
const minimum = array.toSorted((a, b) => a - b)[0];
```
#12432 cf61682 Thanks @dyc3! - Added the nursery rule noBooleanSortComparator, which reports sort comparators that return a boolean instead of a number. For example, array.sort((a, b) => a > b) never puts the first item before the second, so the array isn't sorted correctly.
#12304 b4654c5 Thanks @dyc3! - Added the new nursery rule noEagerArrayMethodsInLoops, which reports .map() and .filter() calls in the header of for...of loops. These calls build a new array that is only used by the loop.
```
for (const name of users.map((user) => user.name)) {
  console.log(name);
}
```
#12121 66c3791 Thanks @dyc3! - Added the nursery rule noNewRequire, which disallows calling require with new, such as new require("app-header").
#12316 34b520d Thanks @dyc3! - Added the new nursery rule noObsoleteAttributes, which disallows obsolete attributes on HTML elements and suggests what to use instead.
```
<table bgcolor="#ffffff" cellpadding="5"></table>
```
#12258 cce2385 Thanks @dyc3! - Added the nursery rule noPathConcat, which disallows building file paths and URLs by joining strings to __dirname, __filename, import.meta.dirname, import.meta.filename, or import.meta.url.
```
const fullPath = __dirname + "/foo.js"; // reported
```
#12287 e12ad78 Thanks @dyc3! - Added the new nursery rule noPlaywrightNthMethods, which disallows selecting Playwright elements by position with first(), last(), and nth(). A test that relies on the position of an element can act on a different element when the page changes.
```
await page.locator("button").first().click();
```
#12343 62ad123 Thanks @vibbix! - Added the nursery rule noSelfNestedLayer, which disallows nesting a cascade layer inside a layer with the same name. Layer names inside an @layer block are relative to it, so the inner layer below creates the sublayer components.components instead of adding to components.
```
@layer components {
  @layer components {
    .button {
      color: red;
    }
  }
}
```
#12289 bbbd95d Thanks @dyc3! - Added the nursery rule noShortTimeValues, which reports CSS animation and transition times that are shorter than the configured minimum number of milliseconds. The rule does nothing until minimum is set.

For example, the following code is invalid when minimum is 100:
```
a {
  transition-duration: 80ms;
}
```
#12431 f748ec0 Thanks @dyc3! - Added the nursery rule noSvelteInternal, which disallows importing from svelte/internal and its submodules. These modules are private to Svelte and can change or disappear in any release.
```
import { get_current_component } from "svelte/internal";
```
#12270 8ae35c4 Thanks @dyc3! - Added the nursery rule noTanstackQueryRestDestructuring, which disallows rest destructuring and object spread on TanStack Query results. Both read every property of the result, so the component updates on every change to the query.
```
import { useQuery } from "@tanstack/react-query";

const { data, ...rest } = useQuery({ queryKey: ["todos"], queryFn: fetchTodos });
```
The rule belongs to the new tanstackQuery domain.
#12308 372af2a Thanks @dyc3! - Added the new nursery rule noUnreadableForOfExpression, which reports for...of and for await...of loops that go through the result of a complex expression instead of a variable, a property, or a short call.
```
for (const item of getItems(createArgument(seed))) {} // reported
```
#12422 0be8d10 Thanks @dyc3! - Added the new nursery rule noUnsafeReturn, which disallows returning a value typed as any from a function.
```
function parse(text: string) {
  return JSON.parse(text); // reported
}
```
#12311 8434c92 Thanks @dyc3! - Added the nursery rule noUselessSplice, which reports splice() calls that have a simpler alternative. For example, array.splice(0, 1) can be written as array.shift().
#12293 eaa4a2b Thanks @dyc3! - Added the nursery rule noVueUnusedEmitDeclarations, which reports events that a Vue component declares but never emits.

For example, the following component never emits close:
```
<script setup>
const emit = defineEmits(["change", "close"]);
emit("change");
</script>
```
#12386 f01ebb0 Thanks @dyc3! - Added the nursery rule noVueVTextVHtmlOnComponent, which disallows v-text and v-html on Vue components. These directives replace everything inside the component's root element instead of filling its slot.
```
<template>
  <MyComponent v-html="html"></MyComponent>
</template>
```
#12385 7bd38b7 Thanks @dyc3! - Added the new nursery rule noVueWatchAfterAwait, which disallows creating watchers after an await in a Vue component's setup() function. Vue doesn't stop these watchers when the component is removed. A watcher is allowed when the function it returns is stored, so that function can be called later to stop the watcher.
```
<script>
import { watch } from "vue";

export default {
  async setup() {
    await fetchUser();
    watch(source, () => {});
  },
};
</script>
```
#12286 50d2a4e Thanks @dyc3! - Added the nursery rule noZeroLengthUnit, which disallows units on zero lengths in CSS. Biome can remove the unit.
```
a {
  top: 0px;
}
```
#12300 ab2eb9e Thanks @dyc3! - Added the nursery rule useBlockStatementOverIife, which reports functions that are called immediately when a block statement can replace them. Biome can replace these functions with a block statement.

Invalid:
```
(() => {
    const value = getValue();
    run(value);
})();
```
#12421 1c2cac0 Thanks @dyc3! - Added the nursery rule useConsistentLightnessNotation, which enforces writing the lightness of lab(), lch(), oklab(), and oklch() colors as a percentage, or as a number with the notation option. For example, with the default options, oklch(0.85 0.17 88) is reported and can be fixed to oklch(85% 0.17 88).
#12224 fef7ed4 Thanks @dyc3! - Added the nursery rule useExpectToContain, which reports tests that compare the result of includes() to a boolean, and suggests using toContain() instead.
```
expect(fruits.includes("apple")).toBe(true);
```
#12299 0d5025d Thanks @dyc3! - Added the new nursery rule useIteratorZip, which reports for loops that use an index only to read the same position from several arrays. Such loops can use Iterator.zip() instead.
```
// reported
for (let index = 0; index < Math.min(names.length, scores.length); index++) {
  save(names[index], scores[index]);
}
```
#12298 a234d2f Thanks @dyc3! - Added the nursery rule useMathAbs, which reports manual absolute value calculations and range checks that can use Math.abs(). For example, value < 0 ? -value : value can be written as Math.abs(value), and value > limit || value < -limit can be written as Math.abs(value) > limit.
#12499 bd024cc Thanks @dyc3! - Added the nursery rule useMathTrunc, which requires Math.trunc() instead of bitwise operations or parseInt(String(x), 10) for removing the decimal part of a number. For example, const result = value | 0; and const result = ~~value; are now reported.
#12314 9e875a4 Thanks @dyc3! - Added the new nursery rule usePackageJsonValidCpu, which reports a cpu field in package.json that isn't an array of known processor types. The cpu field lists the processor types that the package supports.

For example, the rule reports the following package.json file because x86 isn't a processor type that package managers recognize:
```
{
  "name": "my-package",
  "cpu": ["x86"]
}
```
#12315 cb30544 Thanks @dyc3! - Added the nursery rule usePackageJsonValidEngines, which reports an invalid engines field in package.json. The field must be an object, and each of its values must be a non-empty string.

For example, the following engines field is reported because the version of node is a number:
```
{
    "engines": {
        "node": 24
    }
}
```
#12400 407604d Thanks @dyc3! - Added the nursery rule useVueComponentIs, which requires Vue <component> elements to bind the is attribute with :is or v-bind:is. Without it, Vue has no component to render.
```
<template>
  <component :is="currentView" />
</template>
```
#12337 c371520 Thanks @dyc3! - Added the nursery rule useVueToggleInsideTransition, which requires the element inside a Vue <Transition> to be shown and hidden with v-if or v-show. Without one of them, the element is always shown and the transition never plays.
```
<template>
  <Transition>
    <div>Content</div>
  </Transition>
</template>
```
#12387 64472e9 Thanks @dyc3! - Added the nursery rule useVueTypedRef, which reports ref() and shallowRef() calls in TypeScript that have no type argument and no initial value other than null or undefined. Without a type, TypeScript can't tell which values these refs are meant to hold.
```
import { ref } from "vue";

const count = ref();
```
#12423 bf1a55a Thanks @dyc3! - Added the nursery rule useVueVOnExact, which requires the .exact modifier on a v-on listener when another listener for the same event on the element needs more modifier keys, such as .ctrl. Without .exact, both listeners run when those keys are held down. The rule accepts the following code:
```
<template>
  <button @click.exact="select" @click.ctrl="open"></button>
</template>
```
#12418 208730e Thanks @latin-1! - Fixed #12417: useSortedProperties could produce invalid CSS when sorting properties without a final semicolon. Comments attached to reordered properties are preserved.
#12216 f2a3c71 Thanks @dyc3! - Added the new nursery rule noDanglingUnderscore, which disallows variable names, function names, and property accesses that start or end with an underscore.
```
const _count = 0; // reported
user._id; // reported
```
#12536 438997f Thanks @vidigoat! - Fixed the formatter removing the parentheses around an instantiation expression before +, -, <, >, >=, >> and >>>. TypeScript reads make<T> + y as make < T > +y, and make<T> >> y doesn't parse.
```
- x = make<T> + y;
+ x = (make<T>) + y;
- x = make<T> >> y;
+ x = (make<T>) >> y;
```
#12540 7d3e8a1 Thanks @vidigoat! - Fixed the formatter removing the parentheses around an instantiation expression before a non-null assertion or type arguments of a class heritage, which produced code that doesn't parse.
```
- const a = make<T>!;
+ const a = (make<T>)!;
- class D extends B<T><T> {}
+ class D extends (B<T>)<T> {}
```
#12496 09d89b9 Thanks @vidigoat! - Fixed the formatter removing the parentheses around binary, logical, type-cast and instantiation operands of an instantiation expression. The type arguments then applied to the last operand only, and a nested instantiation expression didn't parse.
```
- const x = a + b<T>;
+ const x = (a + b)<T>;
- const y = a as B<T>;
+ const y = (a as B)<T>;
- const z = f<A><B>;
+ const z = (f<A>)<B>;
```
#12526 dbcdab1 Thanks @dyc3! - Fixed #12524: the Markdown formatter no longer removes the blank line between a paragraph and the list that follows it. Removing it could change the document, because an ordered list that doesn't start at 1 can't interrupt a paragraph and became part of the paragraph text.
```
Steps:

3. three
4. four
```
#12509 470018b Thanks @dyc3! - Fixed #12507: the Markdown formatter no longer drops the > markers after an empty quote line when proseWrap is "always" or "never". Previously, the text after the empty line was moved out of the blockquote.
```
  > a
  >
- b
+ > b
```
#12598 5699601 Thanks @vidigoat! - Fixed the formatter removing the parentheses around the callee of a new expression when it contains a dynamic import() call, which produced code that doesn't parse.
```
- new import("foo").bar();
+ new (import("foo").bar)();
```
#12508 87d9e6b Thanks @dyc3! - Fixed #12502: noInvalidGridAreas now counts the cells in each row of grid-template-areas instead of comparing the length of the row text. Rows such as "a" "bb" are no longer reported, and rows such as "abc" "d e" are now reported.
#12530 7f467b2 Thanks @dyc3! - Fixed #12529: noUselessElse no longer reports an else clause when the if block ends with a switch statement that has no default clause. If no case matches, such a switch doesn't exit, so the else clause is needed.
#12511 d4ea663 Thanks @dyc3! - Fixed #12505: useDomNodeTextContent no longer reports innerText on values whose type annotation shows they aren't DOM nodes. The following code is now valid:
```
const Link = ({ innerText }: { innerText: string }) => <a>{innerText}</a>;
```
#12588 e262362 Thanks @ematipico! - Fixed noDescendingSpecificity to compare resolved nested selector targets. Biome no longer reports nested selectors that resolve to different targets, detects equivalent explicit and nested targets, and emits one diagnostic when a parent selector list expands the same nested selector multiple times.

For example, the following selectors are no longer reported because their final targets are .column and code, respectively:
```
.card {
  .column {
    :root[data-theme="dark"] & {}
  }

  code {
    :root[data-theme="dark"] & {}
  }
}
```
#12534 e59a324 Thanks @Netail! - Improved the diagnostics of noIdenticalTestTitle. Biome now reports one diagnostic per repeated title, pointing at the first occurrence and at every later occurrence, instead of one diagnostic per duplicate.
#12528 a3132dc Thanks @ff1451! - Fixed #12503: noUnknownProperty now checks SCSS nested properties by the name Sass emits for them. For example, radius in border: { radius: 4px; } is checked as border-radius and is no longer reported, while color in font: { color: red; } is checked as font-color and is now reported.
#12113 ec4eb2d Thanks @dyc3! - Added the nursery rule useConsistentUnicodeBom, which disallows a leading Unicode byte order mark by default and can require one with bom: "always". The rule supports JavaScript, TypeScript, JSON, CSS, GraphQL, HTML, and Markdown, provides a fix, and preserves the unicode-bom option during ESLint migration.

The following example is invalid by default because it starts with an invisible U+FEFF character:
```
const value = 1;
```
#12248 afbc81e Thanks @dyc3! - Added the nursery rule useReactNativeValidPlatformColors, which requires PlatformColor() and DynamicColorIOS() calls to use values written directly in the call, so React Native can optimize them.
```
import { PlatformColor } from "react-native";

const labelColor = "labelColor";
const color = PlatformColor(labelColor);
```
#12599 b62494a Thanks @dyc3! - Fixed #12532: checking the project root no longer applies files.includes exclusions to directories above the project.
#12578 6162922 Thanks @ematipico! - Fixed GraphQL parsing and formatting for executable descriptions and legacy fragment variables. Biome now formats inputs such as "Description" query { field } without panicking and removes insignificant commas consistently.
#12593 35c69ad Thanks @dyc3! - Fixed #12555: the default reporter now prints the command summary, the --max-diagnostics warning, and the skipped-fixes notice to stderr instead of stdout. Diagnostics already go to stderr, so the summary can no longer get mixed into the middle of a diagnostic when a tool reads the two streams separately.
#12415 9520907 Thanks @latin-1! - Fixed #12412: useSortedProperties now sorts properties inside @keyframes animations in CSS and SCSS.

cloudflare/workers-sdk (@cloudflare/vite-plugin)

`v1.65.0`

Compare Source

Minor Changes

#16363 d3240f2 Thanks @jamesopstad! - Remove the experimental.newConfig option from Vite plugin v1

Vite plugin v1 now supports Wrangler configuration files only. Projects using cloudflare.config.ts for configuration should upgrade to Vite plugin v2 beta.

Patch Changes

#16373 8cc5f87 Thanks @petebacondarwin! - Report unsupported remote bindings under Bun instead of hanging

Starting remote bindings now fails with an actionable error explaining Bun's unsupported request routing. Use Node.js or disable remote bindings to continue local development.
#16334 9cecd09 Thanks @petebacondarwin! - Fix Container setup guidance in Vite development and preview

Container registry instructions now show the Wrangler command and the configuration location, including Wrangler files and inline Vite configuration.
#16333 68d6eec Thanks @petebacondarwin! - Update the local Workers runtime to the October 19 release

Include the fix for nested asset paths during local development on Windows, together with the compatible Wrangler release.

The runtime update also disposes Workflow step results and introspection modifiers after use, preventing undisposed RPC warnings and cancelled local Workflow requests.
#16379 160e655 Thanks @petebacondarwin! - Update the local Workflow runtime to use native storage cleanup

Consume the Miniflare fix that queues Workflow persistence deletion with instance recreation, including deletion through the local Explorer. This prevents storage cleanup from racing reuse of the same Workflow instance ID.
#16289 bbe822f Thanks @petebacondarwin! - Retry remote preview token refreshes after transient failures

Backport the retry fix to the private remote-bindings workspace package and require wrangler@4.151.1 so long-running remote development sessions recover after a network outage.
#16291 0262f7d Thanks @petebacondarwin! - Use published SDK dependencies for Vite plugin v1 maintenance

Pin the plugin's published SDK dependencies to their deployed npm versions. Keep private shared packages as workspace dependencies so their implementation and build tools remain available on the v1 maintenance branch.

cloudflare/workers-sdk (@cloudflare/vitest-plugin)

`v1.4.9`

Compare Source

Patch Changes

Updated dependencies [0968b08, f3c13b3]:
- miniflare@5.20261023.1-beta
- wrangler@4.154.0

`v1.4.8`

Patch Changes

#16403 5f82a56 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-10-22

Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16437 e651d7c Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-10-23

Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16476 8a30d8e Thanks @tannerlinsley! - Update Undici to 7.30.1 to prevent a malformed HTTP response from crashing development tools

The updated shared dependency rejects excessive content encodings without leaving an unhandled stream error when the server closes the connection early. This fixes GHSA-xjj6-f33q-929c and keeps the matching Undici types on the same version.
#16490 bcd618d Thanks @petebacondarwin! - Update Zod to 4.6.6 to address GHSA-mrhx-c7xc-m3w5

The updated shared dependency fixes excessive memory consumption when validating oversized collections. This updates both the published Zod dependencies and the copies bundled into development tools and Workers.
#16335 28cca4c Thanks @robingenz! - Fix Worker tests failing when CommonJS dependencies require packages with separate import and require entries on Vite 8. The fix needs Vite 8.2.1 or later; Vite 8.0.x, 8.1.x and 8.2.0 stay affected.
Updated dependencies [9e05ade, 5f82a56, e651d7c, 5f82a56, e651d7c, 8a30d8e, c0e915f, b7e762d, c709bff, 23ef63a, bcd618d]:
- miniflare@5.20261023.0-beta
- wrangler@4.153.0

`v1.4.7`

Patch Changes

Updated dependencies [80a9f96, 08f22d3, 2878645, a4eb57d, 182d6de]:
- wrangler@4.152.0
- miniflare@5.20261019.2-beta

cloudflare/workerd (@cloudflare/workers-types)

remix-run/react-router (@react-router/dev)

`v8.5.1`

Compare Source

Patch Changes

Use resolved Vite environment output directories when reading and writing build artifacts (#15480)
- Finalize server-bundle manifest paths after asynchronous Vite configuration hooks complete
- Preserve output-directory overrides applied when creating a Vite build environment
Run prerendering after other Vite plugins finish their application build hooks (#15481)
- Close React Router's build resources when another plugin's application build hook fails during react-router build
Updated dependencies:

remix-run/react-router (@react-router/node)

`v8.5.1`

Compare Source

Patch Changes

Updated dependencies:
- react-router@8.5.1

remix-run/react-router (@react-router/serve)

`v8.5.1`

Compare Source

Patch Changes

Avoid writing a blank line to stderr when the server shuts down successfully (#15641)
Updated dependencies:

stryker-mutator/stryker-js (@stryker-mutator/core)

`v10.1.1`

Compare Source

Note: Version bump only for package @stryker-mutator/core

stryker-mutator/stryker-js (@stryker-mutator/vitest-runner)

`v10.1.1`

Compare Source

Note: Version bump only for package @stryker-mutator/vitest-runner

withastro/astro (astro)

`v7.4.2`

Compare Source

Patch Changes

#18430 dda9ec3 Thanks @Abhirup-99! - Speeds up content sync with experimental.collectionStorage: "chunked" by computing each character's UTF-8 width from its code point instead of encoding every character through TextEncoder. On a store of ~44k entries this cuts the chunking step from about 60 seconds to well under a second, with byte-identical output.
#18438 5e0eaa4 Thanks @astro-factory! - Fixes astro dev with @astrojs/cloudflare failing with Calling `require` for "node-fetch" when a server dependency such as cross-fetch requires node-fetch
[#183

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Madrid)

Branch creation
- "on monday"
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.

renovate · 2026-10-27T02:02:40Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Error: ERR_PNPM_UNUSED_PATCH

  × installing dependencies
  ╰─▶ The following patches were not used: @stryker-mutator/vitest-
      runner@10.0.0
  help: Either remove them from "patchedDependencies" or update them to match
        packages in your dependencies.

renovate Bot force-pushed the renovate/non-major branch 6 times, most recently from 0227d6a to d18e8cf Compare October 27, 2026 02:02

renovate Bot force-pushed the renovate/non-major branch 14 times, most recently from cc8e09a to 247721a Compare October 31, 2026 10:15

benatespina force-pushed the main branch from b540e34 to 8d0aa00 Compare October 31, 2026 10:39

renovate Bot force-pushed the renovate/non-major branch from 247721a to aa3d398 Compare October 31, 2026 10:43

chore(deps): update non-major dependencies

31a62e0

renovate Bot force-pushed the renovate/non-major branch from aa3d398 to 31a62e0 Compare October 31, 2026 11:11

Navigation Menu

Repository navigation

chore(deps): update non-major dependencies - #214

chore(deps): update non-major dependencies#214
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/non-major

renovate Bot commented Oct 26, 2026 •

edited

Loading

Uh oh!

renovate Bot commented Oct 27, 2026

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Oct 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

renovate Bot commented Oct 27, 2026

⚠️ Artifact update problem

File name: pnpm-lock.yaml

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Oct 26, 2026 •

edited

Loading