fix(deps): update all dependencies #2088

renovate · 2025-11-24T00:39:11Z

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`2.3.5` -> `2.3.8`	devDependencies	patch
@changesets/changelog-github (source)	`0.5.1` -> `0.5.2`	devDependencies	patch
@changesets/cli (source)	`2.29.7` -> `2.29.8`	devDependencies	patch
@commitlint/cli (source)	`20.1.0` -> `20.2.0`	devDependencies	minor
@commitlint/config-conventional (source)	`20.0.0` -> `20.2.0`	devDependencies	minor
@reduxjs/toolkit (source)	`2.10.1` -> `2.11.1`	dependencies	minor
@types/lodash (source)	`4.17.20` -> `4.17.21`	devDependencies	patch
@types/node (source)	`22.19.1` -> `22.19.3`	devDependencies	patch
@types/react (source)	`19.2.5` -> `19.2.7`	devDependencies	patch
@types/react (source)	`19.2.5` -> `19.2.7`	dependencies	patch
@types/react (source)	`19.2.5` -> `19.2.7`	pnpm.overrides	patch
@vitejs/plugin-react (source)	`5.1.1` -> `5.1.2`	devDependencies	patch
core-js (source)	`3.46.0` -> `3.47.0`	devDependencies	minor
jsdom	`27.2.0` -> `27.3.0`	devDependencies	minor
lint-staged	`16.2.6` -> `16.2.7`	devDependencies	patch
node (source)	`24.11` -> `24.12`		minor
node (source)	`24.11.1` -> `24.12.0`		minor
pnpm (source)	`10.22.0` -> `10.25.0`	packageManager	minor
react (source)	`19.2.0` -> `19.2.3`	dependencies	patch
react (source)	`19.2.0` -> `19.2.3`	devDependencies	patch
react-dom (source)	`19.2.0` -> `19.2.3`	dependencies	patch
react-dom (source)	`19.2.0` -> `19.2.3`	devDependencies	patch
react-is (source)	`19.2.0` -> `19.2.3`	dependencies	patch
rimraf	`6.1.0` -> `6.1.2`	devDependencies	patch
turbo (source)	`2.6.1` -> `2.6.3`	devDependencies	patch
vite (source)	`7.2.2` -> `7.2.7`	devDependencies	patch

Release Notes

biomejs/biome (@biomejs/biome)

`v2.3.8`

Compare Source

Patch Changes

#8188 4ca088c Thanks @ematipico! - Fixed #7390, where Biome couldn't apply the correct configuration passed via --config-path.

If you have multiple root configuration files, running any command with --config-path will now apply the chosen configuration file.
#8171 79adaea Thanks @dibashthapa! - Added the new rule noLeakedRender. This rule helps prevent potential leaks when rendering components that use binary expressions or ternaries.

For example, the following code triggers the rule because the component would render 0:
```
const Component = () => {
  const count = 0;
  return <div>{count && <span>Count: {count}</span>}</div>;
};
```
#8116 b537918 Thanks @Netail! - Added the nursery rule noDuplicatedSpreadProps. Disallow JSX prop spreading the same identifier multiple times.

Invalid:
```
<div {...props} something="else" {...props} />
```
#8256 f1e4696 Thanks @cormacrelf! - Fixed a bug where logs were discarded (the kind from --log-level=info etc.). This is a regression introduced after an internal refactor that wasn't adequately tested.
#8226 3f19b52 Thanks @dyc3! - Fixed #8222: The HTML parser, with Vue directives enabled, can now parse v-slot shorthand syntax, e.g. <template #foo>.
#8007 182ecdc Thanks @brandonmcconnell! - Added support for dollar-sign-prefixed filenames in the useFilenamingConvention rule.

Biome now allows filenames starting with the dollar-sign (e.g. $postId.tsx) by default to support naming conventions used by frameworks such as TanStack Start for file-based-routing.
#8218 91484d1 Thanks @hirokiokada77! - Added the noMultiStr rule, which disallows creating multiline strings by escaping newlines.

Invalid:
```
const foo =
  "Line 1\n\
Line 2";
```
Valid:
```
const foo = "Line 1\nLine 2";
const bar = `Line 1
Line 2`;
```

#8225 98ca2ae Thanks @ongyuxing! - Fixed #7806: Prefer breaking after the assignment operator for conditional types with generic parameters to match Prettier.

-type True = unknown extends Type<
-  "many",
-  "generic",
-  "parameters",
-  "one",
-  "two",
-  "three"
->
-  ? true
-  : false;
+type True =
+  unknown extends Type<"many", "generic", "parameters", "one", "two", "three">
+    ? true
+    : false;

#6765 23f7855 Thanks @emilyinure! - Fixed #6569: Allow files to export from themselves with noImportCycles.

This means the following is now allowed:

// example.js
export function example() {
  return 1;
}

// Re-exports all named exports from the current module under a single namespace
// and then imports the namespace from the current module.
// Allows for encapsulating functions/variables into a namespace instead
// of using a static class.
export * as Example from "./example.js";

import { Example } from "./example.js";

#8214 68c052e Thanks @hirokiokada77! - Added the noEqualsToNull rule, which enforces the use of === and !== for comparison with null instead of == or !=.

Invalid:
```
foo == null;
foo != null;
```
Valid:
```
foo === null;
foo !== null;
```
#8219 793bb9a Thanks @dyc3! - Fixed #8190: The HTML parser will now parse Vue event handlers that contain : correctly, e.g. @update:modelValue="onUpdate".
#8259 4a9139b Thanks @hirokiokada77! - Fixed #8254: The noParameterAssign rule with propertyAssignment: "deny" was incorrectly reporting an error when a function parameter was used on the right-hand side of an assignment to a local variable's property.

The rule should only flag assignments that modify the parameter binding or its properties (L-value), not the use of its value.

Valid:
```
(input) => {
  const local = { property: 0 };
  local.property = input;
};
```
#8201 cd2edd7 Thanks @Netail! - Added the nursery rule noTernary. Disallow ternary operators.

Invalid:
```
const foo = isBar ? baz : qux;
```
#8172 de98933 Thanks @JeremyMoeglich! - Fixed #8145: handling of large hex literals, which previously caused both false positives and false negatives.

This affects noPrecisionLoss and noConstantMathMinMaxClamp.
#8210 7b44e9e Thanks @Netail! - Corrected rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8213 e430555 Thanks @ruidosujeira! - Fixed #8209: Recognized formatting capability when either range or on-type formatting is supported, not only full-file formatting. This ensures editors and the language server correctly detect formatting support in files like JSONC.
#8202 6f49d95 Thanks @hirokiokada77! - Fixed #8079: Properly handle name and value metavariables for JsxAttribute GritQL queries.

The following biome search command no longer throws an error:
```
biome search 'JsxAttribute($name, $value) as $attr where { $name <: "style" }'
```
#8276 f7e836f Thanks @hirokiokada77! - Added the noProto rule, which disallows the use of the __proto__ property for getting or setting the prototype of an object.

Invalid:
```
obj.__proto__ = a;
const b = obj.__proto__;
```
Valid:
```
const a = Object.getPrototypeOf(obj);
Object.setPrototypeOf(obj, b);
```

`v2.3.7`

Compare Source

Patch Changes

#8169 7fdcec8 Thanks @arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.
#8157 12d5b42 Thanks @Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

The following code is no longer reported as invalid:
```
class classA {
  C = C;
}
const C = 0;
```
#8178 6ba4157 Thanks @dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.
```
- <Component v-else:property="123" />
+ <Component v-else :property="123" />
```
#8088 0eb08e8 Thanks @db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @linkcode and @linkplain (previously supported @link and @see).

The following code will no longer be a false positive:
```
import type { a } from "a"

/**
 * {@&#8203;linkcode a}
 */
function func() {}
```
#8119 8d64655 Thanks @ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn't triggered for variables that are mutated inside a module.

This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as "inspired".

In the following example, hey starts as false, but then it's assigned to a string. The rule isn't triggered inside the if check.
```
let hey = false;

function test() {
  hey = "string";
}

if (hey) {
}
```
#8149 e0a02bf Thanks @Netail! - Fixed #8144: Improve noSyncScripts, ignore script tags with type="module" as these are always non-blocking.
#8182 e9f068e Thanks @hirokiokada77! - Fixed #7877: Range suppressions now handle suppressed categories properly.

Valid:
```
// biome-ignore-start lint: explanation
const foo = 1;
// biome-ignore-end lint: explanation
```
#8111 bf1a836 Thanks @ryan-m-walker! - Added support for parsing and formatting the CSS if function.

Example
```
.basic-style {
  color: if(style(--scheme: dark): #eeeeee; else: #&#8203;000000;);
}
```
#8173 7fc07c1 Thanks @ematipico! - Fixed #8138 by reverting an internal refactor that caused a regression to the rule noUnusedPrivateClassMembers.
#8119 8d64655 Thanks @ematipico! - Improved the type inference engine, by resolving types for variables that are assigned to multiple values.
#8158 fb1458b Thanks @dyc3! - Added the useVueValidVText lint rule to enforce valid v-text directives. The rule reports when v-text has an argument, has modifiers, or is missing a value.

Invalid:
```
<div v-text />

<div v-text:aaa="foo" />

<div v-text.bbb="foo" />

```
#8158 fb1458b Thanks @dyc3! - Fixed useVueValidVHtml so that it will now flag empty strings, e.g. v-html=""
#7078 bb7a15c Thanks @emilyinure! - Fixed #6675: Now only flags
noAccumulatingSpread on Object.assign when a new object is being allocated on
each iteration. Before, all cases using Object.assign with reduce parameters
were warned despite not making new allocations.

The following code will no longer be a false positive:
```
foo.reduce((acc, bar) => Object.assign(acc, bar), {});
```
The following cases which do make new allocations will continue to warn:
```
foo.reduce((acc, bar) => Object.assign({}, acc, bar), {});
```
#8175 0c8349e Thanks @ryan-m-walker! - Fixed CSS formatting of dimension units to use correct casing for Q, Hz and kHz.

Before:
```
.cssUnits {
  a: 1Q;
  b: 1Hz;
  c: 1kHz;
}
```
After:
```
.cssUnits {
  a: 1Q;
  b: 1Hz;
  c: 1kHz;
}
```

`v2.3.6`

Compare Source

Patch Changes

#8100 82b9a8e Thanks @Netail! - Added the nursery rule useFind. Enforce the use of Array.prototype.find() over Array.prototype.filter() followed by [0] when looking for a single result.

Invalid:
```
[1, 2, 3].filter((x) => x > 1)[0];

[1, 2, 3].filter((x) => x > 1).at(0);
```
#8118 dbc7021 Thanks @hirokiokada77! - Fixed #8117: useValidLang now accepts valid BCP 47 language tags with script subtags.

Valid:
```
<html lang="zh-Hans-CN"></html>
```
#7672 f1d5725 Thanks @Netail! - Added the nursery rule useConsistentGraphqlDescriptions, requiring all descriptions to follow the same style (either block or inline) inside GraphQL files.

Invalid:
```
enum EnumValue {
  "this is a description"
  DEFAULT
}
```
Valid:
```
enum EnumValue {
  """
  this is a description
  """
  DEFAULT
}
```
#8026 f102661 Thanks @matanshavit! - Fixed #8004: noParametersOnlyUsedInRecursion now correctly detects recursion by comparing function bindings instead of just names.

Previously, the rule incorrectly flagged parameters when a method had the same name as an outer function but called the outer function (not itself):
```
function notRecursive(arg) {
  return arg;
}

const obj = {
  notRecursive(arg) {
    return notRecursive(arg); // This calls the outer function, not the method itself
  },
};
```
Biome now properly distinguishes between these cases and will not report false positives.
#8097 5fc5416 Thanks @dyc3! - Added the nursery rule noVueVIfWithVFor. This rule disallows v-for and v-if on the same element.
```

<div v-for="item in items" v-if="item.isActive">
  {{ item.name }}
</div>
```
#8085 7983940 Thanks @Netail! - Added the nursery rule noForIn. Disallow iterating using a for-in loop.

Invalid:
```
for (const i in array) {
  console.log(i, array[i]);
}
```
#8086 2b41e82 Thanks @matanshavit! - Fixed #8045: The noNestedTernary rule now correctly detects nested ternary expressions even when they are wrapped in parentheses (e.g. foo ? (bar ? 1 : 2) : 3).

Previously, the rule would not flag nested ternaries like foo ? (bar ? 1 : 2) : 3 because the parentheses prevented detection. The rule now looks through parentheses to identify nested conditionals.

Previously not detected (now flagged):
```
const result = foo ? (bar ? 1 : 2) : 3;
```
Still valid (non-nested with parentheses):
```
const result = foo ? bar : baz;
```
#8075 e403868 Thanks @YTomm! - Fixed #7948: The useReadonlyClassProperties code fix when checkAllProperties is enabled will no longer insert a newline after readonly and the class property.
#8102 47d940e Thanks @lucasweng! - Fixed #8027. useReactFunctionComponents no longer reports class components that implement componentDidCatch using class expressions.

The rule now correctly recognizes error boundaries defined as class expressions:
```
const ErrorBoundary = class extends Component {
  componentDidCatch(error, info) {}

  render() {
    return this.props.children;
  }
};
```
#8097 5fc5416 Thanks @dyc3! - Added the nursery rule useVueHyphenatedAttributes, which encourages using kebab case for attribute names, per the Vue style guide's recommendations.
```

<MyComponent myProp="value" />


<MyComponent my-prop="value" />
```

#8108 0f0a658 Thanks @Netail! - Added the nursery rule noSyncScripts. Prevent the usage of synchronous scripts.

Invalid:

<script src="https://third-party-script.js" />

Valid:

<script src="https://third-party-script.js" async />
<script src="https://third-party-script.js" defer />

#8098 1fdcaf0 Thanks @Jayllyz! - Added documentation URLs to rule descriptions in the JSON schema.
#8097 5fc5416 Thanks @dyc3! - Fixed an issue with the HTML parser where it would treat Vue directives with dynamic arguments as static arguments instead.
#7684 f4433b3 Thanks @vladimir-ivanov! - Changed noUnusedPrivateClassMembers to align more fully with meaningful reads.

This rule now distinguishes more carefully between writes and reads of private class members.
- A meaningful read is any access that affects program behavior.
- For example, this.#x += 1 both reads and writes #x, so it counts as usage.
- Pure writes without a read (e.g. this.#x = 1 with no getter) are no longer treated as usage.
This change ensures that private members are only considered “used” when they are actually read in a way that influences execution.

Invalid examples (previously valid)
```
class UsedMember {
  set #x(value) {
    doSomething(value);
  }

  foo() {
    // This assignment does not actually read #x, because there is no getter.
    // Previously, this was considered a usage, but now it’s correctly flagged.
    this.#x = 1;
  }
}
```
Valid example (Previously invalid)
```
class Foo {
  #usedOnlyInWriteStatement = 5;

  method() {
    // This counts as a meaningful read because we both read and write the value.
    this.#usedOnlyInWriteStatement += 42;
  }
}
```
#7684 f4433b3 Thanks @vladimir-ivanov! - Improved detection of used private class members

The analysis for private class members has been improved: now the tool only considers a private member “used” if it is actually referenced in the code.
- Previously, some private members might have been reported as used even if they weren’t actually accessed.
- With this change, only members that are truly read or called in the code are counted as used.
- Members that are never accessed will now be correctly reported as unused.
This makes reports about unused private members more accurate and helps you clean up truly unused code.

Example (previously valid)
```
type YesNo = "yes" | "no";

export class SampleYesNo {
  private yes: () => void;
  private no: () => void;
  private dontKnow: () => void; // <- will now report as unused

  on(action: YesNo): void {
    this[action]();
  }
}
```
#7681 b406db6 Thanks @kedevked! - Added the new lint rule, useSpread, ported from the ESLint rule prefer-spread.

This rule enforces the use of the spread syntax (...) over Function.prototype.apply() when calling variadic functions, as spread syntax is generally more concise and idiomatic in modern JavaScript (ES2015+).

The rule provides a safe fix.

Invalid

Math.max.apply(Math, args);
foo.apply(undefined, args);
obj.method.apply(obj, args);

Valid

Math.max(...args);
foo(...args);
obj.method(...args);

// Allowed: cases where the `this` binding is intentionally changed
foo.apply(otherObj, args);

#7287 aa55c8d Thanks @ToBinio! - Fixed #7205: The noDuplicateTestHooks rule now treats chained describe variants (e.g., describe.each/for/todo) as proper describe scopes, eliminating false positives.

The following code will no longer be a false positive:

describe("foo", () => {
  describe.for([])("baz", () => {
    beforeEach(() => {});
  });

  describe.todo("qux", () => {
    beforeEach(() => {});
  });

  describe.todo.each([])("baz", () => {
    beforeEach(() => {});
  });
});

#8013 0c0edd4 Thanks @Jayllyz! - Added the GraphQL nursery rule useUniqueGraphqlOperationName. This rule ensures that all GraphQL operations within a document have unique names.

Invalid:

query user {
  user {
    id
  }
}

query user {
  user {
    id
    email
  }
}

Valid:

query user {
  user {
    id
  }
}

query userWithEmail {
  user {
    id
    email
  }
}

#8084 c2983f9 Thanks @dyc3! - Fixed #8080: The HTML parser, when parsing Vue, can now properly handle Vue directives with no argument, modifiers, or initializer (e.g. v-else). It will no longer treat subsequent valid attributes as bogus.
```
<p v-else class="flex">World</p>

```
#8104 041196b Thanks @Conaclos! - Fixed noInvalidUseBeforeDeclaration.
The rule no longer reports a use of an ambient variable before its declarations.
The rule also completely ignores TypeScript declaration files.
The following code is no longer reported as invalid:
```
CONSTANT;
declare const CONSTANT: number;
```
#8060 ba7b076 Thanks @dyc3! - Added the nursery rule useVueValidVBind, which enforces the validity of v-bind directives in Vue files.

Invalid v-bind usages include:
```
<Foo v-bind />

<Foo v-bind:foo />

<Foo v-bind:foo.bar="baz" />

```
#8113 fb8e3e7 Thanks @Conaclos! - Fixed noInvalidUseBeforeDeclaration.
The rule now reports invalid use of classes, enums, and TypeScript's import-equals before their declarations.

The following code is now reported as invalid:
```
new C();
class C {}
```
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVElseIf to enforce valid v-else-if directives in Vue templates. This rule reports invalid v-else-if directives with missing conditional expressions or when not preceded by a v-if or v-else-if directive.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVElse to enforce valid v-else directives in Vue templates. This rule reports v-else directives that are not preceded by a v-if or v-else-if directive.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVHtml to enforce valid usage of the v-html directive in Vue templates. This rule reports v-html directives with missing expressions, unexpected arguments, or unexpected modifiers.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVIf to enforce valid v-if directives in Vue templates. It disallows arguments and modifiers, and ensures a value is provided.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVOn to enforce valid v-on directives in Vue templates. This rule reports invalid v-on / shorthand @ directives with missing event names, invalid modifiers, or missing handler expressions.

changesets/changesets (@changesets/changelog-github)

`v0.5.2`

Compare Source

conventional-changelog/commitlint (@commitlint/cli)

`v20.2.0`

Compare Source

Note: Version bump only for package @commitlint/cli

conventional-changelog/commitlint (@commitlint/config-conventional)

`v20.2.0`

Compare Source

Note: Version bump only for package @commitlint/config-conventional

reduxjs/redux-toolkit (@reduxjs/toolkit)

`v2.11.1`

Compare Source

This bugfix release fixes an issue with our internal AbortSignal handling that was reported as causing an error in a rare reset situation. We've also restructured our publishing process to use NPM Trusted Publishing, and updated our TS support matrix to only support TS 5.4+.

Changelog

Publishing Changes

We've previously done most of our releases semi-manually locally, with various release process CLI tools. With the changes to NPM publishing security and the recent wave of NPM attacks, we've updated our publishing process to solely use NPM Trusted Publishing via workflows. We've also done a hardening pass on our own CI setup.

We had done a couple releases via CI workflows previously, and later semi-manual releases caused PNPM to warn that RTK was no longer trusted. This release should be trusted and will resolve that issue.

Thanks to the e18e folks and their excellent guide at https://e18e.dev/docs/publishing for making this process easier!

TS Support Matrix Updates

We've previously mentioned rolling changes to our TS support matrix in release notes, but didn't officially document our support policy. We've added a description of the support policy (last 2 years of TS releases, matching DefinitelyTyped) and the current oldest TS version we support in the docs:

As of today, we've updated the support matrix to be TS 5.4+ . As always, it's possible RTK will work if you're using an earlier version of TS, but we don't test against earlier versions and don't support any issues with those versions.

We have run an initial test with the upcoming TS 7.0 native tsgo release. We found a couple minor issues with our own TS build and test setup, but no obvious issues with using RTK with TS 7.0.

Bug Fixes

A user reported a rare edge case where the combination of resetApiState and retry() could lead to an error calling an AbortController. We've restructured our AbortController handling logic to avoid that (and simplified a bit of our internals in the process).

What's Changed

Use trusted publishing and harden workflows by @markerikson in #5152
Update TS typecheck matrix and add TS native job by @markerikson in #5155
Officially document TS support by @markerikson in #5158
Tweaks to AbortSignal logic by @EskiMojo14 in #5150

Full Changelog: reduxjs/redux-toolkit@v2.11.0...v2.11.1

`v2.11.0`

Compare Source

vitejs/vite-plugin-react (@vitejs/plugin-react)

`v5.1.2`

Compare Source

zloirock/core-js (core-js)

`v3.47.0`

Compare Source

Changes v3.46.0...v3.47.0 (117 commits)
JSON.parse source text access proposal :
- Built-ins:
  - JSON.isRawJSON
  - JSON.parse
  - JSON.rawJSON
  - JSON.stringify
- Moved to stable ES, November 2025 TC39 meeting
- Added es. namespace modules, /es/ and /stable/ namespaces entries
- Reworked JSON.stringify internals
Iterator sequencing proposal:
- Built-ins:
  - Iterator.concat
- Moved to stable ES, November 2025 TC39 meeting
- Added es. namespace modules, /es/ and /stable/ namespaces entries
Joint iteration proposal:
- Built-ins:
  - Iterator.zip
  - Iterator.zipKeyed
- Moved to stage 3, November 2025 TC39 meeting
- Added /actual/ namespace entries, unconditional forced replacement changed to feature detection
Fixed increasing .size in URLSearchParams.prototype.append polyfill in IE8-
Compat data improvements:
- Iterator.concat marked as shipped in FF147
- Map upsert proposal features marked as shipped in Safari 26.2
- Math.sumPrecise marked as shipped in Safari 26.2
- Uint8Array.{ fromBase64, prototype.setFromBase64 } marked as fixed in Safari 26.2
- Missed Explicit Resource Management features added in Bun 1.3.0
- Added Oculus Quest Browser 41 compat data mapping
- Added Electron 40 compat data mapping

jsdom/jsdom (jsdom)

`v27.3.0`

Compare Source

Improved CSS parsing and CSSOM object APIs via updates to @acemir/cssom. (acemir)

lint-staged/lint-staged (lint-staged)

`v16.2.7`

Compare Source

Patch Changes

#1711 ef74c8d Thanks @iiroj! - Do not display a "failed to spawn" error message when a task fails normally. This message is reserved for when the task didn't run because spawning it failed.

nodejs/node (node)

[`v24.12.0`](https://redirect.github.c

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

changeset-bot · 2025-11-24T00:39:15Z

⚠️ No Changeset found

Latest commit: 86a5df7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

socket-security · 2025-11-24T00:39:45Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Supply Chain Security	Quality	Maintenance
@changesets/changelog-github@0.5.1 ⏵ 0.5.2		⁺¹
@commitlint/cli@20.1.0 ⏵ 20.2.0			^-1
@types/react@19.2.5 ⏵ 19.2.7		⁺¹
@types/lodash@4.17.20 ⏵ 4.17.21		⁺¹
vite@7.2.2 ⏵ 7.2.7	^-1	⁺¹
react@19.2.0 ⏵ 19.2.3
turbo@2.6.1 ⏵ 2.6.3		^-1	⁺²
core-js@3.46.0 ⏵ 3.47.0	⁺¹	⁺¹	^-1
rimraf@6.1.0 ⏵ 6.1.2			⁺⁴
@commitlint/config-conventional@20.0.0 ⏵ 20.2.0			^-1
react-dom@19.2.0 ⏵ 19.2.3
@changesets/cli@2.29.7 ⏵ 2.29.8			⁺²
lint-staged@16.2.6 ⏵ 16.2.7	⁺¹
@reduxjs/toolkit@2.10.1 ⏵ 2.11.1		⁺¹	⁺²
jsdom@27.2.0 ⏵ 27.3.0		⁺¹
@vitejs/plugin-react@5.1.1 ⏵ 5.1.2
react-is@19.2.0 ⏵ 19.2.3
@biomejs/biome@2.3.5 ⏵ 2.3.8	⁺¹		^-1
@types/node@22.19.1 ⏵ 22.19.3	⁺¹	⁺²⁰	⁺⁶

View full report

codecov · 2025-11-24T00:41:37Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.37%. Comparing base (fc58242) to head (86a5df7).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2088      +/-   ##
==========================================
- Coverage   91.42%   91.37%   -0.06%     
==========================================
  Files          94       94              
  Lines        3826     3826              
  Branches      565      567       +2     
==========================================
- Hits         3498     3496       -2     
  Misses        317      317              
- Partials       11       13       +2

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

renovate bot added the 🤖 Dependencies label Nov 24, 2025

renovate-approve bot approved these changes Nov 24, 2025

View reviewed changes

renovate bot force-pushed the renovate/all branch 2 times, most recently from 3e4b246 to c15d0f0 Compare November 27, 2025 16:57

renovate bot force-pushed the renovate/all branch 9 times, most recently from 6508039 to b0c7c85 Compare December 8, 2025 05:43

renovate bot force-pushed the renovate/all branch 6 times, most recently from fc6bc9b to afda111 Compare December 12, 2025 03:40

fix(deps): update all dependencies

86a5df7

renovate bot force-pushed the renovate/all branch from afda111 to 86a5df7 Compare December 14, 2025 02:42

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(deps): update all dependencies #2088

fix(deps): update all dependencies #2088

renovate bot commented Nov 24, 2025 •

edited

Loading

Uh oh!

changeset-bot bot commented Nov 24, 2025 •

edited

Loading

Uh oh!

socket-security bot commented Nov 24, 2025 •

edited

Loading

Uh oh!

codecov bot commented Nov 24, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

fix(deps): update all dependencies #2088

Are you sure you want to change the base?

fix(deps): update all dependencies #2088

Conversation

renovate bot commented Nov 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Invalid

Valid

Changelog

Publishing Changes

TS Support Matrix Updates

Bug Fixes

What's Changed

Patch Changes

[v24.12.0](https://redirect.github.c

Configuration

Uh oh!

changeset-bot bot commented Nov 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

socket-security bot commented Nov 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov bot commented Nov 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Nov 24, 2025 •

edited

Loading

[`v24.12.0`](https://redirect.github.c

changeset-bot bot commented Nov 24, 2025 •

edited

Loading

socket-security bot commented Nov 24, 2025 •

edited

Loading

codecov bot commented Nov 24, 2025 •

edited

Loading