Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 1, 2025

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

This PR contains the following updates:

Package Change Age Confidence
@eslint/js (source) ^9.39.1 -> ^9.39.2 age confidence
@reduxjs/toolkit (source) ^2.11.0 -> ^2.11.2 age confidence
@storybook/addon-onboarding (source) ^10.1.2 -> ^10.1.10 age confidence
@storybook/react-vite (source) ^10.1.2 -> ^10.1.10 age confidence
@testing-library/react ^16.3.0 -> ^16.3.1 age confidence
@types/chrome (source) ^0.1.31 -> ^0.1.32 age confidence
@types/express (source) ^5.0.5 -> ^5.0.6 age confidence
@types/node (source) ^24.10.1 -> ^24.10.4 age confidence
@typescript-eslint/eslint-plugin (source) ^8.48.0 -> ^8.50.0 age confidence
@typescript-eslint/parser (source) ^8.48.0 -> ^8.50.0 age confidence
anser ^2.3.3 -> ^2.3.5 age confidence
esbuild ^0.27.0 -> ^0.27.2 age confidence
eslint (source) ^9.39.1 -> ^9.39.2 age confidence
eslint-plugin-jest ^29.2.1 -> ^29.5.0 age confidence
express (source) ^5.1.0 -> ^5.2.1 age confidence
lodash-es (source) ^4.17.21 -> ^4.17.22 age confidence
pnpm (source) 10.24.0 -> 10.26.0 age confidence
prettier (source) 3.7.3 -> 3.7.4 age confidence
react (source) ^19.2.0 -> ^19.2.3 age confidence
react-dom (source) ^19.2.0 -> ^19.2.3 age confidence
react-is (source) ^19.2.0 -> ^19.2.3 age confidence
react-router-dom (source) ^7.9.6 -> ^7.11.0 age confidence
selenium-webdriver (source) ^4.38.0 -> ^4.39.0 age confidence
storybook (source) ^10.1.2 -> ^10.1.10 age confidence
ts-jest (source) ^29.4.5 -> ^29.4.6 age confidence
typescript-eslint (source) ^8.48.0 -> ^8.50.0 age confidence
vite (source) ^7.2.6 -> ^7.3.0 age confidence
webpack ^5.103.0 -> ^5.104.1 age confidence

Release Notes

eslint/eslint (@​eslint/js)

v9.39.2

Compare Source

reduxjs/redux-toolkit (@​reduxjs/toolkit)

v2.11.2

Compare Source

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

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

storybookjs/storybook (@​storybook/addon-onboarding)

v10.1.10

Compare Source

10.1.10

v10.1.9

Compare Source

v10.1.8

Compare Source

10.1.8

v10.1.7

Compare Source

10.1.7

v10.1.6

Compare Source

10.1.6

v10.1.5

Compare Source

10.1.5

v10.1.4

Compare Source

10.1.4

v10.1.3

Compare Source

10.1.3

storybookjs/storybook (@​storybook/react-vite)

v10.1.10

Compare Source

v10.1.9

Compare Source

v10.1.8

Compare Source

v10.1.7

Compare Source

v10.1.6

Compare Source

v10.1.5

Compare Source

v10.1.4

Compare Source

v10.1.3

Compare Source

testing-library/react-testing-library (@​testing-library/react)

v16.3.1

Compare Source

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.50.0

Compare Source

🚀 Features
  • eslint-plugin: [no-useless-default-assignment] add rule (#​11720)
❤️ Thank You
  • Josh Goldberg ✨
  • Ulrich Stark

You can read about our versioning strategy and releases on our website.

v8.49.0

Compare Source

🚀 Features
  • eslint-plugin: use Intl.Segmenter instead of graphemer (#​11804)
🩹 Fixes
  • deps: update dependency prettier to v3.7.2 (#​11820)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.48.1

Compare Source

🩹 Fixes
  • eslint-plugin: [restrict-template-expressions] check base types in allow list (#​11764, #​11759)
  • eslint-plugin: honor ignored base types on generic classes (#​11767)
  • eslint-plugin: [consistent-type-exports] check value flag before resolving alias (#​11769)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.50.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.49.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.48.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

IonicaBizau/anser (anser)

v2.3.5

Compare Source

Clean up files

v2.3.4

Compare Source

Fix grayscale palette colors returning undefined /cc #​83 -- thanks @​skipi 🍰

evanw/esbuild (esbuild)

v0.27.2

Compare Source

  • Allow import path specifiers starting with #/ (#​4361)

    Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

    This change was contributed by @​hybrist.

  • Automatically add the -webkit-mask prefix (#​4357, #​4358)

    This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

    /* Original code */
    main {
      mask: url(x.png) center/5rem no-repeat
    }
    
    /* Old output (with --target=chrome110) */
    main {
      mask: url(x.png) center/5rem no-repeat;
    }
    
    /* New output (with --target=chrome110) */
    main {
      -webkit-mask: url(x.png) center/5rem no-repeat;
      mask: url(x.png) center/5rem no-repeat;
    }

    This change was contributed by @​BPJEnnova.

  • Additional minification of switch statements (#​4176, #​4359)

    This release contains additional minification patterns for reducing switch statements. Here is an example:

    // Original code
    switch (x) {
      case 0:
        foo()
        break
      case 1:
      default:
        bar()
    }
    
    // Old output (with --minify)
    switch(x){case 0:foo();break;case 1:default:bar()}
    
    // New output (with --minify)
    x===0?foo():bar();
  • Forbid using declarations inside switch clauses (#​4323)

    This is a rare change to remove something that was previously possible. The Explicit Resource Management proposal introduced using declarations. These were previously allowed inside case and default clauses in switch statements. This had well-defined semantics and was already widely implemented (by V8, SpiderMonkey, TypeScript, esbuild, and others). However, it was considered to be too confusing because of how scope works in switch statements, so it has been removed from the specification. This edge case will now be a syntax error. See tc39/proposal-explicit-resource-management#215 and rbuckton/ecma262#14 for details.

    Here is an example of code that is no longer allowed:

    switch (mode) {
      case 'read':
        using readLock = db.read()
        return readAll(readLock)
    
      case 'write':
        using writeLock = db.write()
        return writeAll(writeLock)
    }

    That code will now have to be modified to look like this instead (note the additional { and } block statements around each case body):

    switch (mode) {
      case 'read': {
        using readLock = db.read()
        return readAll(readLock)
      }
      case 'write': {
        using writeLock = db.write()
        return writeAll(writeLock)
      }
    }

    This is not being released in one of esbuild's breaking change releases since this feature hasn't been finalized yet, and esbuild always tracks the current state of the specification (so esbuild's previous behavior was arguably incorrect).

v0.27.1

Compare Source

  • Fix bundler bug with var nested inside if (#​4348)

    This release fixes a bug with the bundler that happens when importing an ES module using require (which causes it to be wrapped) and there's a top-level var inside an if statement without being wrapped in a { ... } block (and a few other conditions). The bundling transform needed to hoist these var declarations outside of the lazy ES module wrapper for correctness. See the issue for details.

  • Fix minifier bug with for inside try inside label (#​4351)

    This fixes an old regression from version v0.21.4. Some code was introduced to move the label inside the try statement to address a problem with transforming labeled for await loops to avoid the await (the transformation involves converting the for await loop into a for loop and wrapping it in a try statement). However, it introduces problems for cross-compiled JVM code that uses all three of these features heavily. This release restricts this transform to only apply to for loops that esbuild itself generates internally as part of the for await transform. Here is an example of some affected code:

    // Original code
    d: {
      e: {
        try {
          while (1) { break d }
        } catch { break e; }
      }
    }
    
    // Old output (with --minify)
    a:try{e:for(;;)break a}catch{break e}
    
    // New output (with --minify)
    a:e:try{for(;;)break a}catch{break e}
  • Inline IIFEs containing a single expression (#​4354)

    Previously inlining of IIFEs (immediately-invoked function expressions) only worked if the body contained a single return statement. Now it should also work if the body contains a single expression statement instead:

    // Original code
    const foo = () => {
      const cb = () => {
        console.log(x())
      }
      return cb()
    }
    
    // Old output (with --minify)
    const foo=()=>(()=>{console.log(x())})();
    
    // New output (with --minify)
    const foo=()=>{console.log(x())};
  • The minifier now strips empty finally clauses (#​4353)

    This improvement means that finally clauses containing dead code can potentially cause the associated try statement to be removed from the output entirely in minified builds:

    // Original code
    function foo(callback) {
      if (DEBUG) stack.push(callback.name);
      try {
        callback();
      } finally {
        if (DEBUG) stack.pop();
      }
    }
    
    // Old output (with --minify --define:DEBUG=false)
    function foo(a){try{a()}finally{}}
    
    // New output (with --minify --define:DEBUG=false)
    function foo(a){a()}
  • Allow tree-shaking of the Symbol constructor

    With this release, calling Symbol is now considered to be side-effect free when the argument is known to be a primitive value. This means esbuild can now tree-shake module-level symbol variables:

    // Original code
    const a = Symbol('foo')
    const b = Symbol(bar)
    
    // Old output (with --tree-shaking=true)
    const a = Symbol("foo");
    const b = Symbol(bar);
    
    // New output (with --tree-shaking=true)
    const b = Symbol(bar);
eslint/eslint (eslint)

v9.39.2

Compare Source

jest-community/eslint-plugin-jest (eslint-plugin-jest)

v29.5.0

Compare Source

Features

29.4.1 (2025-12-14)

Bug Fixes
  • prefer-to-have-been-called-times: actually check that current matcher is toHaveLength (#​1878) (3415744)

v29.4.1

Compare Source

Features

29.4.1 (2025-12-14)

Bug Fixes
  • prefer-to-have-been-called-times: actually check that current matcher is toHaveLength (#​1878) (3415744)

v29.4.0

Compare Source

Features
  • create new prefer-to-have-been-called-times rule (281085a)
  • create new prefer-to-have-been-called rule (24e2acd)

v29.3.0

Compare Source

Features
  • prefer-expect-assertions: support basic uses of hasAssertions in beforeEach and afterEach hooks (#​1871) (eed9acb)

29.2.3 (2025-12-13)

Bug Fixes
  • prefer-expect-assertions: use correct word in error message (#​1873) (c48c48c)

29.2.2 (2025-12-12)

Bug Fixes

29.2.1 (2025-11-23)

Bug Fixes
  • valid-mock-module-path: report on ERR_PACKAGE_PATH_NOT_EXPORTED errors (#​1860) (6cd4e89)

v29.2.3

Compare Source

Bug Fixes
  • prefer-expect-assertions: use correct word in error message (#​1873) (c48c48c)

v29.2.2

Compare Source

Bug Fixes
expressjs/express (express)

v5.2.1

Compare Source

=======================

v5.2.0

Compare Source

========================

  • Security fix for CVE-2024-51999 (GHSA-pj86-cfqh-vqx6)
  • deps: body-parser@^2.2.1
  • A deprecation warning was added when using res.redirect with undefined arguments, Express now emits a warning to help detect calls that pass undefined as the status or URL and make them easier to fix.
lodash/lodash (lodash-es)

v4.17.22

Compare Source

pnpm/pnpm (pnpm)

v10.26.0

Compare Source

v10.25.0

Compare Source

prettier/prettier (prettier)

v3.7.4

Compare Source

diff

LWC: Avoid quote around interpolations (#​18383 by @​kovsu)
<!-- Input -->
<div foo={bar}>   </div>

<!-- Prettier 3.7.3 (--embedded-language-formatting off) -->
<div foo="{bar}"></div>

<!-- Prettier 3.7.4 (--embedded-language-formatting off) -->
<div foo={bar}></div>
TypeScript: Fix comment inside union type gets duplicated (#​18393 by @​fisker)
// Input
type Foo = (/** comment */ a | b) | c;

// Prettier 3.7.3
type Foo = /** comment */ (/** comment */ a | b) | c;

// Prettier 3.7.4
type Foo = /** comment */ (a | b) | c;
TypeScript: Fix unstable comment print in union type comments (#​18395 by @​fisker)
// Input
type X = (A | B) & (
  // comment
  A | B
);

// Prettier 3.7.3 (first format)
type X = (A | B) &
  (// comment
  A | B);

// Prettier 3.7.3 (second format)
type X = (
  | A
  | B // comment
) &
  (A | B);

// Prettier 3.7.4
type X = (A | B) &
  // comment
  (A | B);
facebook/react (react)

v19.2.3: 19.2.3 (December 11th, 2025)

Compare Source

React Server Components

v19.2.2: 19.2.2 (December 11th, 2025)

Compare Source

React Server Components

v19.2.1: 19.2.1 (December 3rd, 2025)

Compare Source

React Server Components
remix-run/react-router (react-router-dom)

v7.11.0

Compare Source

Patch Changes

v7.10.1

Compare Source

Patch Changes

v7.10.0

Compare Source

Patch Changes
SeleniumHQ/selenium (selenium-webdriver)

v4.39.0

Compare Source

kulshekhar/ts-jest (ts-jest)

v29.4.6

Compare Source

Bug Fixes
typescript-eslint/typescript-eslint (typescript-eslint)

v8.50.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.49.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.48.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

vitejs/vite (vite)

v7.3.0

Compare Source

Please refer to CHANGELOG.md for details.

v7.2.7

Compare Source

webpack/webpack (webpack)

[v5.104.1](https://redirect.github.com/webpack/webpack/blob/HEAD/CHANGELOG.md#51


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help 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
Copy link

changeset-bot bot commented Dec 1, 2025

⚠️ No Changeset found

Latest commit: 1fd38f6

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

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from f6c3a4b to 3198936 Compare December 8, 2025 17:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 14 times, most recently from a3a7f02 to d643419 Compare December 15, 2025 17:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 5008962 to 8c551fc Compare December 16, 2025 18:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from a9bf707 to 75fb466 Compare December 17, 2025 20:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 75fb466 to 1fd38f6 Compare December 18, 2025 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant