Skip to content

chore(deps): update dependency @reduxjs/toolkit to v2.15.0 - #856

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/reduxjs-toolkit-2.x-lockfile
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/reduxjs-toolkit-2.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@reduxjs/toolkit (source) 2.10.1 → 2.15.0 age confidence

Release Notes

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

v2.15.0

Compare Source

This feature release gives each store its own RTK Query middleware runtime, makes initiate() promises resolve with their own request's result, adds several new options to RTK Query, improves listener middleware fork child capabilities, improves readability for several RTK type definitions, and fixes a variety of RTKQ bugs.

This release continues the work from our roadmap to Redux Toolkit 3.0. Several of the RTK Query changes here are bug fixes that change behavior in edge cases, so please read the "Behavior Changes" notes below.

Changelog

Per-Store RTK Query Runtime

RTK Query's middleware keeps a lot of state outside the Redux store in order to manage requests and cache lifetimes: subscriber counts, running requests, poll and cache collection timers, and cache lifecycle promises. That state used to live in closures shared by every store that used the same api object. That was fine for a single client-side store, but caused problems for SSR and tests, where many stores share one api.

Each store now gets its own consolidated internal runtime state, created by the API middleware. resetApiState now calls runtime.reset(), which clears every subscriber, timer and cache lifecycle for that store, aborts running requests, and clears pending tag invalidations. It no longer touches other stores.

Internally, each cache key now has one record that tracks its running request, timers and lifecycle, and all removals go through a single path. That made the initiate() fixes below possible.

The missing-middleware check now runs once per store, and looks for the store's runtime instead of dispatching an internal action. This check is stricter: an api whose middleware is missing now throws even if another api with the same reducerPath has its middleware in the store.

initiate() Promises Resolve With Their Own Result

We had several long-standing reports (#​5506, #​4833, #​5173, #​5346) that the promise from initiate() could resolve with undefined, or with a different request's data. That happened when the cache entry was removed, reset, invalidated or replaced while the request was running, because the promise read the cache entry after the request finished instead of the request's own result.

We've done a thorough review of the promise resolution logic to analyze the current intended behavior, ran separate formal modeling of the derived behavior to help uncover gaps, updated the model to fill those gaps, and reworked that logic to fully comply with the improved expected behavior.

Each initiate() promise now resolves with its own request's result, captured as soon as that request's fulfilled or rejected action reaches the store.

Thanks to @​kkatalz (#​5474) and @​rajanpanth (#​5347): both PRs fixed part of this, and their tests are included.

Behavior Changes

These ship in 2.x as bug fixes, but code that depended on the old behavior will see a difference:

  • Removing a cache entry while its request runs now aborts that request. This covers removeQueryResult, a lazy query's reset(), cache collection, and resetApiState. The initiate() promise resolves with isError: true and an AbortError whose message is 'removed' or 'reset'. That means unwrap() now rejects in this case, where it used to resolve with stale or missing data. The plain promise still never rejects.

  • queryFulfilled in onQueryStarted rejects in the same case. If your onQueryStarted does await queryFulfilled without a try/catch, you'll now get an unhandled rejection when the entry is removed mid-request. Wrap it:

    async onQueryStarted(arg, { queryFulfilled }) {
      try {
        const { data } = await queryFulfilled
        // ...
      } catch {
        // request failed, or the cache entry was removed while it ran
      }
    }
  • Invalidating an entry that has a running request (by tags, or a focus/reconnect refetch) now waits for that request to finish. The running request's promise gets its own result, and then the entry refetches if it has subscribers, or is removed if it doesn't.

  • A refetch while a request is running joins that request instead of starting another one. initiate() also joins a running upsertQueryData.

  • A pending entry restored from persisted state, with no request actually running, now fetches again.

onCacheEntryAdded has a new getCacheEntryRemovedReason() function that returns 'reset' if the entry was removed by resetApiState, 'removed' for any other removal, or undefined while the entry is still in the cache. cacheEntryRemoved stays a Promise<void>, since many apps declare that type in their own handler types.

async onCacheEntryAdded(arg, { cacheEntryRemoved, getCacheEntryRemovedReason }) {
  const connection = openConnection(arg)
  await cacheEntryRemoved
  if (getCacheEntryRemovedReason() !== 'reset') {
    connection.unsubscribe()
  }
  connection.close()
}
startReason for Query Requests

We've had a request (#​4757) to know why a query is fetching. For example, a queryFn might want to read from the primary database after a tag invalidation, instead of a replica that may be behind.

baseQuery / queryFn (via BaseQueryApi), fetchBaseQuery's prepareHeaders, onQueryStarted and onCacheEntryAdded now receive a startReason. The new QueryStartReason type is 'initial' | 'refetch' | 'invalidation' | 'poll' | 'focus' | 'reconnect' | 'upsert' | 'hydrate' | 'nextPage' | 'previousPage'.

const api = createApi({
  baseQuery: fetchBaseQuery({
    baseUrl: '/api',
    prepareHeaders: (headers, { startReason }) => {
      if (startReason === 'invalidation') {
        headers.set('x-read-from-primary', 'true')
      }
      return headers
    },
  }),
  endpoints: () => ({}),
})

A few details: 'initial' vs 'refetch' depends on whether the entry already has data. Mutations get startReason: undefined. 'hydrate' is reserved for upcoming hydration work and isn't set yet. We may add additional values in the future if needed.

Function pollingInterval

pollingInterval can now be a function that receives the current cache entry and returns an interval in ms (#​2639). This covers "poll while a job is running, stop when it's done" without a second hook:

useGetJobQuery(id, {
  pollingInterval: ({ data }) => (data?.status === 'running' ? 1000 : 0),
})

It works in all the query hooks, initiate() and updateSubscriptionOptions. The function runs once per cache key when the next poll is scheduled after a request settles. When several subscribers poll the same key, the lowest result wins, the same as numeric intervals. Returning 0, a negative number or a non-number means "don't poll", and polling resumes if a later request makes the function return an interval again. An inline function in a hook doesn't dispatch updateSubscriptionOptions on every render.

Related changes:

  • A negative numeric pollingInterval now means "no polling". Before, it re-polled immediately in a loop.
  • 'payload.options.pollingInterval' is a new default entry in the serializability check's ignoredActionPaths. If you pass your own ignoredActionPaths, you'll need to add it.
  • SubscriptionOptions['pollingInterval'] is now number | ((entry) => number), so code that reads it as a number needs a type check. There's a new exported PollingInterval type.
getRunningQuery and retainFor

api.endpoints.x.getRunningQuery(arg) is a typed thunk for query and infinite query endpoints. Dispatching it returns the promise of the running request for that cache entry, or undefined. It's the same promise the initiate() call that started the request returned, and awaiting it doesn't add a subscription. It's the typed per-endpoint form of api.util.getRunningQueryThunk.

Query initiate() has a new retainFor option, in seconds. After the last subscriber leaves, the entry is kept for Math.max(keepUnusedDataFor, retainFor) seconds. This is useful for prefetching or subscribe: false requests whose data will be read soon:

dispatch(api.endpoints.getPost.initiate(id, { subscribe: false, retainFor: 60 }))

// later
const running = dispatch(api.endpoints.getPost.getRunningQuery(id))
if (running) {
  await running
}

There's also a new dev-only warning when an infinite query page fetch joins a running fetch in the other direction, like calling fetchNextPage() while fetchPreviousPage() is running. The second call still joins and doesn't fetch its own page, same as before.

getMiddlewareState() and isSubscribed()

The React hooks used to dispatch an internal internal_getRTKQSubscriptions action to check subscription status, and some libraries copied that pattern. We've added real APIs for it:

  • api.util.getMiddlewareState() is a thunk that returns read-only access to what the middleware tracks for that store (currently getSubscriptionCount(queryCacheKey)), or undefined if the middleware isn't added (#​5501).
  • Query initiate() results have an isSubscribed() method.

The hooks use isSubscribed() now, and don't dispatch anything to check subscriptions. The internal_getRTKQSubscriptions action is deprecated. It still works in 2.x, but logs a one-time dev warning and will be removed in 3.0. If you maintain a library that dispatches it (such as a port of the RTKQ hooks to another framework), switch to getMiddlewareState() and isSubscribed().

The hooks also no longer run their own missing-middleware check. A hook with skip: true on a store without the API middleware no longer throws. A non-skipped hook still throws, from the check in initiate().

Listener Middleware: Nested Forks

ForkedTaskAPI now has getState, dispatch and fork, so a forked task can read state, dispatch actions and start its own child tasks (#​3314). Nested forks are cancelled when the task that forked them ends or is cancelled. A nested fork with autoJoin: true makes its parent wait for it before completing.

listenerMiddleware.startListening({
  actionCreator: startSync,
  effect: async (action, listenerApi) => {
    listenerApi.fork(async (forkApi) => {
      const { userId } = forkApi.getState().auth
      forkApi.fork(
        async (childApi) => {
          childApi.dispatch(syncStarted(userId))
        },
        { autoJoin: true },
      )
    })
  },
})

ForkedTaskAPI and the task executor types have optional State and DispatchType generics, which flow through startListening, addListener and their withTypes() versions. Like the listener's own getState and dispatch, these aren't guarded after the task finishes. With some internal cleanup in the same PR, the listener middleware is slightly smaller even with the new API.

Readable Editor Hovers

Hovering over RTK and RTKQ types in an editor often showed a wall of text that the editor cut off at 500 characters, along with odd names like Slice$1 and IsAny. We've added named types so hovers show a name instead of the full structure: FetchBaseQueryFn, ApiUtil, ListenerMiddlewareDispatch, AsyncThunkPromise and ReactApiModules. The query, mutation and infinite query selector result types were rewritten so TypeScript keeps their names. Some hover lengths, before and after:

Hover Before After
useMutation tuple 2508 386
endpoints.getPost.select(...) 2399 602
api.util 16102 471
dispatch(thunk(...)) 552 71

These are type-only changes. Please let us know if the selector result rewrite causes problems in code that's generic over endpoint definitions.

Refetch and Polling Option Fixes

When several subscribers share a query, RTKQ combines their options. Some of those rules skipped refetches that a subscriber asked for (#​5583). Each subscriber's options are now resolved before they're combined:

  • refetchOnMountOrArgChange: 0 and forceRefetch: 0 now always refetch. Before, 0 disabled the option.
  • refetchOnFocus and refetchOnReconnect refetch a shared query if any subscriber's own or inherited setting is true. One subscriber's false no longer turns it off for the others.
  • Polling skips while unfocused only if every polling subscriber sets skipPollingIfUnfocused. Non-polling subscribers don't affect this.

Thanks to @​duckieeeduck for this fix!

Other Fixes

An endpoint's maxRetries now caps retries even when the api-level retry() has a retryCondition. The retryCondition still decides which errors retry (thanks @​luantaraschi!).

retry.fail() called inside a backoff function no longer nests the error inside { error, meta } (thanks @​dfedoryshchev!).

fetchBaseQuery's timeout now works when the request passes its own signal (thanks @​wozhenbang2004!). Query parameters are now added before a URL #fragment instead of after it (thanks @​henricop!). FetchArgs.headers now accepts number and boolean values, which are converted to strings. They already worked at runtime (thanks @​emersion!).

The entity adapter keeps the ids order when an update changes an entity's id (thanks @​b84330808!).

Wrapping createSlice in a generic helper now keeps the prepare callback's parameter types (thanks @​kkatalz!).

Docs Updates

We've documented getCacheEntryRemovedReason, startReason, getRunningQuery, retainFor, getMiddlewareState, isSubscribed, function pollingInterval and nested forks, and fixed several smaller doc and JSDoc errors.

What's Changed

Full Changelog: reduxjs/redux-toolkit@v2.14.0...v2.15.0

v2.14.0

Compare Source

This feature release speeds up the dispatch path and RTK Query's Api type checking, shrinks createSlice in esbuild bundles, adds RTK-owned Draft and Patch types so emitted declarations no longer reference Immer, adds removeMany({ where }) and selectByIds to the entity adapter, adds RTK Query cache entry selectors and a DevTools action sanitizer, and fixes a very long list of RTK Query lifecycle, polling, upsert, timer, hook and fetchBaseQuery bugs.

Note that we just announced our roadmap to Redux Toolkit 3.0, which includes both a large set of planned 2.x features and improvements, and planned 3.0 breaking changes. The fixes and updates in this release help pave the way for all of those efforts. We'd also appreciate feedback on the linked RTK Query usage patterns and 3.0 planned breaking changes discussion threads.

Changelog

Dispatch Performance

Every dispatched action runs through every reducer and middleware, so small costs on that path add up. We added a benchmark harness for the dispatch path and used it to find several places where RTK did work for actions it didn't care about.

createAction(...).match now compares action.type before calling isAction, so a non-matching action costs a property read. createReducer no longer allocates arrays on every dispatch to collect case and matcher reducers. Since createSlice builds its reducer with createReducer, every slice reducer gets this improvement.

The listener middleware used to copy its listener list and call every predicate for every action. It now keeps a snapshot that is rebuilt only when listeners are added or removed, and that snapshot knows which action types have type or actionCreator listeners. If an action's type isn't in that set and there are no matcher or predicate listeners, the middleware skips the loop entirely.

The RTK Query root reducer now returns the existing state for actions that none of its slices handle, instead of running all five slice reducers. It also skips rewriting a query's provided tags when the new tags are the same as the stored ones, so re-fetching a query that returns the same tags no longer creates new provided state.

Some numbers from the PR benchmarks (Node 26, ops/sec unless noted):

Scenario Before After
Listener middleware, 200 listeners, unrelated action 108K 5.34M
Listener middleware, 200 actionCreator listeners, matching action 100K 612K
createSlice, 20 slices, unrelated action 320K 394K
RTKQ store, unrelated action 352K 468K
RTKQ re-dispatch of a fulfilled query with unchanged tags, 1000 entries (ms per dispatch) 2.50 0.55

The listener middleware numbers are the biggest change, because the old cost grew with the number of listeners. Apps with a handful of listeners will see much smaller gains.

The RTK Query middleware also does less work keeping the store's subscriptions state in sync (#​5499). It used to JSON-copy the whole subscriptions object and diff it with Immer every 500ms while subscriptions were changing. It now records which cache keys changed and writes one patch per key. Keys that didn't change keep their object references, so the Redux DevTools no longer receive a full copy of subscriptions on every sync. Polls, refetch() calls and tag invalidation refetches don't add subscribers, so they no longer schedule a sync at all. The visible difference: a cache key that only ever had subscribe: false requests no longer shows up as an empty {} in subscriptions.

Smaller createSlice Bundles With esbuild

createSlice references asyncThunkCreator so that create.asyncThunk works in the reducers callback. esbuild couldn't tell that the asyncThunkCreator object was free of side effects, so it always bundled createAsyncThunk along with createSlice. webpack already dropped it. We've marked it as pure, and an esbuild bundle that imports only createSlice is now about 1 kB smaller (brotli).

Faster RTK Query Api Type Checking

The Api type combines every registered module (core, React hooks, and any third-party modules) by running UnionToIntersection over the module names. TanStack Table hit the same cost with the same design, and found that writing out the known intersection and adding variance annotations helped a lot.

We've done the same thing here: Api uses the core module type directly, and ApiModules has in out variance annotations. On a test app with one ~50-endpoint createApi, type instantiations dropped 22% and check time dropped about 25% on TS 6, and about 18% on the TS 7 native preview. Third-party modules like ngrx-rtk-query saw 7-8% fewer instantiations. There are no runtime changes.

RTK-Owned Draft and Patch Types

RTK used to re-export Immer's Draft type, and used Immer's types in signatures like CaseReducer and PatchCollection. That meant the .d.ts files TypeScript generated for your slices referenced immer. With a package manager layout where immer isn't hoisted, those declarations failed to build with TS2883 (#​5516). Re-exporting doesn't fix that, so RTK now declares its own Draft, WritableDraft and Patch types with the same shapes as Immer's. Emitted declarations now point at @reduxjs/toolkit instead. Our type tests check that RTK's Draft and Immer's Draft stay interchangeable, so code that mixes castDraft or current with RTK's types keeps working. We also bumped the immer dependency to ^11.2.9.

There are a few other type additions in this release:

  • ApiRootState replaces RTK Query's RootState type, which is now deprecated. RootState will be removed in 3.0.
  • TypedAddListenerAction and TypedRemoveListenerAction describe the actions that addListener and removeListener actually dispatch. The default payload type of TypedAddListener and TypedRemoveListener is now the listener options object, so addListener.match(action) no longer claims action.payload has fields like id and unsubscribe that don't exist at runtime.
  • dispatch(removeListener(...)) is typed as returning boolean and dispatch(clearAllListeners()) as returning void, matching the runtime.
  • UseQueryStateDefaultResult and UseInfiniteQueryStateDefaultResult are exported from @reduxjs/toolkit/query/react, for wrapping hooks with a generic selectFromResult.
RTK Query Cache Entry Selectors

We've had requests for a way to list everything in the cache for an endpoint (#​2995). api.util.selectEntriesForEndpoint(state, endpointName) returns all cache entries for one query or infinite query endpoint, and api.util.selectAllQueryEntries(state) returns them for every endpoint. Each item has the entry's fields plus its queryCacheKey, and is typed for its endpoint. Both selectors are memoized. There's also a new exported QueryCacheEntry<Definition> type.

const postEntries = api.util.selectEntriesForEndpoint(state, 'getPost')
const loadedPostIds = postEntries
  .filter((entry) => entry.status === 'fulfilled')
  .map((entry) => entry.originalArgs)
DevTools Action Sanitizer

All RTK Query requests use the same few action types, so the Redux DevTools show a long list of api/executeQuery/fulfilled actions, and you have to open each one to see which endpoint it was for. The new createApiActionSanitizer(api) returns a function for the DevTools actionSanitizer option that renames those actions for display, like api/executeQuery/fulfilled (getPosts). The dispatched actions aren't modified.

import { configureStore } from '@reduxjs/toolkit'
import { createApiActionSanitizer } from '@reduxjs/toolkit/query'
import { api } from './api'

export const store = configureStore({
  reducer: {
    [api.reducerPath]: api.reducer,
  },
  middleware: (getDefaultMiddleware) =>
    getDefaultMiddleware().concat(api.middleware),
  devTools: {
    actionSanitizer: createApiActionSanitizer(api),
  },
})

See the createApiActionSanitizer docs for combining sanitizers for multiple APIs.

Entity Adapter Additions

adapter.removeMany now accepts a { where } object, and removes every entity whose fields match all the given values (#​5524):

postsAdapter.removeMany(state, { where: { authorId: 5 } })

The match object is typed as Partial<T>, and values are compared with ===. A where object with no keys removes nothing, so a filter built at runtime that ends up empty can't clear the collection by accident. Use removeAll for that. There's also a new exported RemoveManyFilter<T> type.

getSelectors() now includes selectByIds(state, ids), which returns the entities for the given ids in the order of ids, skipping ids that don't exist.

removeMany is also faster. It used to filter the Immer draft of the ids array, which reads every element through the draft proxy. It now filters a plain copy against a Set of removed ids.

RTK Query Fixes

Lifecycles: cacheDataLoaded now only resolves for a response from a request that started while that lifecycle was waiting. A late response from before a removeQueryResult no longer resolves the next lifecycle on the same key with discarded data. Re-triggering a mutation with the same fixedCacheKey now ends the previous onCacheEntryAdded lifecycle, so its cacheEntryRemoved cleanup runs instead of leaking. If that earlier trigger is still in flight, its cacheDataLoaded now rejects instead of never settling. Thanks to @​hamarshehmhmd for the analysis in #​5539. getCacheEntry() in a mutation's onQueryStarted now finds the entry for fixedCacheKey mutations instead of always returning uninitialized.

Synchronous throws from onQueryStarted and onCacheEntryAdded are now caught and logged with console.error. Before, a sync throw in onQueryStarted escaped the pending dispatch and failed the request without ever calling queryFn. We also added a dev warning when updateCachedData is called before the entry has any data, since that call does nothing.

Polling: Polling now stops after the last unsubscribe even if the subscription cleanup hasn't run yet (thanks to @​LeulTew for the original fix in #​5444). A due poll re-reads skipPollingIfUnfocused instead of using the value from when the timer was set, and skips the poll if a request for that entry is already pending. pollingInterval values above 2^31-1 ms are now clamped with a dev warning, since larger values overflow setTimeout and fire after 1ms. Removing a cache entry with removeQueryResult now stops its poll timer right away, and switching a subscriber to a slower pollingInterval now reschedules the pending poll instead of letting the old, faster one fire once more. We also fixed a stale internal poll record that could block updatePollingInterval, and fetchBaseQuery now clears its timeout timer when the request finishes.

Upserts: A failed upsertQueryData over an existing entry (for example, from a responseSchema validation error) no longer leaves that entry stuck in pending. upsertQueryEntries now skips bad entries one at a time instead of failing the whole batch: unknown or mutation endpoint names and throwing providesTags callbacks are skipped, with dev warnings.

Timers and multiple stores: resetApiState now clears the subscription sync timer and the state for delayed tag invalidation, so work scheduled before the reset can't fire afterward. A keepUnusedDataFor removal timer is now cleared when the key gets a new subscriber or is removed with removeQueryResult, so an old timer can't remove a newer entry for the same key. Repeated initiate(arg, { subscribe: false }) calls that hit the cache no longer push back the keepUnusedDataFor removal, which could keep unused data around indefinitely (#​4480, thanks @​veksa!). setupListeners now works with more than one store. Before, only the first store got focus and online events.

Hooks: A query that failed before it ever got data now reports isLoading: true when it refetches, instead of having isLoading, isError and data all falsy while the request is pending (#​4449, thanks @​AnimeshPandey!). This undoes a change from 2.2.4 (#​4364) that kept isLoading false when a second hook subscribed to an errored entry. If a parent renders null while isLoading is true and a child mounts the same query, the parent now unmounts the child on each refetch, and the two can loop. Render the child based on data or isError instead. Query args containing NaN no longer cause an endless refetch loop when the query errors. This was a regression from 2.9.0, where arg comparison treated NaN as never equal to itself (#​5338, thanks @​aagostino31!). fetchNextPage() and fetchPreviousPage() no longer send a request when the infinite query hook's arg is skipToken, and initiate(skipToken) no longer sends a request for any query or infinite query endpoint (#​5028, thanks @​haigou-web!).

fetchBaseQuery: A null body no longer throws Cannot read properties of null before the request is sent (thanks @​dfedoryshchev!). An explicit content-type header is now kept for ArrayBuffer, typed array and Blob bodies, which broke presigned S3 and GCS uploads. It's still removed for FormData and for a JSON content type on a non-JSON body, and that JSON content type check is now case-insensitive (thanks @​tad-bit-better!). A custom responseHandler that throws or rejects with a falsy value like undefined now produces a PARSING_ERROR, instead of being treated as a successful response (#​5480, thanks @​JunaidAhamed-7777!). A timeout that fires while the response body is being read is now reported as TIMEOUT_ERROR instead of PARSING_ERROR (thanks @​Gurmehar-git!).

Other RTKQ fixes: An overlapping refetch now stays registered as the running query, so later calls join it and aborting it works (thanks @​tedy69!). Apps with many createApi middlewares could hit a "Maximum call stack size exceeded" error when the middlewares registered themselves on the first query. Registration no longer restarts dispatch from the start of the middleware chain (thanks @​PabloJoan!). api.enhanceEndpoints({ endpoints }) now logs an error in development when it names an endpoint that doesn't exist, which usually means a typo.

RTK Query thunk actions now include startedTimeStamp and a per-store seq counter in the fulfilled and rejected-with-value meta, matching the request's pending action, so you can tell which request a response belongs to and in what order requests started. Rejections for aborted requests and unhandled errors don't include these fields yet.

Other Fixes

The listener middleware's take(), condition() and delay() no longer leave their timers running after the listener is cancelled or the action arrives first.

The autoBatchEnhancer raf fallback no longer throws a cancelAnimationFrame ReferenceError in test environments that delete window globals during teardown (thanks @​msutkowski!).

RTK Query hooks now log a dev warning when they render with a different store than the one they first subscribed to. If you swap the store passed to <Provider>, give the Provider a key that changes with the store so the tree remounts.

The serializability check middleware now reports a circular reference in state or actions as a non-serializable value, instead of overflowing the stack (thanks @​OskarEichler!).

@types/react is now declared as an optional peer dependency. RTK's React entry points import React types, and with pnpm's isolated linker or a global virtual store, TypeScript couldn't find them and those types became any (thanks @​unrevised6419!).

What's Changed

Full Changelog: reduxjs/redux-toolkit@v2.13.0...v2.14.0

v2.13.0

Compare Source

This feature release updates our build tooling to TSDown and PNPM, adds official TypeScript 7 support, and includes a long list of bugfixes across RTK Query, createAsyncThunk, createEntityAdapter, and combineSlices.

Changelog

Build Tooling Updates

We've fully modernizing modernized our build tooling across all of the Redux repos. That included switching from Yarn to PNPM, ESLint to Oxlint, Prettier to Oxfmt, and TSUp to TSDown.

The part that matters for users is that we now build the package with TSDown instead of tsup. The package layout, exports definitions, and exported APIs are all unchanged from 2.12. We've checked the new build with attw, and verified that CJS and ESM entry points load in both dev and prod builds, and that the legacy-esm artifacts still target ES2017. The contents of the bundles do look a bit different (smaller CJS artifacts, slightly different helper output in the legacy-esm files). If you see any behavior differences that look build-related, please file an issue!

This is also our first release published via the updated PNPM-based workflow, still using NPM Trusted Publishing. We've also added pkg.pr.new previews for every commit, so you can try out a PR build before it's released.

Docs Updates

We've shipped a new combined Redux libraries docs site! The core docs site at https://redux.js.org now contains the docs for all of our libraries: Redux core and usage guides, Redux Toolkit, React Redux, and Reselect. The prior standalone docs sites for RTK, R-R, and Reselect now redirect to their respective sections of the combined docs. We've also done a major cleanup pass on the docs, deduplicating pages that had similarities (like the Next.js or RTK2 migration pages that lived in both the core and RTK docs), and updating outdated content (modernizing example code snippets, deleting dead links, and making RTK and hooks the default patterns shown). The RTK content now lives at https://redux.js.org/toolkit/ .

TypeScript 7 Support

TS 7.0 (the native Go port) is now out! We fixed the remaining type errors in RTK when checked by TS 7.0 and 7.1, and TS 7.0 is now part of our CI test matrix.

Per our TS support policy of matching DefinitelyTyped's support window, we've also updated our support matrix to TS 5.6+. As always, RTK may still work with earlier versions, but we no longer test against them.

RTK Query Fixes

useQueryState (and thus useQuery) was passing a new inline selector to useSelector on every render, and also reading the store directly during render. The selector is now memoized, and the direct store read is gone. This also fixes a bug where isSuccess could flip from false to true on an unrelated re-render while a query was refetching after an error. isSuccess now correctly stays false in that case.

data now reflects cache updates made via updateQueryData while a refetch is in flight, instead of showing the previous result.

Polling now reads the current cache state when each poll fires, rather than the state at the time the poll was scheduled. This means skipPollingIfUnfocused respects focus loss

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


Configuration

📅 Schedule: (UTC)

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@renovate renovate Bot added the dependencies label Oct 7, 2026
@changeset-bot

changeset-bot Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: c9b39a7

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

@coderabbitai

coderabbitai Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 5e2abd7c-1993-45b9-990d-80ada96aaf09

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@renovate
renovate Bot force-pushed the renovate/reduxjs-toolkit-2.x-lockfile branch from 3238ced to a5d1543 Compare October 20, 2026 14:33
@nx-cloud

nx-cloud Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

View your CI Pipeline Execution ↗ for commit c9b39a7

Command Status Duration Result
nx affected -t build lint test typecheck e2e-ci ❌ Failed 2m 7s View ↗

💡 Dealing with memory or CPU issues? See memory and CPU details with the resource usage add-on ↗.


☁️ Nx Cloud last updated this comment at 2026-11-18 21:33:46 UTC

@renovate
renovate Bot force-pushed the renovate/reduxjs-toolkit-2.x-lockfile branch from a5d1543 to 528639a Compare October 22, 2026 14:37
nx-cloud[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/reduxjs-toolkit-2.x-lockfile branch from 528639a to a82f0df Compare October 26, 2026 21:48
nx-cloud[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/reduxjs-toolkit-2.x-lockfile branch from a82f0df to ca68648 Compare November 2, 2026 19:11
nx-cloud[bot]

This comment was marked as outdated.

@renovate renovate Bot changed the title chore(deps): update dependency @reduxjs/toolkit to v2.13.0 chore(deps): update dependency @reduxjs/toolkit to v2.14.0 Nov 3, 2026
@renovate
renovate Bot force-pushed the renovate/reduxjs-toolkit-2.x-lockfile branch from ca68648 to 3273c63 Compare November 3, 2026 23:42
nx-cloud[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/reduxjs-toolkit-2.x-lockfile branch from 3273c63 to 828fcd0 Compare November 11, 2026 15:34
nx-cloud[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/reduxjs-toolkit-2.x-lockfile branch from 828fcd0 to d629519 Compare November 16, 2026 14:54
nx-cloud[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/reduxjs-toolkit-2.x-lockfile branch from d629519 to c9b39a7 Compare November 18, 2026 21:30
@renovate renovate Bot changed the title chore(deps): update dependency @reduxjs/toolkit to v2.14.0 chore(deps): update dependency @reduxjs/toolkit to v2.15.0 Nov 18, 2026

@nx-cloud nx-cloud Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nx Cloud is proposing a fix for your failed CI:

We fixed the TS4023 build and typecheck failure that came with the @reduxjs/toolkit 2.15.0 bump. The reducers in node.slice.ts now have explicit Draft<NodeStates> state parameters and explicit return types. Declaration emit for nodeSlice can now name them without using RTK's unexported WritableNonArrayDraft helper.

Tip

✅ We verified this fix by re-running @forgerock/davinci-client:typecheck, @forgerock/davinci-client:build.

Suggested Fix changes
diff --git a/packages/davinci-client/src/lib/node.slice.ts b/packages/davinci-client/src/lib/node.slice.ts
index f9d68af..bd636ae 100644
--- a/packages/davinci-client/src/lib/node.slice.ts
+++ b/packages/davinci-client/src/lib/node.slice.ts
@@ -71,9 +71,9 @@ export const nodeSlice = createSlice({
      * @returns {ErrorNode} - The error node
      */
     error(
-      state,
+      state: Draft<NodeStates>,
       action: PayloadAction<{ data: DavinciErrorResponse; requestId: string; httpStatus: number }>,
-    ) {
+    ): ErrorNode {
       const newState = state as Draft<ErrorNode>;
 
       // Reference to the original response from DaVinci in the cache
@@ -117,13 +117,13 @@ export const nodeSlice = createSlice({
      * @returns {FailureNode} - The failure node
      */
     failure(
-      state,
+      state: Draft<NodeStates>,
       action: PayloadAction<{
         data: DaVinciFailureResponse | unknown;
         requestId: string;
         httpStatus: number;
       }>,
-    ) {
+    ): FailureNode {
       const newState = state as Draft<FailureNode>;
 
       newState.cache = {
@@ -172,13 +172,13 @@ export const nodeSlice = createSlice({
      * @returns {ContinueNode} - The next node
      */
     next(
-      state,
+      state: Draft<NodeStates>,
       action: PayloadAction<{
         data: DaVinciNextResponse;
         requestId: string;
         httpStatus: number;
       }>,
-    ) {
+    ): ContinueNode {
       const newState = state as Draft<ContinueNode>;
 
       const collectors = nodeCollectorReducer([], {
@@ -234,13 +234,13 @@ export const nodeSlice = createSlice({
      * @returns {SuccessNode} - The success node
      */
     success(
-      state,
+      state: Draft<NodeStates>,
       action: PayloadAction<{
         data: DaVinciSuccessResponse;
         requestId: string;
         httpStatus: number;
       }>,
-    ) {
+    ): SuccessNode {
       const newState = state as Draft<SuccessNode>;
 
       newState.cache = {
@@ -277,7 +277,10 @@ export const nodeSlice = createSlice({
      * @param {PayloadAction<unknown>} action - The action to be dispatched
      * @returns {ContinueNode} - The next node
      */
-    update(state, action: ReturnType<typeof updateCollectorValues>) {
+    update(
+      state: Draft<NodeStates>,
+      action: ReturnType<typeof updateCollectorValues>,
+    ): ContinueNode {
       const newState = state as Draft<ContinueNode>;
 
       newState.client.collectors = nodeCollectorReducer(newState.client.collectors, action);
@@ -292,11 +295,11 @@ export const nodeSlice = createSlice({
      * @returns {ContinueNode} - The next node
      */
     poll(
-      state,
+      state: Draft<NodeStates>,
       action: PayloadAction<{
         requestId: string;
       }>,
-    ) {
+    ): ContinueNode {
       const newState = state as Draft<ContinueNode>;
 
       // Update retries remaining in poll collector

Apply fix via Nx Cloud  Reject fix via Nx Cloud


Or Apply changes locally with:

npx nx-cloud apply-locally daIb-wtVY

Apply fix locally with your editor ↗   View interactive diff ↗



🎓 Learn more about Self-Healing CI on nx.dev

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

0 participants