chore(deps): update all dependencies by renovate[bot] · Pull Request #566 · mnahkies/openapi-code-generator

renovate · 2026-11-01T01:36:24Z

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update	Pending
@azure-tools/typespec-autorest (source)	`0.73.1` → `0.73.2`	pnpm.catalog.default	patch	`0.74.0`
@azure-tools/typespec-client-generator-core (source)	`0.73.0` → `0.73.1`	pnpm.catalog.default	patch	`0.74.0`
@biomejs/biome (source)	`2.5.15` → `2.6.5`	pnpm.catalog.default	minor	`2.6.7` (+1)
@biomejs/js-api (source)	`6.0.0` → `6.1.0`	pnpm.catalog.default	minor
@biomejs/wasm-nodejs (source)	`2.5.15` → `2.6.5`	pnpm.catalog.default	minor	`2.6.7` (+1)
@vitest/coverage-v8 (source)	`5.0.5` → `5.1.0`	pnpm.catalog.default	minor
node (source)	`26.12.1` → `26.13.1`	tools	minor
node	`26.12.1` → `26.13.1`	uses-with	minor
pnpm (source)	`12.14.0+sha512.c18ba6d87993d3d164cb5e8948f32b2c06ee854487e06cd8d86781342fb3e5bb4634367034711e86802baa9c37bea906ce1929ad08d70884c97d801df13389a6` → `12.18.0`	packageManager	minor
pnpm/action-setup	`v6.1.0` → `v6.1.1`	action	patch
typescript (source)	`^6.0.3` → `^7.0.0`	pnpm.catalog.typescript6	major

Release Notes

Azure/typespec-azure (@azure-tools/typespec-autorest)

`v0.73.2`

Compare Source

Bug Fixes

#5799 Report an error at the source YAML when an applicable unified example references an operation that does not exist in the emitted API version.

biomejs/biome (@biomejs/biome)

`v2.6.5`

Compare Source

Patch Changes

#12755 bbc4887 Thanks @dyc3! - Added the new nursery rule noArrayForEach, which reports forEach() calls that can be written as for...of loops. Values known not to be arrays, such as a Map or a Set, are ignored.
```
array.forEach((element) => {
	bar(element);
});
```
#12777 ba692e4 Thanks @dyc3! - Added the new nursery rule noAwaitInPromiseMethods, which reports await inside the array passed to Promise.all(), Promise.allSettled(), Promise.any(), or Promise.race(). The await pauses the code before the method is called, so the promises no longer run at the same time.
```
Promise.all([await promise, anotherPromise]);
```
#12765 af84fb4 Thanks @dyc3! - Added the new nursery rule noChainedComparison, which reports comparisons chained like a < b < c or a === b === c. JavaScript compares a with b first, and then compares the resulting true or false with c, so 3 > 2 > 1 is false.
```
if (a < b < c) {}
```
#12547 0a2073d Thanks @dyc3! - Added the nursery rule noDynamicDelete, which disallows using delete with a property name that is computed at runtime. Fixed property names written as string or number literals are allowed.
```
delete container[name];
```
#12481 ed7adc2 Thanks @dyc3! - Added the nursery rule noLateEventControl, which reports calls to preventDefault(), stopPropagation(), and stopImmediatePropagation() that run after the browser has finished handling the event, where they have no effect.
```
element.addEventListener("click", async (event) => {
  await save();
  event.preventDefault();
});
```
#12795 179666d Thanks @dyc3! - Added the nursery rule noMapSpread, which disallows spreading objects or arrays in the values returned by map() and flatMap() callbacks. Each spread copies a whole object or array for every item, which is slow for large arrays. Its unsafe fix replaces an object that starts with a spread with Object.assign().
```
const users = getUsers();
const rows = users.map((user) => ({ ...user, role: getRole(user) }));
```
#12793 d9a99fd Thanks @dyc3! - Added the nursery rule noMismatchedMapKey, which reports get() and set() calls that use a different key than the has() check before them. Checking one key and then using another is usually a copy-paste mistake.
```
if (map.has(key)) {
  map.get(otherKey); // reported
}
```
#12342 1db7c0d Thanks @vibbix! - Added the nursery rule noMissingScssInterpolation, which disallows Sass variables and function calls in custom property values without #{} interpolation. Sass copies these values into the CSS unchanged, so the browser receives $gap or math.div(8px, 2) instead of their results. Its unsafe fix wraps variables in #{}.
```
:root {
  --gap: $gap;
  --half: math.div(8px, 2);
}
```
#12792 de86b37 Thanks @dyc3! - Added the nursery rule noMissingThrow, which reports errors that are created with new but never thrown. Its unsafe fix adds the missing throw keyword.
```
function check(value) {
  if (!value) {
    new Error("Missing value");
  }
}
```
#12790 c23e4c3 Thanks @dyc3! - Added the new nursery rule noObjectLiteralComparison, which reports comparisons with an empty object {} or an empty array []. These comparisons never check whether a value is empty, because objects and arrays are compared by reference.
```
if (value === {}) {}
```
#12450 793f07d Thanks @dyc3! - Added the new nursery rule noPlaywrightUnsafeReferences, which reports functions passed to page.evaluate() or page.addInitScript() that use variables declared outside of them. Playwright runs these functions in the browser page, where those variables don't exist.
```
const x = 7;
await page.evaluate(() => x * 2); // reported: `x` must be passed as an argument
```
#12388 a0160a4 Thanks @vibbix! - Added the nursery rule noPseudoElementInFunctionalPseudoClass, which disallows pseudo-elements inside :is(), :where(), :not() and :has(). Browsers drop these selectors, so the styles never apply to the pseudo-element.
```
.card:is(::before, ::after) {
  content: "";
}
```
#12779 bc1befb Thanks @dyc3! - Added the new nursery rule noSinglePromiseInPromiseMethods, which reports an array with a single element passed to Promise.all(), Promise.any(), or Promise.race(). The rule offers a fix that awaits the value directly or uses Promise.resolve().
```
const result = await Promise.all([promise]);
```
#12241 d96de1d Thanks @dyc3! - Added the nursery rule noSvelteBindValueOnCheckableInputs, which reports bind:value on checkbox and radio inputs in Svelte files. Users change whether these inputs are checked, not their value, so bind:value does not track their choice.
```
<input type="checkbox" bind:value={accepted} />
```
#12764 e166d08 Thanks @dyc3! - Added the new nursery rule noSyncMethods, which reports calls to functions whose names end with Sync, such as fs.readFileSync(). These calls block the program until they finish. The allowAtRootLevel option allows them outside of functions, and the ignore option allows specific function names.
```
const contents = fs.readFileSync("data.txt");
```
#12515 c0a4174 Thanks @dyc3! - Added the nursery rule noTanstackQueryVoidQueryFn, which disallows TanStack Query functions that don't return any data. TanStack Query doesn't accept undefined as the data of a query, so the query fails with an error.
```
import { useQuery } from "@tanstack/react-query";

useQuery({
    queryKey: ["todos"],
    queryFn: async () => {
        await fetch("/api/todos");
    },
});
```
The rule belongs to the tanstackQuery and types domains.
#12482 1e6e407 Thanks @dyc3! - Added the nursery rule noUnnecessaryStringTrim, which reports trim() calls before startsWith() or endsWith() when only one side of the string matters. Use trimStart() or trimEnd() instead.
```
value.trim().startsWith("-");
```
#12772 a108773 Thanks @dyc3! - Added the nursery rule noUselessAwait, which reports await on values that are never promises, such as literals, arrays, and the results of comparisons.
```
await [fetchUser(), fetchPosts()];
```
#12783 d0931b0 Thanks @dyc3! - Added the new nursery rule noUselessLengthCheck, which reports array length checks that don't change the result: a check that the array is empty next to every(), a check that it isn't empty next to some(), or a check that it isn't empty around a for...of loop over the same array.
```
if (array.length > 0 && array.some(Boolean)) {}
```
#12488 93e0e73 Thanks @dyc3! - Added the new nursery rule noUselessTypeAssertion, which reports type assertions that don't change the type of an expression, such as a non-null assertion on a value that can't be null or undefined.
```
function double(value: number): number {
  return value! * 2;
}
```
#12632 0e197b4 Thanks @dyc3! - Added the nursery rule noVueChildContent, which disallows content inside elements that use v-html or v-text. These directives replace the content of their element, so Vue discards anything written there.
```
<template>
  <div v-html="html">Loading...</div>
</template>
```
#12616 cb7b888 Thanks @dyc3! - Added the new nursery rule noVueDeprecatedConfigKeyCodes, which reports uses of Vue.config.keyCodes. Vue 3 removed this option, so custom key names defined with it no longer work.
```
Vue.config.keyCodes = { f1: 112 };
```
#12568 59f3a42 Thanks @dyc3! - Added the nursery rule noVueDeprecatedDestroyedLifecycle, which reports the beforeDestroy and destroyed lifecycle hooks in Vue components. Vue 3 renamed them to beforeUnmount and unmounted, and no longer calls hooks with the old names.
```
<script>
export default {
  destroyed() {},
};
</script>
```
#12654 bcb1e0f Thanks @dyc3! - Added the nursery rule noVueDeprecatedEventsApi, which reports calls to the $on, $off, and $once instance methods in Vue components. Vue 3 removed these methods, so calling them throws an error.
```
<script>
export default {
  mounted() {
    this.$on("start", handler); // reported
  },
};
</script>
```
#12590 b9872ef Thanks @dyc3! - Added the nursery rule noVueDeprecatedFunctionalTemplate, which reports the functional attribute on the <template> of a Vue component. Vue 3 no longer supports this attribute.
```
<template functional>
  <div>{{ props.message }}</div>
</template>
```
#12552 b71b705 Thanks @dyc3! - Added the nursery rule noVueDeprecatedHtmlElementIs, which disallows the is attribute on HTML elements in Vue templates. Vue 3 no longer renders a component in place of these elements, unless the value starts with vue:.
```
<template>
  <tr is="my-row"></tr>
</template>
```
#12553 4a613e1 Thanks @dyc3! - Added the nursery rule noVueDeprecatedInlineTemplate, which disallows the inline-template attribute on Vue components. Vue 3 removed this feature, so the content between the component's tags is no longer used as its template.
```
<template>
  <my-component inline-template>
    <div>{{ message }}</div>
  </my-component>
</template>
```
#12617 0e9ca5b Thanks @dyc3! - Added the nursery rule noVueDeprecatedModelDefinition, which reports the model option in Vue components. Vue 3 ignores this option, so v-model on the component always uses the modelValue prop and the update:modelValue event.
```
<script>
export default {
  model: {
    prop: "checked",
    event: "change",
  },
};
</script>
```
#12604 e998921 Thanks @dyc3! - Added the nursery rule noVueDeprecatedPropsDefaultThis, which reports this inside the function that computes the default value of a Vue prop. Vue doesn't give this function access to the component, so this doesn't point to it. Read other props from the function's first argument instead.
```
<script>
export default {
  props: {
    size: Number,
    sizes: {
      type: Array,
      default() {
        return [this.size];
      },
    },
  },
};
</script>
```
#12633 f65fe1e Thanks @dyc3! - Added the nursery rule noVueDeprecatedSlotAttribute, which reports the slot attribute in Vue templates. Vue 3 no longer uses this attribute to fill named slots, so use v-slot (or #) on a <template> element instead.
```
<template>
  <MyComponent>
    <template slot="header">Title</template>
  </MyComponent>
</template>
```
#12589 8ccb19a Thanks @dyc3! - Added the new nursery rule noVueDeprecatedVBindSync, which reports the .sync modifier on Vue v-bind directives. Vue 3 removed this modifier, so the rule suggests v-model with the same argument instead.
```
<MyComponent :title.sync="pageTitle" />
```
#12609 e1e102b Thanks @dyc3! - Added the new nursery rule noVueDeprecatedVOnNativeModifier, which disallows the .native modifier on Vue's v-on directive. Vue 3 removed this modifier.
```
<MyComponent @click.native="onClick" />
```
#12667 de354e7 Thanks @dyc3! - Added the new nursery rule noVueExcessiveProps, which reports Vue components that declare more props than the maxProps option allows. The default limit is 10.
```

<script setup lang="ts">
defineProps<{ title: string; subtitle: string; icon: string }>(); // reported
</script>
```
#12666 c3dc557 Thanks @dyc3! - Added the nursery rule noVueLoneTemplate, which reports <template> elements inside a Vue template that don't use v-if, v-else-if, v-else, v-for, or v-slot. Vue renders these as regular HTML <template> elements, so their content isn't shown.
```
<template>
  <template>
    <p>Hello</p>
  </template>
</template>
```
#12533 4b1089d Thanks @dyc3! - Added the new nursery rule noVueMixin, which reports the mixins option in Vue components. In Vue 3, composables are the recommended way to share logic between components. The rule is recommended and part of the vue domain.
```
<script>
export default {
  mixins: [counterMixin],
};
</script>
```
#12658 807e358 Thanks @dyc3! - Added the new nursery rule noVueMultipleObjectsInClass, which reports :class arrays in Vue templates that contain more than one object. Merge the conditional classes into a single object instead.
```
<template>
  <div :class="[{ active: isActive }, { disabled: isDisabled }]" />
</template>
```
#12564 78c1dd5 Thanks @dyc3! - Added the nursery rule noVueRefObjectReactivityLoss, which reports reads of a Vue ref's value that run only once, in the same function that creates the ref. Such a read copies the current value, and the copy doesn't update when the ref changes.
```
import { ref } from "vue";

const count = ref(0);
const doubled = count.value * 2;
```
#12517 5044c56 Thanks @dyc3! - Added the nursery rule noVueRestrictedCallAfterAwait, which reports calls to configured functions that come after an await in a Vue component's setup() function.

For example, with { "functions": [{ "module": "vue-i18n", "path": "useI18n" }] }, the following call is reported:
```
<script>
import { useI18n } from "vue-i18n";

export default {
  async setup() {
    await fetchUser();
    const { t } = useI18n();
    return { t };
  },
};
</script>
```
#12558 e898da4 Thanks @dyc3! - Added the nursery rule noVueRestrictedVOn, which reports v-on event listeners that are disallowed through the listeners option. An entry can match an event name, a set of modifiers, and an element. For example, with { "listeners": [{ "event": "click", "element": "MyButton" }] }, <MyButton @click="onClick" /> is now reported.
#12573 65c6b0b Thanks @dyc3! - Added the new nursery rule noVueTemplateKey, which disallows the key attribute on <template> elements in Vue files. A key on a <template> that also uses v-for is still allowed.
```
<template>
  <template :key="item.id"><div /></template>
</template>
```
#12629 2a34da1 Thanks @dyc3! - Added the new nursery rule noVueTemplateShadow, which disallows v-for and v-slot variables that hide a variable with the same name from an outer scope of a Vue template.
```
<template>
  <div v-for="item in groups">
    <span v-for="item in item.children">{{ item }}</span>
  </div>
</template>
```
#12610 40de561 Thanks @dyc3! - Added the new nursery rule noVueTextareaMustache, which disallows {{ }} text interpolation inside a Vue <textarea>. Vue doesn't support it there; use v-model instead.
```
<template>
  <textarea>{{ message }}</textarea>
</template>
```
#12665 7742209 Thanks @dyc3! - Added the new nursery rule noVueThisInBeforeRouteEnter, which reports this in the beforeRouteEnter navigation guard of a Vue component. Vue Router calls this guard before it creates the component, so this is undefined there.
```
<script>
export default {
  beforeRouteEnter(to, from, next) {
    this.loadUser(to.params.id); // reported
    next();
  },
};
</script>
```
#12620 70d7173 Thanks @dyc3! - Added the nursery rule noVueThisInTemplate, which reports this in Vue templates. Templates can read the properties of the component directly, so this.text can be written as text:
```
<template>
  <p>{{ this.text }}</p>
</template>
```
#12601 1d4ed92 Thanks @dyc3! - Added the new nursery rule noVueUndeclaredEmits, which reports events that a Vue component emits without declaring them in the emits option or in defineEmits().
```
<script setup>
const emit = defineEmits(["change"]);

emit("close"); // reported: "close" is not declared
</script>
```
#12583 4e870a8 Thanks @dyc3! - Added the nursery rule noVueUndeclaredProperties, which reports names that a Vue component uses but doesn't declare, in its template, in this.name, and in props.name.
```
<script setup>
const count = 0;
</script>

<template>
  
  <p>{{ cnt }}</p>
</template>
```
#12657 b45fe79 Thanks @dyc3! - Added the new nursery rule noVueUndeclaredSlots, which reports <slot> elements in Vue components written in TypeScript when the slot isn't declared with defineSlots() or with the slots option.
```
<script setup lang="ts">
defineSlots<{
  default(props: { msg: string }): any;
}>();
</script>

<template>
  <slot name="footer" /> 
</template>
```
#12789 041c800 Thanks @dyc3! - Added the new nursery rule noVueUselessTemplateAttributes, which reports attributes and directives that have no effect on a <template> element with v-if, v-else-if, v-else, v-for, or v-slot in Vue files. Vue renders only the content of such an element, so it ignores the other attributes.
```
<template>
  <template v-if="visible" class="heading">Title</template>
</template>
```
#12592 36531cc Thanks @dyc3! - Added the nursery rule noVueUselessVBind, which reports v-bind directives whose value is a fixed string. A plain attribute does the same thing.
```
<template>
  <div :id="'foo'" /> 
</template>
```
#12522 59838bb Thanks @dyc3! - Added the nursery rule noVueVForTemplateKeyOnChild, which reports a key placed on a child element of a <template v-for> instead of on the <template> tag.
```
<template>
  <template v-for="todo in todos">
    <TodoItem :key="todo.id" />
  </template>
</template>
```
#12516 2d9e57e Thanks @dyc3! - Added the nursery rule useAccessorPairs. The rule reports setters that have no matching getter in object literals, classes, and property descriptors.
```
const user = {
    set name(value) {
        this._name = value;
    },
};
```
#12756 1c6e3ef Thanks @dyc3! - Added the new nursery rule useObjectFromEntries, which reports code that builds an object from a list of key-value pairs with reduce(), a for...of loop, or _.fromPairs() instead of Object.fromEntries(). The functions option adds other helper functions to report.
```
const object = pairs.reduce((object, [key, value]) => ({ ...object, [key]: value }), {});
```
#12778 5432756 Thanks @dyc3! - Added the new nursery rule useSetSize, which reports code that copies a Set into an array only to read the array's length, and suggests reading the size property of the Set instead.
```
const uniqueCount = [...new Set(userIds)].length;
```
#12302 b0d3390 Thanks @dyc3! - Added the nursery rule useSvelteStoreInitialValue, which requires writable(), readable(), and derived() stores from svelte/store to be created with an initial value.
```
import { writable } from "svelte/store";

export const count = writable();
```
#12290 c973fed Thanks @dyc3! - Added the nursery rule useTailwindVariablesShorthand for JavaScript and HTML. It reports Tailwind CSS classes that read a CSS variable with [var()], and fixes them to the shorthand that Tailwind CSS v4 added.
```
<div className="bg-[var(--brand)]" />; // use `bg-(--brand)`
```
#12518 e9d9616 Thanks @dyc3! - Added the nursery rule useTanstackQueryStableQueryClient, which reports a TanStack Query QueryClient created inside a React component or custom hook. Such a client is created again on every render, and its cache starts empty each time.
```
import { QueryClient, QueryClientProvider } from "@tanstack/react-query";

function App() {
    const queryClient = new QueryClient();
    return <QueryClientProvider client={queryClient}><Home /></QueryClientProvider>;
}
```
#12650 0ddd08f Thanks @dyc3! - Added the nursery rule useVueBlockOrder, which enforces the order of the top-level blocks in Vue components. By default, <script> and <template> blocks come first, in any order, followed by <style> blocks. The order can be changed with the order option.
```
<style></style>
<script></script>
```
#12715 7863f32 Thanks @dyc3! - Added the nursery rule useVueBooleanPropTypeFirst, which requires Boolean to come first in the list of types of a Vue prop. When String comes before Boolean, a prop written in a template without a value is set to an empty string instead of true.
```
<script setup>
defineProps({
  disabled: [String, Boolean],
});
</script>
```

#12563 91ac4cb Thanks @dyc3! - Added the nursery rule useVueComputedPropertyReturn, which requires the getters of Vue computed properties to return a value on every path.

<script setup>
import { computed, ref } from "vue";

const count = ref(0);
const double = computed(() => {
  count.value * 2; // reported: the getter never returns a value
});
</script>

#12716 ae535ea Thanks @dyc3! - Added the new nursery rule useVueConsistentBooleanPropStyle, which enforces a consistent style for Vue component props set to true. By default, it requires the shorthand form; the style option can require the longhand form instead.
```
<template>
  <MyComponent :disabled="true" />
</template>
```
#12675 2a16d59 Thanks @dyc3! - Added the new nursery rule useVueConsistentDefineEmitsDeclaration, which enforces one declaration style for defineEmits in <script setup lang="ts">. By default, events must be declared with a type. The style option can instead require each event to be a property of that type, such as change: [id: number], or require an argument, such as defineEmits(["change"]).
```
<script setup lang="ts">
const emit = defineEmits(["change", "update"]);
</script>
```
#12612 ab53e4f Thanks @dyc3! - Added the nursery rule useVueConsistentPropNameCasing, which requires prop names in Vue components to use one casing style. By default, prop names must be in camelCase. The casing option switches the rule to snake_case.
```
<script setup>
defineProps({
  greeting_text: String,
});
</script>
```
#12608 0928a75 Thanks @dyc3! - Added the nursery rule useVueConsistentVForDelimiter, which requires the same word, in or of, between the item and the list in every Vue v-for directive. The default is in, and the delimiter option switches it to of.
```

<div v-for="item of items"></div>
```
#12611 d2df495 Thanks @dyc3! - Added the nursery rule useVueConsistentVSlotStyle, which enforces one style for Vue slots: #name, v-slot:name, or v-slot for the default slot. By default, it expects v-slot on a component and # on <template> elements.
```
<template>
  <MyComponent>
    <template v-slot:header>Tit
```

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

Configuration

📅 Schedule: (UTC)

Branch creation
- Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
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 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-11-01T01:36:27Z

⚠️ 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

[ERR_PNPM_PEER_DEP_ISSUES] Unmet peer dependencies

.
  ✕ unmet peer @vitest/coverage-v8
    Installed: 5.1.0
    Wanted:
      5.0.5:
        vitest@5.0.5

  ✕ unmet peer vitest
    Installed: 5.0.5
    Wanted:
      5.1.0:
        @vitest/coverage-v8@5.1.0

integration-tests/typescript-angular
  ✕ unmet peer typescript
    Installed: 7.0.2
    Wanted:
      ">=6.0 <6.1":
        @angular/build@22.2.3
        @angular/compiler-cli@22.2.3

packages/documentation
  ✕ unmet peer typescript
    Installed: 7.0.2
    Wanted:
      "^5.5.0 || ^6.0.0":
        twoslash@0.3.9
hint: To disable failing on peer dependency issues, add the following to pnpm-workspace.yaml in your project root:

  strictPeerDependencies: false

renovate Bot force-pushed the renovate/all branch 7 times, most recently from 0e39e5a to 07c8606 Compare November 7, 2026 13:00

renovate Bot force-pushed the renovate/all branch 3 times, most recently from babd058 to 1b117c8 Compare November 11, 2026 18:07

chore(deps): update all dependencies

b58ba35

renovate Bot force-pushed the renovate/all branch from 1b117c8 to b58ba35 Compare November 12, 2026 03:29

Navigation Menu

Repository navigation

chore(deps): update all dependencies - #566

chore(deps): update all dependencies#566
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all

renovate Bot commented Nov 1, 2026 •

edited

Loading

Uh oh!

renovate Bot commented Nov 1, 2026 •

edited

Loading

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

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

Uh oh!

Release Notes

v0.73.2

Bug Fixes

v2.6.5

Patch Changes

Configuration

Uh oh!

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

Uh oh!

⚠️ 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 Nov 1, 2026 •

edited

Loading

`v0.73.2`

`v2.6.5`

renovate Bot commented Nov 1, 2026 •

edited

Loading