kjuulh/vidow
1
0
Fork 0
Code Issues 1 Pull Requests 4 Packages Projects Releases Wiki Activity

Update all dependencies #451

Open
kjuulh wants to merge 1 commits from renovate/all into main
pull from: renovate/all
merge into: kjuulh:main
Conversation 0 Commits 1 Files Changed 3 +95 -89
kjuulh commented 2025-03-26 00:25:40 +01:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
@reduxjs/toolkit (source) dependencies minor 2.6.0 -> 2.11.1
@types/node (source) devDependencies major 22.13.9 -> 24.10.2
clap dependencies patch 4.5.31 -> 4.5.53
ts-jest (source) devDependencies minor 29.2.6 -> 29.4.6
typescript (source) devDependencies minor 5.8.2 -> 5.9.3

Release Notes

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

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.11.0...v2.11.1

v2.11.0

Compare Source

This feature release upgrades our Immer dependency to v11 to pick up the additional recent performance optimizations, adds a new refetchCachedPages option to allow only fetching the first cached page, and fixes an issue with regex ignore paths in the immutability middleware.

Changelog

Immer v11 Performance Improvements

As described in the release notes for v2.10.0, we recently put significant effort into profiling Immer, and contributed several PRs that aimed to optimize its update performance.

v2.10.0 updated to use Immer 10.2.0, which added the first smaller set of perf updates. That included a new Immer option to disable "strict iteration" to speed up iterating copied objects, and we specifically applied that change in RTK under the assumption that standard plain JS objects as Redux state shouldn't have unusual keys anyway. Overall, this appears to boost Immer update perf by ~+20% over v10.1 depending on update scenario.

Immer v11.0.0 was just released and contains the second perf PR, a major internal architectural rewrite to change the update finalization implementation from a recursive tree traversal to a set of targeted updates based on accessed and updated fields. Based on the benchmarks in the PR, this adds another ~+5% perf boost over the improvements in v10.2, again with variations depending on update scenario. In practice, the actual improvement may be better than that - the benchmarks list includes some array update cases which actually got a bit slower (and thus drag down the overall average), and a majority of update scenarios show anywhere from +25% to +60% faster than Immer v10.1!

As a practical example, we have an RTK Query stress test benchmark where we mount 1000 components with query hooks at once, unmount, then remount them. We ran the same benchmark steps for RTK 2.9 and Immer 10.1, and then RTK 2.10+ and Immer 11. The overall scripting time dropped by about 30% (3330ms -> 2350ms), and the amount of time spent in Immer methods and the RTK reducers dropped significantly:

image

Based on this, it appears to be a major improvement overall.

As with the instructions in v2.10.0: if by some chance your Redux app state relies on non-string keys, you can still manually call setUseStrictIteration(true) in your app code to retain compatibility there, but we don't expect that standard Redux apps will have to worry about that.

There are still two outstanding Immer perf PRs that may offer further improvements: one that adds an optional plugin to override array methods to avoid proxy creation overhead, and another experimental tweak to shallow copying that may be better with larger object sizes.

New refetchCachedPages Option

RTK Query's infinite query API was directly based on React Query's approach, including the pages cache structure and refetching behavior. By default, that means that when you trigger a refetch, both R-Q and RTKQ will try to sequentially refetch all pages currently in that cache entry. So, if there were 5 pages cached for an entry, they will try to fetch pages 0...4, in turn.

Some users have asked for the ability to only refetch the first page. This can be accomplished somewhat manually by directly updating the cache entry to eliminate the old pages and then triggering a refetch, but that's admittedly not very ergonomic.

We've merged a contributed PR that adds a new refetchCachedPages flag. This can be defined as part of infinite query endpoints, passed as an option to infinite query hooks, or passed as an option in initiate() calls or hook refetch() methods. If set to refetchCachedPages: false, it will only refetch the first page in the cache and not the remaining pages, thus shrinking the cache from N pages to 1 page.

Other Fixes

We merged a fix to the immutability dev middleware where it was treating ignoredPath regexes as strings and not actually testing them correctly.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.10.1...v2.11.0

v2.10.1

Compare Source

This bugfix release fixes an issue with window access breaking in SSR due to the byte-shaving work in 2.10.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.10.0...v2.10.1

v2.10.0

Compare Source

This feature release updates our Immer dep to 10.2 to pick up its performance improvements, has additional byte-shaving and internal performance updates, and fixes a combineSlices type issue.

Changelog

Immer Performance Improvements

Redux Toolkit has been built around Immer since the very first prototype in 2018. Use of Immer as the default in createSlice directly eliminated accidental mutations as a class of errors in Redux apps, and drastically simplified writing immutable updates in reducers.

We've had various issues filed over the years asking to make Immer optional, or raising concerns about Immer's perf. Immer is indeed slower than writing immutable updates by hand, but our stance has always been that Immer's DX is absolutely worth whatever modest perf cost it might incur, and that reducers are usually not the bottleneck in Redux apps anyway - it's usually the cost of updating the UI that's more expensive.

However, a year ago an issue was filed with some specific complaints about Immer perf being very slow. We investigated, ran benchmarks, and filed an Immer issue confirming that it had gotten noticeably slower over time. Immer author Michel Weststrate agreed, and said there were some potential tweaks and architectural changes that could be made, but didn't have time to look into them himself.

A couple months ago, we started investigating possible Immer perf improvements ourselves, including profiling various scenarios and comparing implementations of other similar immutable update libraries. After extensive research and development, we were able to file several PRs to improve Immer's perf: a set of smaller tweaks around iteration and caching, a couple much larger architectural changes, and a potential change to copying objects.

Immer 10.2.0 contains the first set of smaller perf improvements, and this RTK release updates our dependency to 10.2 to pick up those changes.

One important behavior note here: Earlier versions of Immer (8, 9, 10.1) added more handling for edge cases like symbol keys in objects. These changes made sense for correctness, but also contributed to the slowdown. Immer 10.2 now includes a new setUseStrictIteration option to allow only copying string keys in objects (using Object.keys() instead of Reflect.ownKeys()), but keeps the option as strict: true for compatibility with its own users. That default will likely change in Immer 11.

For RTK 2.10.0, we specifically import and call setUseStrictIteration(false), under the assumption that standard Redux state usage only involves string keys in plain JS objects! This should provide a ~10% speedup for Immer update operations. Given that expectation, we believe this is a reasonable feature change and only needs a minor version bump.

If by some chance you are using symbol keys in your Redux state, or in other Immer-powered updates in your Redux app, you can easily revert to the previous behavior by calling setUseStrictIteration(true) in your own app code.

Based on discussions with Michel, Immer v11 should come out in the near future with additional architectural changes for better perf, including optional support for faster array methods that would be available as an Immer plugin adding ~2KB bundle size. We will likely not turn that plugin on by default, but recommend that users enable it if they do frequent array ops in reducers.

We're happy to have contributed these perf improvements to Immer, and that they will benefit not just RTK users but all Immer users everywhere!

You can follow the additional discussion and progress updates in the main Immer perf update tracking issue.

Additional RTK Perf Improvements

We've tweaked some places where we were doing repeated filter().map().map() calls to micro-optimize those loops.

RTKQ tag invalidation was always reading from proxy-wrapped arrays when rewriting provided tags. It now reads from the plain arrays instead, providing a modest speedup.

We previously found that ESBuild wasn't deduplicating imports from the same libraries in separate files bundled together (ie import { useEffect as useEffect2/3/4/ } from 'react'). We've restructured our internals to ensure all external imports are only pulled in once.

We've done some extensive byte-shaving in various places in the codebase. The byte-shaving and import deduplication saves about 0.6K min from the RTKQ core, and 0.2K min from the RTKQ React bundle.

Other Changes

combineSlices now better handles cases where PreloadedState might not match the incoming type, such as persisted values.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.9.2...v2.10.0

v2.9.2

Compare Source

This bugfix release fixes a potential internal data leak in SSR environments, improves handling of headers in fetchBaseQuery, improves retry handling for unexpected errors and request aborts, and fixes a longstanding issue with prefetch leaving an unused subscription. We've also shipped a new graphqlRequestBaseQuery release with updated dependencies and better error handling.

Changelog

Internal Subscription Handling

We had a report that a Redux SSR app had internal subscription data showing up across different requests. After investigation, this was a bug introduced by the recent RTKQ perf optimizations, where the internal subscription fields were hoisted outside of the middleware setup and into createApi itself. This meant they existed outside of the per-store-instance lifecycle. We've reworked the logic to ensure the data is per-store again. We also fixed another issue that miscalculated when there was an active request while checking for cache entry cleanup.

Note that no actual app data was leaked in this case, just the internal subscription IDs that RTKQ uses in its own middleware to track the existence of subscriptions per cache entry.

fetchBaseQuery Headers

We've updated fetchBaseQuery to avoid setting content-type in cases where a non-JSONifiable value like FormData is being passed as the request body, so that the browser can set that content type itself. It also now sets the accept header based on the selected responseHandler (JSON or text).

retry Behavior and Cleanup

The retry util now respects the maxRetries option when catching unknown errors in addition to the existing known errors logic. It also now checks the request's AbortSignal and will stop retrying if aborted.

In conjunction with that, dispatching resetApiState will now abort all in-flight requests.

The prefetch util and usePrefetch hook had a long-standing issue where they would create a subscription for a cache entry, but there was no way to clean up that subscription. This meant that the cache entry was effectively permanent. They now initiate the request without adding a subscription. This will fetch the cache entry and leave it in the store for the keepUnusedDataFor period as intended, giving your app time to actually subscribe to the value (such as prefetching the cache entry in a route handler, and then subscribing in a component).

graphqlRequestBaseQuery

We've published @rtk-query/graphql-request-base-query v2.3.2, which updates the graphql-request dep to ^7. We also fixed an issue where the error handling rethrew unknown errors - it now returns {error} as a base query is supposed to.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.9.1...v2.9.2

v2.9.1

Compare Source

This bugfix release fixes how sorted entity adapters handle duplicate IDs, tweaks the TS types for RTKQ query state cache entries to improve how the data field is handled, and adds better cleanup for long-running listener middleware effects.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.9.0...v2.9.1

v2.9.0

Compare Source

This feature release rewrites RTK Query's internal subscription and polling systems and the useStableQueryArgs hook for better perf, adds automatic AbortSignal handling to requests still in progress when a cache entry is removed, fixes a bug with the transformResponse option for queries, adds a new builder.addAsyncThunk method, and fixes assorted other issues.

Changelog

RTK Query Performance Improvements

We had reports that RTK Query could get very slow when there were thousands of subscriptions to the same cache entry. After investigation, we found that the internal polling logic was attempting to recalculate the minimum polling time after every new subscription was added. This was highly inefficient, as most subscriptions don't change polling settings, and it required repeated O(n) iteration over the growing list of subscriptions. We've rewritten that logic to debounce the update check and ensure a max of one polling value update per tick for the entire API instance.

Related, while working on the request abort changes, testing showed that use of plain Records to hold subscription data was inefficient because we have to iterate keys to check size. We've rewritten the subscription handling internals to use Maps instead, as well as restructuring some additional checks around in-flight requests.

These two improvements drastically improved runtime perf for the thousands-of-subscriptions-one-cache-entry repro, eliminating RTK methods as visible hotspots in the perf profiles. It likely also improves perf for general usage as well.

We've also changed the implementation of our internal useStableQueryArgs hook to avoid calling serializeQueryArgs on its value, which can avoid potential perf issues when a query takes a very large object as its cache key.

[!NOTE]
The internal logic switched from serializing the query arg to doing reference checks on nested values. This means that if you are passing a non-POJO value in a query arg, such as useSomeQuery({a: new Set()}), and you have refetchOnMountOrArgChange enabled, this will now trigger refeteches each time as the Set references are now considered different based on equality instead of serialization.

Abort Signal Handling on Cleanup

We've had numerous requests over time for various forms of "abort in-progress requests when the data is no longer needed / params change / component unmounts / some expensive request is taking too long". This is a complex topic with multiple potential use cases, and our standard answer has been that we don't want to abort those requests - after all, cache entries default to staying in memory for 1 minute after the last subscription is removed, so RTKQ's cache can still be updated when the request completes. That also means that it doesn't make sense to abort a request "on unmount".

However, it does then make sense to abort an in-progress request if the cache entry itself is removed. Given that, we've updated our cache handling to automatically call the existing resPromise.abort() method in that case, triggering the AbortSignal attached to the baseQuery. The handling at that point depends on your app - fetchBaseQuery should handle that, a custom baseQuery or queryFn would need to listen to the AbortSignal.

We do have an open issue asking for further discussions of potential abort / cancelation use cases and would appreciate further feedback.

New Options

The builder callback used in createReducer and createSlice.extraReducers now has builder.addAsyncThunk available, which allows handling specific actions from a thunk in the same way that you could define a thunk inside createSlice.reducers:

        const slice = createSlice({
          name: 'counter',
          initialState: {
            loading: false,
            errored: false,
            value: 0,
          },
          reducers: {},
          extraReducers: (builder) =>
            builder.addAsyncThunk(asyncThunk, {
              pending(state) {
                state.loading = true
              },
              fulfilled(state, action) {
                state.value = action.payload
              },
              rejected(state) {
                state.errored = true
              },
              settled(state) {
                state.loading = false
              },
            }),
        })

createApi and individual endpoint definitions now accept a skipSchemaValidation option with an array of schema types to skip, or true to skip validation entirely (in case you want to use a schema for its types, but the actual validation is expensive).

Bug Fixes

The infinite query implementation accidentally changed the query internals to always run transformResponse if provided, including if you were using upsertQueryData(), which then broke. It's been fixed to only run on an actual query request.

The internal changes to the structure of the state.api.provided structure broke our handling of extractRehydrationInfo - we've updated that to handle the changed structure.

The infinite query status fields like hasNextPage are now a looser type of boolean initially, rather than strictly false.

TS Types

We now export Immer's WritableDraft type to fix another non-portable types issue.

We've added an api.endpoints.myEndpoint.types.RawResultType types-only field to match the other available fields.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.8.2...v2.9.0

v2.8.2

Compare Source

This bugfix release fixes a bundle size regression in RTK Query from the build and packaging changes in v2.8.0.

If you're using v2.8.0 or v2.8.1, please upgrade to v2.8.2 right away to resolve that bundle size issue!

Changelog

RTK Query Bundle Size

In v2.8.0, we reworked our packaging setup to better support React Native. While there weren't many meaningful code changes, we did alter our bundling build config file. In the process, we lost the config options to externalize the @reduxjs/toolkit core when building the RTK Query nested entry points. This resulted in a regression where the RTK core code also got bundled directly into the RTK Query artifacts, resulting in a significant size increase.

This release fixes the build config and restores the previous RTKQ build artifact sizes.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.8.1...v2.8.2

v2.8.1

Compare Source

This bugfix release makes an additional update to the package config to fix a regression that happened with Jest and jest-environment-jsdom.

[!CAUTION]
This release had a bundle size regression. Please update to v2.8.2 to resolve that issue.

Changes

More Package Updates

After releasing v2.8.0, we got reports that Jest tests were breaking. After investigation we concluded that jest-environment-jsdom was looking at the new browser package exports condition we'd added to better support JSPM, finding an ESM file containing the export keyword, and erroring because it doesn't support ES modules correctly.

https://github.com/reduxjs/redux-toolkit/issues/4971#issuecomment-2859506562 listed several viable workarounds, but this is enough of an issue we wanted to fix it directly. We've tweaked the package exports setup again, and it appears to resolve the issue with Jest.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.8.0...v2.8.1

v2.8.0

Compare Source

This feature release improves React Native compatibility by updating our package exports definitions, and adds queryArg as an additional parameter to infinite query page param functions.

[!CAUTION]
This release had a bundle size regression, as well as a breakage with jest-environment-jsdom. Please update to v2.8.2 to resolve those issues.

Changelog

Package Exports and React Native Compatibility

Expo and the Metro bundler have been adding improved support for the exports field in package.json files, but those changes started printing warnings due to how some of our package definitions were configured.

We've reworked the package definitions (again!), and this should be resolved now.

Infinite Query Page Params

The signature for the getNext/PreviousPageParam functions has been:

(
    lastPage: DataType,
    allPages: Array<DataType>,
    lastPageParam: PageParam,
    allPageParams: Array<PageParam>,
  ) => PageParam | undefined | null

This came directly from React Query's API and implementation.

We've had some requests to make the endpoint's queryArg available in page param functions. For React Query, that isn't necessary because the callbacks are defined inline when you call the useInfiniteQuery hook, so you've already got the query arg available in scope and can use it. Since RTK Query defines these callbacks as part of the endpoint definition, the query arg isn't in scope.

We've added queryArg as an additional 5th parameter to these functions in case it's needed.

Other Changes

We've made a few assorted docs updates, including replacing the search implementation to now use a local index generated on build (which should be more reliable and also has a nicer results list uI), and fixing some long-standing minor docs issues.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.7.0...v2.8.0

v2.7.0

Compare Source

RTK has hit Stage 2.7! 🤣 This feature release adds support for Standard Schema validation in RTK Query endpoints, fixes several issues with infinite queries, improves perf when infinite queries provide tags, adds a dev-mode check for duplicate middleware, and improves reference stability in slice selectors and infinite query hooks.

Changelog

Standard Schema Validation for RTK Query

Apps often need to validate responses from the server, both to ensure the data is correct, and to help enforce that the data matches the expected TS types. This is typically done with schema libraries such as Zod, Valibot, and Arktype. Because of the similarities in usage APIs, those libraries and others now support a common API definition called Standard Schema, allowing you to plug your chosen validation library in anywhere Standard Schema is supported.

RTK Query now supports using Standard Schema to validate query args, responses, and errors. If schemas are provided, the validations will be run and errors thrown if the data is invalid. Additionally, providing a schema allows TS inference for that type as well, allowing you to omit generic types from the endpoint.

Schema usage is per-endpoint, and can look like this:

import { createApi, fetchBaseQuery } from '@&#8203;reduxjs/toolkit/query/react'
import * as v from 'valibot'

const postSchema = v.object({
  id: v.number(),
  name: v.string(),
})
type Post = v.InferOutput<typeof postSchema>

const api = createApi({
  baseQuery: fetchBaseQuery({ baseUrl: '/' }),
  endpoints: (build) => ({
    getPost: build.query({
      // infer arg from here
      query: ({ id }: { id: number }) => `/post/${id}`,
      // infer result from here
      responseSchema: postSchema,
    }),
    getTransformedPost: build.query({
      // infer arg from here
      query: ({ id }: { id: number }) => `/post/${id}`,
      // infer untransformed result from here
      rawResponseSchema: postSchema,
      // infer transformed result from here
      transformResponse: (response) => ({
        ...response,
        published_at: new Date(response.published_at),
      }),
    }),
  }),
})

If desired, you can also configure schema error handling with the catchSchemaFailure option. You can also disable actual runtime validation with skipSchemaValidation (primarily useful for cases when payloads may be large and expensive to validate, but you still want to benefit from the TS type inference).

See the "Schema Validation" docs section in the createApi reference and the usage guide sections on queries, infinite queries, and mutations, for more details.

Infinite Query Fixes

This release fixes several reported issue with infinite queries:

  • The lifecycleApi.updateCachedData method is now correctly available
  • The skip option now correctly works for infinite query hooks
  • Infinite query fulfilled actions now include the meta field from the base query (such as {request, response}). For cases where multiple pages are being refetched, this will be the meta from the last page fetched.
  • useInfiniteQuerySubscription now returns stable references for refetch and the fetchNext/PreviousPage methods
upsertQueryEntries, Tags Performance and API State Structure

We recently published a fix to actually process per-endpoint providedTags when using upsertQueryEntries. However, this exposed a performance issue - the internal tag handling logic was doing repeated O(n) iterations over all endpoint+tag entries in order to clear out existing references to that cache key. In cases where hundreds or thousands of cache entries were being inserted, this became extremely expensive.

We've restructured the state.api.provided data structure to handle reverse-mapping between tags and cache keys, which drastically improves performance in this case. However, it's worth noting that this is a change to that state structure. This shouldn't affect apps, because the RTKQ state is intended to be treated as a black box and not generally directly accessed by user app code. However, it's possible someone may have depended on that specific state structure when writing a custom selector, in which case this would break. An actual example of this is the Redux DevTools RTKQ panel, which iterates the tags data while displaying cache entries. That did break with this change. Prior to releasing RTK 2.7,we released Redux DevTools 3.2.10, which includes support for both the old and new state.api.provided definitions.

TS Support Matrix Updates

Following with the DefinitelyTyped support matrix, we've officially dropped support for TS 5.0, and currently support TS 5.1 - 5.8. (RTK likely still works with 5.0, but we no longer test against that in CI.)

Duplicate Middleware Dev Checks

configureStore now checks the final middleware array for duplicate middleware references. This will catch cases such as accidentally adding the same RTKQ API middleware twice (such as adding baseApi.middleware and injectedApi.middlweware - these are actually the same object and same middleware).

Unlike the other dev-mode checks, this is part of configureStore itself, not getDefaultMiddleware().

This can be configured via the new duplicateMiddlewareCheck option.

Other Changes

createEntityAdapter now correctly handles adding an item and then applying multiple updates to it.

The generated combineSlices selectors will now return the same placeholder initial state reference for a given slice, rather than returning a new initial state reference every time.

useQuery hooks should now correctly refetch after dispatching resetApiState.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.6.1...v2.7.0

v2.6.1

Compare Source

This bugfix release fixes several assorted types issues with the initial infinite query feature release, and adds support for an optional signal argument to createAsyncThunk.

Changelog

Infinite Query Fixes

We've fixed several types issues that were reported with infinite queries after the 2.6.0 release:

  • matchFulfilled and providesTags now get the correct response types
  • We've added pre-typed Type* types to represent infinite queries, similar to the existing pre-defined types for queries and mutations
  • selectCachedArgsForQuery now supports fetching args for infinite query endpoints
  • We fixed some TS type portability issues with infinite queries that caused errors when generating TS declarations
  • useInfiniteQueryState/Subscription now correctly expect just the query arg, not the combined {queryArg, pageParam} object
Other Improvements

createAsyncThunk now accepts an optional {signal} argument. If provided, the internal AbortSignal handling will tie into that signal.

upsertQueryEntries now correctly generates provided tags for upserted cache entries.

What's Changed

Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.6.0...v2.6.1

clap-rs/clap (clap)

v4.5.53

Compare Source

Features
  • Add default_values_if, default_values_ifs

v4.5.52

Compare Source

Fixes
  • Don't panic when args_conflicts_with_subcommands conflicts with an ArgGroup

v4.5.51

Compare Source

Fixes
  • (help) Correctly calculate padding for short flags that take a value
  • (help) Don't panic on short flags using ArgAction::Count

v4.5.50

Compare Source

Features
  • Accept Cow where String and &str are accepted

v4.5.49

Compare Source

Fixes
  • (help) Correctly wrap when ANSI escape codes are present

v4.5.48

Compare Source

Documentation
  • Add a new CLI Concepts document as another way of framing clap
  • Expand the typed_derive cookbook entry

v4.5.47

Compare Source

Features
  • Added impl FromArgMatches for ()
  • Added impl Args for ()
  • Added impl Subcommand for ()
  • Added impl FromArgMatches for Infallible
  • Added impl Subcommand for Infallible
Fixes
  • (derive) Update runtime error text to match clap

v4.5.46

Compare Source

Features
  • Expose StyledStr::push_str

v4.5.45

Compare Source

Fixes
  • (unstable-v5) ValueEnum variants now use the full doc comment, not summary, for PossibleValue::help

v4.5.44

Compare Source

Features
  • Add Command::mut_subcommands

v4.5.43

Compare Source

Fixes
  • (help) In long help, list Possible Values before defaults, rather than after, for a more consistent look

v4.5.42

Compare Source

Fixes
  • Include subcommand visible long aliases in --help

v4.5.41

Compare Source

Features
  • Add Styles::context and Styles::context_value to customize the styling of [default: value] like notes in the --help

v4.5.40

Compare Source

Features
  • Support quoted ids in arg!() macro (e.g. arg!("check-config": ...))

v4.5.39

Compare Source

Fixes
  • (help) Show short flag aliases before long
  • (help) Merge the short and long flag alias lists

v4.5.38

Compare Source

Fixes
  • (help) When showing aliases, include leading -- or -

v4.5.37

Compare Source

Features
  • Added ArgMatches::try_clear_id()

v4.5.36

Compare Source

Fixes
  • (help) Revert 4.5.35's "Don't leave space for shorts if there are none" for now

v4.5.35

Compare Source

Fixes
  • (help) Align positionals and flags when put in the same help_heading
  • (help) Don't leave space for shorts if there are none

v4.5.34

Compare Source

Fixes
  • (help) Don't add extra blank lines with flatten_help(true) and subcommands without arguments

v4.5.33

Compare Source

Fixes
  • (error) When showing the usage of a suggestion for an unknown argument, don't show the group

v4.5.32

Compare Source

Features
  • Add Error::remove
Documentation
  • (cookbook) Switch from humantime to jiff
  • (tutorial) Better cover required vs optional
Internal
  • Update pulldown-cmark
kulshekhar/ts-jest (ts-jest)

v29.4.6

Compare Source

Bug Fixes

v29.4.5

Compare Source

Bug Fixes
  • allow filtering modern module warning message with diagnostic code (c290d4d), , closes #​5013

v29.4.4

Compare Source

Bug Fixes

v29.4.3

Compare Source

Bug Fixes
  • introduce transpilation option to replace isolatedModules option (#​5044) (5868761)

v29.4.2

Compare Source

v29.4.1

Compare Source

v29.4.0

Compare Source

Features

v29.3.4

Compare Source

Bug Fixes
  • fix: fix TsJestTransformerOptions type (3b11e29), closes #​4247
  • fix(cli): fix wrong path for preset creator fns (249eb2c)
  • fix(config): disable rewriteRelativeImportExtensions always (9b1f472), closes #​4855

v29.3.3

Compare Source

Bug Fixes

v29.3.2

Compare Source

Bug Fixes
  • fix: transpile js files from node_modules whenever Jest asks (968370e), closes #​4637

v29.3.1

Compare Source

Bug Fixes
  • fix: allow isolatedModules mode to have ts.Program under Node16/Next (25157eb)
  • fix: improve message for isolatedModules of ts-jest config (547eb6f)

v29.3.0

Compare Source

Features
  • feat: support hybrid module values for isolatedModules: true (f372121)
Bug Fixes
  • fix: set customConditions to undefined in TsCompiler (b091d70), closes #​4620
Code Refactoring
  • refactor: remove manual version checker (89458fc)
  • refactor: remove patching deps based on version checker (bac4c43)
  • refactor: deprecate RawCompilerOptions interface (2b1b6cd)
  • refactor: deprecate transform option isolatedModules (7dfef71)
microsoft/TypeScript (typescript)

v5.9.3: TypeScript 5.9.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

Downloads are available on:

v5.9.2: TypeScript 5.9

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

Downloads are available on:

v5.8.3: TypeScript 5.8.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement.

Downloads are available on:

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@reduxjs/toolkit](https://redux-toolkit.js.org) ([source](https://github.com/reduxjs/redux-toolkit)) | dependencies | minor | [`2.6.0` -> `2.11.1`](https://renovatebot.com/diffs/npm/@reduxjs%2ftoolkit/2.6.0/2.11.1) | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | devDependencies | major | [`22.13.9` -> `24.10.2`](https://renovatebot.com/diffs/npm/@types%2fnode/22.13.9/24.10.2) | | [clap](https://github.com/clap-rs/clap) | dependencies | patch | `4.5.31` -> `4.5.53` | | [ts-jest](https://kulshekhar.github.io/ts-jest) ([source](https://github.com/kulshekhar/ts-jest)) | devDependencies | minor | [`29.2.6` -> `29.4.6`](https://renovatebot.com/diffs/npm/ts-jest/29.2.6/29.4.6) | | [typescript](https://www.typescriptlang.org/) ([source](https://github.com/microsoft/TypeScript)) | devDependencies | minor | [`5.8.2` -> `5.9.3`](https://renovatebot.com/diffs/npm/typescript/5.8.2/5.9.3) | --- ### Release Notes <details> <summary>reduxjs/redux-toolkit (@&#8203;reduxjs/toolkit)</summary> ### [`v2.11.1`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.11.1) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.11.0...v2.11.1) 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: - https://redux-toolkit.js.org/introduction/getting-started#typescript - https://redux-toolkit.js.org/usage/usage-with-typescript#introduction 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 [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5152 - Update TS typecheck matrix and add TS native job by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5155 - Officially document TS support by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5158 - Tweaks to AbortSignal logic by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/5150 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.11.0...v2.11.1 ### [`v2.11.0`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.11.0) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.10.1...v2.11.0) This **feature release** upgrades our Immer dependency to v11 to pick up the additional recent performance optimizations, adds a new `refetchCachedPages` option to allow only fetching the first cached page, and fixes an issue with regex ignore paths in the immutability middleware. #### Changelog ##### Immer v11 Performance Improvements As described in the release notes for [v2.10.0](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.10.0), we recently put significant effort into profiling Immer, and contributed several PRs that aimed to optimize its update performance. v2.10.0 updated to use Immer 10.2.0, which added the first smaller set of perf updates. That included a new Immer option to disable "strict iteration" to speed up iterating copied objects, and we specifically applied that change in RTK under the assumption that standard plain JS objects as Redux state shouldn't have unusual keys anyway. Overall, this appears to boost Immer update perf by ~+20% over v10.1 depending on update scenario. [Immer v11.0.0](https://github.com/immerjs/immer/releases/tag/v11.0.0) was just released and contains the second perf PR, a major internal architectural rewrite to change the update finalization implementation from a recursive tree traversal to a set of targeted updates based on accessed and updated fields. Based on [the benchmarks in the PR](https://github.com/immerjs/immer/pull/1183), this adds another ~+5% perf boost over the improvements in v10.2, again with variations depending on update scenario. In practice, the actual improvement may be better than that - the benchmarks list includes some array update cases which actually got a bit slower (and thus drag down the overall average), and a majority of update scenarios show anywhere from **+25% to +60% faster than Immer v10.1**! As a practical example, we have an RTK Query stress test benchmark where we mount 1000 components with query hooks at once, unmount, then remount them. We ran the same benchmark steps for RTK 2.9 and Immer 10.1, and then RTK 2.10+ and Immer 11. The overall scripting time dropped by about 30% (3330ms -> 2350ms), and the amount of time spent in Immer methods and the RTK reducers dropped significantly: <img width="2561" height="1548" alt="image" src="https://github.com/user-attachments/assets/60d41234-4477-450c-a84c-5ed58ebf62ab" /> Based on this, it appears to be a major improvement overall. As with the instructions in v2.10.0: *if* by some chance your Redux app state relies on non-string keys, you can still manually call `setUseStrictIteration(true)` in your app code to retain compatibility there, but we don't expect that standard Redux apps will have to worry about that. There are still two outstanding Immer perf PRs that may offer further improvements: one that adds an optional plugin to override array methods to avoid proxy creation overhead, and another experimental tweak to shallow copying that may be better with larger object sizes. ##### New `refetchCachedPages` Option RTK Query's infinite query API was directly based on React Query's approach, including the pages cache structure and refetching behavior. By default, that means that when you trigger a refetch, both R-Q and RTKQ will try to sequentially refetch *all* pages currently in that cache entry. So, if there were 5 pages cached for an entry, they will try to fetch pages 0...4, in turn. Some users have asked for the ability to *only* refetch the first page. This can be accomplished somewhat manually by directly updating the cache entry to eliminate the old pages and then triggering a refetch, but that's admittedly not very ergonomic. We've merged a contributed PR that adds a new `refetchCachedPages` flag. This can be defined as part of infinite query endpoints, passed as an option to infinite query hooks, or passed as an option in `initiate()` calls or hook `refetch()` methods. If set to `refetchCachedPages: false`, it will only refetch the *first* page in the cache and not the remaining pages, thus shrinking the cache from N pages to 1 page. ##### Other Fixes We merged a fix to the immutability dev middleware where it was treating `ignoredPath` regexes as strings and not actually testing them correctly. #### What's Changed - Update Immer to v11 for better update performance by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5141 - fix: compare paths against Regex instances in ignoredPaths by [@&#8203;johnste](https://github.com/johnste) in https://github.com/reduxjs/redux-toolkit/pull/5124 - Add refetchCachedPages option for infinite query by [@&#8203;rossmartin](https://github.com/rossmartin) in https://github.com/reduxjs/redux-toolkit/pull/5016 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.10.1...v2.11.0 ### [`v2.10.1`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.10.1) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.10.0...v2.10.1) This **bugfix release** fixes an issue with `window` access breaking in SSR due to the byte-shaving work in 2.10. #### What's Changed - Fix window SSR breakage by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5132 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.10.0...v2.10.1 ### [`v2.10.0`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.10.0) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.9.2...v2.10.0) This **feature release** updates our Immer dep to 10.2 to pick up its performance improvements, has additional byte-shaving and internal performance updates, and fixes a `combineSlices` type issue. #### Changelog ##### Immer Performance Improvements Redux Toolkit has been built around Immer since the very first prototype in 2018. Use of Immer as the default in `createSlice` [directly eliminated accidental mutations as a class of errors in Redux apps, and drastically simplified writing immutable updates in reducers](https://redux-toolkit.js.org/usage/immer-reducers#why-immer-is-built-in). We've had various issues filed over the years asking to make Immer optional, or raising concerns about Immer's perf. Immer is indeed slower than writing immutable updates by hand, but our stance has always been that Immer's DX is absolutely worth whatever modest perf cost it might incur, and that reducers are usually not the bottleneck in Redux apps anyway - it's usually the cost of updating the UI that's more expensive. However, a year ago an issue was filed [with some specific complaints about Immer perf being very slow](https://github.com/reduxjs/redux-toolkit/issues/4793). We investigated, ran benchmarks, and [filed an Immer issue confirming that it had gotten noticeably slower over time](https://github.com/immerjs/immer/issues/1152). Immer author Michel Weststrate agreed, and said there were some potential tweaks and architectural changes that could be made, but didn't have time to look into them himself. A couple months ago, we started investigating possible Immer perf improvements ourselves, including profiling various scenarios and comparing implementations of other similar immutable update libraries. After extensive research and development, we were able to file several PRs to improve Immer's perf: a set of smaller tweaks around iteration and caching, a couple much larger architectural changes, and a potential change to copying objects. [Immer 10.2.0](https://github.com/immerjs/immer/releases/tag/v10.2.0) contains the first set of smaller perf improvements, and this RTK release updates our dependency to 10.2 to pick up those changes. One important behavior note here: Earlier versions of Immer (8, 9, 10.1) added more handling for edge cases like symbol keys in objects. These changes made sense for correctness, but also contributed to the slowdown. Immer 10.2 now includes a new `setUseStrictIteration` option to allow only copying string keys in objects (using `Object.keys()` instead of `Reflect.ownKeys()`), but keeps the option as `strict: true` for compatibility with its own users. That default will likely change in Immer 11. **For RTK 2.10.0, we specifically import and call `setUseStrictIteration(false)`, under the assumption that standard Redux state usage only involves string keys in plain JS objects!** This should provide a ~10% speedup for Immer update operations. Given that expectation, we believe this is a reasonable feature change and only needs a minor version bump. ***If* by some chance you are using symbol keys in your Redux state, or in other Immer-powered updates in your Redux app, you can easily revert to the previous behavior by calling `setUseStrictIteration(true)` in your own app code**. Based on discussions with Michel, Immer v11 should come out in the near future with additional architectural changes for better perf, including optional support for faster array methods that would be available as an Immer plugin adding ~2KB bundle size. We will likely *not* turn that plugin on by default, but recommend that users enable it if they do frequent array ops in reducers. We're happy to have contributed these perf improvements to Immer, and that they will benefit not just RTK users but *all* Immer users everywhere! You can follow the additional discussion and progress updates in [the main Immer perf update tracking issue](https://github.com/immerjs/immer/issues/1152). ##### Additional RTK Perf Improvements We've tweaked some places where we were doing repeated `filter().map().map()` calls to micro-optimize those loops. RTKQ tag invalidation was always reading from proxy-wrapped arrays when rewriting provided tags. It now reads from the plain arrays instead, providing a modest speedup. We previously found that ESBuild wasn't deduplicating imports from the same libraries in separate files bundled together (ie `import { useEffect as useEffect2/3/4/ } from 'react'`). We've restructured our internals to ensure all external imports are only pulled in once. We've done some extensive byte-shaving in various places in the codebase. The byte-shaving and import deduplication saves about 0.6K min from the RTKQ core, and 0.2K min from the RTKQ React bundle. ##### Other Changes `combineSlices` now better handles cases where `PreloadedState` might not match the incoming type, such as persisted values. #### What's Changed - Improve perf for internal map/filter ops by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5126 - Update Immer dep to 10.2 and disable strict iteration for perf by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5127 - Deduplicate imports by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5128 - Byte-shave various chunks of code by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5129 - fix(combineSlices): Infer PreloadedState properly from provided slice by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/5125 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.9.2...v2.10.0 ### [`v2.9.2`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.9.2) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.9.1...v2.9.2) This **bugfix release** fixes a potential internal data leak in SSR environments, improves handling of headers in `fetchBaseQuery`, improves `retry` handling for unexpected errors and request aborts, and fixes a longstanding issue with `prefetch` leaving an unused subscription. We've also shipped a new `graphqlRequestBaseQuery` release with updated dependencies and better error handling. #### Changelog ##### Internal Subscription Handling We had a report that a Redux SSR app had internal subscription data showing up across different requests. After investigation, this was a bug introduced by the recent [RTKQ perf optimizations](https://github.com/reduxjs/redux-toolkit/pull/5064), where the internal subscription fields were hoisted outside of the middleware setup and into `createApi` itself. This meant they existed outside of the per-store-instance lifecycle. We've reworked the logic to ensure the data is per-store again. We also fixed another issue that miscalculated when there was an active request while checking for cache entry cleanup. Note that no actual app data was leaked in this case, just the internal subscription IDs that RTKQ uses in its own middleware to track the existence of subscriptions per cache entry. ##### `fetchBaseQuery` Headers We've updated `fetchBaseQuery` to avoid setting `content-type` in cases where a non-JSONifiable value like `FormData` is being passed as the request body, so that the browser can set that content type itself. It also now sets the `accept` header based on the selected `responseHandler` (JSON or text). ##### `retry` Behavior and Cleanup The `retry` util now respects the `maxRetries` option when catching unknown errors in addition to the existing known errors logic. It also now checks the request's `AbortSignal` and will stop retrying if aborted. In conjunction with that, dispatching `resetApiState` will now abort all in-flight requests. The `prefetch` util and `usePrefetch` hook had a long-standing issue where they would create a subscription for a cache entry, but there was no way to clean up that subscription. This meant that the cache entry was effectively permanent. They now initiate the request without adding a subscription. This will fetch the cache entry and leave it in the store for the `keepUnusedDataFor` period as intended, giving your app time to actually subscribe to the value (such as prefetching the cache entry in a route handler, and then subscribing in a component). ##### `graphqlRequestBaseQuery` We've published `@rtk-query/graphql-request-base-query` v2.3.2, which updates the `graphql-request` dep to ^7. We also fixed an issue where the error handling rethrew unknown errors - it now returns `{error}` as a base query is supposed to. #### What's Changed - Fix potential subscription leakage in SSR environments by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5111 - Improve `fetchBaseQuery` default headers handling by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5112 - Respect maxRetries for unexpected errors by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5113 - fix: update graphql-request dependency to include version ^7.0.0 by [@&#8203;eyesfocus](https://github.com/eyesfocus) in https://github.com/reduxjs/redux-toolkit/pull/4987 - Add `retry` abort handling and abort on `resetApiState` by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5114 - Don't create subscriptions for prefetch calls by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5116 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.9.1...v2.9.2 ### [`v2.9.1`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.9.1) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.9.0...v2.9.1) This **bugfix release** fixes how sorted entity adapters handle duplicate IDs, tweaks the TS types for RTKQ query state cache entries to improve how the `data` field is handled, and adds better cleanup for long-running listener middleware effects. #### What's Changed - fix(entityAdapter): ensure sorted addMany keeps first occurrence of duplicate ids by [@&#8203;demyanm](https://github.com/demyanm) in https://github.com/reduxjs/redux-toolkit/pull/5097 - fix(entityAdapter): ensure sorted setMany keeps just unique IDs in state.ids by [@&#8203;demyanm](https://github.com/demyanm) in https://github.com/reduxjs/redux-toolkit/pull/5107 - fix(types): ensure non-undefined `data` on isSuccess with `exactOptionalPropertyTypes` by [@&#8203;CO0Ki3](https://github.com/CO0Ki3) in https://github.com/reduxjs/redux-toolkit/pull/5088 - Allow executing effects that have become unsubscribed to be canceled by `listenerMiddleware.clearListeners` by [@&#8203;chris-chambers](https://github.com/chris-chambers) in https://github.com/reduxjs/redux-toolkit/pull/5102 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.9.0...v2.9.1 ### [`v2.9.0`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.9.0) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.8.2...v2.9.0) This **feature release** rewrites RTK Query's internal subscription and polling systems and the `useStableQueryArgs` hook for better perf, adds automatic `AbortSignal` handling to requests still in progress when a cache entry is removed, fixes a bug with the `transformResponse` option for queries, adds a new `builder.addAsyncThunk` method, and fixes assorted other issues. #### Changelog ##### RTK Query Performance Improvements We had reports that [RTK Query could get very slow when there were thousands of subscriptions to the same cache entry](https://github.com/reduxjs/redux-toolkit/issues/5052). After investigation, we found that the internal polling logic was attempting to recalculate the minimum polling time after every new subscription was added. This was highly inefficient, as most subscriptions don't change polling settings, and it required repeated O(n) iteration over the growing list of subscriptions. We've rewritten that logic to debounce the update check and ensure a max of one polling value update per tick for the entire API instance. Related, while working on the request abort changes, testing showed that use of plain `Record`s to hold subscription data was inefficient because we have to iterate keys to check size. We've rewritten the subscription handling internals to use `Map`s instead, as well as restructuring some additional checks around in-flight requests. These two improvements drastically improved runtime perf for the thousands-of-subscriptions-one-cache-entry repro, eliminating RTK methods as visible hotspots in the perf profiles. It likely also improves perf for general usage as well. We've also changed the implementation of our internal `useStableQueryArgs` hook to avoid calling `serializeQueryArgs` on its value, which can avoid potential perf issues when a query takes a very large object as its cache key. > \[!NOTE] > The internal logic switched from serializing the query arg to doing reference checks on nested values. This means that if you are passing a non-POJO value in a query arg, such as `useSomeQuery({a: new Set()})`, *and* you have `refetchOnMountOrArgChange` enabled, this will now trigger refeteches each time as the `Set` references are now considered different based on equality instead of serialization. ##### Abort Signal Handling on Cleanup We've had numerous requests over time for various forms of "abort in-progress requests when the data is no longer needed / params change / component unmounts / some expensive request is taking too long". This is a complex topic with multiple potential use cases, and our standard answer has been that we *don't* want to abort those requests - after all, cache entries default to staying in memory for 1 minute after the last subscription is removed, so RTKQ's cache can still be updated when the request completes. That also means that it doesn't make sense to abort a request "on unmount". However, it does then make sense to abort an in-progress request if the cache entry itself is removed. Given that, we've updated our cache handling to automatically call the existing `resPromise.abort()` method in that case, triggering the `AbortSignal` attached to the `baseQuery`. The handling at that point depends on your app - `fetchBaseQuery` should handle that, a custom `baseQuery` or `queryFn` would need to listen to the `AbortSignal`. We do have [an open issue asking for further discussions of potential abort / cancelation use cases](https://github.com/reduxjs/redux-toolkit/issues/2444) and would appreciate further feedback. ##### New Options The builder callback used in `createReducer` and `createSlice.extraReducers` now has `builder.addAsyncThunk` available, which allows handling specific actions from a thunk in the same way that you could define a thunk inside `createSlice.reducers`: ```ts const slice = createSlice({ name: 'counter', initialState: { loading: false, errored: false, value: 0, }, reducers: {}, extraReducers: (builder) => builder.addAsyncThunk(asyncThunk, { pending(state) { state.loading = true }, fulfilled(state, action) { state.value = action.payload }, rejected(state) { state.errored = true }, settled(state) { state.loading = false }, }), }) ``` `createApi` and individual endpoint definitions now accept a `skipSchemaValidation` option with an array of schema types to skip, or `true` to skip validation entirely (in case you want to use a schema for its types, but the actual validation is expensive). ##### Bug Fixes The infinite query implementation accidentally changed the query internals to *always* run `transformResponse` if provided, including if you were using `upsertQueryData()`, which then broke. It's been fixed to only run on an actual query request. The internal changes to the structure of the `state.api.provided` structure broke our handling of `extractRehydrationInfo` - we've updated that to handle the changed structure. The infinite query status fields like `hasNextPage` are now a looser type of `boolean` initially, rather than strictly `false`. ##### TS Types We now export Immer's `WritableDraft` type to fix another non-portable types issue. We've added an `api.endpoints.myEndpoint.types.RawResultType` types-only field to match the other available fields. #### What's Changed - Add RawResultType as a type-only property on endpoints by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/5037 - allow passing an array of specific schemas to skip by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/5042 - fix(types): re-exporting WritableDraft from immer by [@&#8203;marinsokol5](https://github.com/marinsokol5) in https://github.com/reduxjs/redux-toolkit/pull/5015 - Remove Serialisation from useStableQueryArgs by [@&#8203;riqts](https://github.com/riqts) in https://github.com/reduxjs/redux-toolkit/pull/4996 - add addAsyncThunk method to reducer map builder by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/5007 - Only run `transformResponse` when a `query` is used by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5049 - Assorted bugfixes for 2.8.3 by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5060 - Abort pending requests if the cache entry is removed by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5061 - Update TS CI config by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5065 - Rewrite subscription handling and polling calculations for better perf by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/5064 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.8.2...v2.9.0 ### [`v2.8.2`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.8.2) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.8.1...v2.8.2) This **bugfix release** fixes a bundle size regression in RTK Query from the build and packaging changes in v2.8.0. If you're using v2.8.0 or v2.8.1, please upgrade to v2.8.2 right away to resolve that bundle size issue! #### Changelog ##### RTK Query Bundle Size In v2.8.0, we reworked our packaging setup to better support React Native. While there weren't many meaningful code changes, we did alter our bundling build config file. In the process, we lost the config options to externalize the `@reduxjs/toolkit` core when building the RTK Query nested entry points. This resulted in a regression where the RTK core code also got bundled directly into the RTK Query artifacts, resulting in a significant size increase. This release fixes the build config and restores the previous RTKQ build artifact sizes. #### What's Changed - Restructure build config to fix RTKQ externals by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4985 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.8.1...v2.8.2 ### [`v2.8.1`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.8.1) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.8.0...v2.8.1) This **bugfix release** makes an additional update to the package config to fix a regression that happened with Jest and `jest-environment-jsdom`. > \[!CAUTION] > This release had a bundle size regression. Please update to [v2.8.2](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.8.2) to resolve that issue. #### Changes ##### More Package Updates After releasing [v2.8.0](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.8.0), we got reports that [Jest tests were breaking](https://github.com/reduxjs/redux-toolkit/issues/4971). After investigation we concluded that `jest-environment-jsdom` was looking at the new `browser` package exports condition we'd added to better support JSPM, finding an ESM file containing the `export` keyword, and erroring because it doesn't support ES modules correctly. https://github.com/reduxjs/redux-toolkit/issues/4971#issuecomment-2859506562 listed several viable workarounds, but this is enough of an issue we wanted to fix it directly. We've tweaked the package exports setup again, and it appears to resolve the issue with Jest. #### What's Changed - fix: `browser` `exports` condition by [@&#8203;aryaemami59](https://github.com/aryaemami59) in https://github.com/reduxjs/redux-toolkit/pull/4973 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.8.0...v2.8.1 ### [`v2.8.0`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.8.0) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.7.0...v2.8.0) This **feature release** improves React Native compatibility by updating our package exports definitions, and adds `queryArg` as an additional parameter to infinite query page param functions. > \[!CAUTION] > This release had a bundle size regression, as well as a breakage with `jest-environment-jsdom`. Please update to [v2.8.2](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.8.2) to resolve those issues. #### Changelog ##### Package Exports and React Native Compatibility Expo and the Metro bundler have been adding improved support for the `exports` field in `package.json` files, but those changes started printing warnings due to how some of our package definitions were configured. We've reworked the package definitions (*again*!), and this should be resolved now. ##### Infinite Query Page Params The signature for the `getNext/PreviousPageParam` functions has been: ```ts ( lastPage: DataType, allPages: Array<DataType>, lastPageParam: PageParam, allPageParams: Array<PageParam>, ) => PageParam | undefined | null ``` This came directly from React Query's API and implementation. We've had some requests to make the endpoint's `queryArg` available in page param functions. For React Query, that isn't necessary because the callbacks are defined inline when you call the `useInfiniteQuery` hook, so you've already got the query arg available in scope and can use it. Since RTK Query defines these callbacks as part of the endpoint definition, the query arg isn't in scope. We've added `queryArg` as an additional 5th parameter to these functions in case it's needed. ##### Other Changes We've made a few assorted docs updates, including replacing the search implementation to now use a local index generated on build (which should be more reliable and also has a nicer results list uI), and fixing some long-standing minor docs issues. #### What's Changed - fix: React-Native package exports by [@&#8203;aryaemami59](https://github.com/aryaemami59) in https://github.com/reduxjs/redux-toolkit/pull/4887 - Add queryArg as 5th param to page param functions by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4967 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.7.0...v2.8.0 ### [`v2.7.0`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.7.0) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.6.1...v2.7.0) RTK has hit Stage 2.7! :rofl: This **feature release** adds support for Standard Schema validation in RTK Query endpoints, fixes several issues with infinite queries, improves perf when infinite queries provide tags, adds a dev-mode check for duplicate middleware, and improves reference stability in slice selectors and infinite query hooks. #### Changelog ##### Standard Schema Validation for RTK Query Apps often need to validate responses from the server, both to ensure the data is correct, and to help enforce that the data matches the expected TS types. This is typically done with schema libraries such as Zod, Valibot, and Arktype. Because of the similarities in usage APIs, those libraries and others now support a common API definition called [Standard Schema](https://standardschema.dev/), allowing you to plug your chosen validation library in anywhere Standard Schema is supported. RTK Query now supports using Standard Schema to validate query args, responses, and errors. If schemas are provided, the validations will be run and errors thrown if the data is invalid. Additionally, providing a schema allows TS inference for that type as well, allowing you to omit generic types from the endpoint. Schema usage is per-endpoint, and can look like this: ```ts import { createApi, fetchBaseQuery } from '@&#8203;reduxjs/toolkit/query/react' import * as v from 'valibot' const postSchema = v.object({ id: v.number(), name: v.string(), }) type Post = v.InferOutput<typeof postSchema> const api = createApi({ baseQuery: fetchBaseQuery({ baseUrl: '/' }), endpoints: (build) => ({ getPost: build.query({ // infer arg from here query: ({ id }: { id: number }) => `/post/${id}`, // infer result from here responseSchema: postSchema, }), getTransformedPost: build.query({ // infer arg from here query: ({ id }: { id: number }) => `/post/${id}`, // infer untransformed result from here rawResponseSchema: postSchema, // infer transformed result from here transformResponse: (response) => ({ ...response, published_at: new Date(response.published_at), }), }), }), }) ``` If desired, you can also configure schema error handling with the `catchSchemaFailure` option. You can also disable actual runtime validation with `skipSchemaValidation` (primarily useful for cases when payloads may be large and expensive to validate, but you still want to benefit from the TS type inference). See the ["Schema Validation" docs section in the `createApi` reference](https://redux-toolkit.js.org/rtk-query/api/createApi#schema-validation) and the usage guide sections on [queries](https://redux-toolkit.js.org/rtk-query/usage/queries#runtime-validation-using-schemas), infinite queries, and mutations, for more details. ##### Infinite Query Fixes This release fixes several reported issue with infinite queries: - The `lifecycleApi.updateCachedData` method is now correctly available - The `skip` option now correctly works for infinite query hooks - Infinite query `fulfilled` actions now include the `meta` field from the base query (such as `{request, response}`). For cases where multiple pages are being refetched, this will be the meta from the last page fetched. - `useInfiniteQuerySubscription` now returns stable references for `refetch` and the `fetchNext/PreviousPage` methods ##### `upsertQueryEntries`, Tags Performance and API State Structure We recently published a fix to actually process per-endpoint `providedTags` when using `upsertQueryEntries`. However, this exposed a performance issue - the internal tag handling logic was doing repeated O(n) iterations over *all* endpoint+tag entries in order to clear out existing references to that cache key. In cases where hundreds or thousands of cache entries were being inserted, this became extremely expensive. We've restructured the `state.api.provided` data structure to handle reverse-mapping between tags and cache keys, which drastically improves performance in this case. However, it's worth noting that this *is* a change to that state structure. This *shouldn't* affect apps, because the RTKQ state is intended to be treated as a black box and not generally directly accessed by user app code. However, it's possible someone may have depended on that specific state structure when writing a custom selector, in which case this would break. An actual example of this is the Redux DevTools RTKQ panel, which iterates the tags data while displaying cache entries. That *did* break with this change. Prior to releasing RTK 2.7,we released [Redux DevTools 3.2.10](https://github.com/reduxjs/redux-devtools/releases/tag/remotedev-redux-devtools-extensions%403.2.10), which includes support for both the old and new `state.api.provided` definitions. ##### TS Support Matrix Updates Following with the DefinitelyTyped support matrix, we've officially dropped support for TS 5.0, and currently support TS 5.1 - 5.8. (RTK likely still works with 5.0, but we no longer test against that in CI.) ##### Duplicate Middleware Dev Checks `configureStore` now checks the final middleware array for duplicate middleware references. This will catch cases such as accidentally adding the same RTKQ API middleware twice (such as adding `baseApi.middleware` and `injectedApi.middlweware` - these are actually the same object and same middleware). Unlike the other dev-mode checks, this is part of `configureStore` itself, not `getDefaultMiddleware()`. This can be configured via the new `duplicateMiddlewareCheck` option. ##### Other Changes `createEntityAdapter` now correctly handles adding an item and then applying multiple updates to it. The generated `combineSlices` selectors will now return the same placeholder initial state reference for a given slice, rather than returning a new initial state reference every time. `useQuery` hooks should now correctly refetch after dispatching `resetApiState`. #### What's Changed - Process multiple update for the same new entity by [@&#8203;demyanm](https://github.com/demyanm) in https://github.com/reduxjs/redux-toolkit/pull/4890 - add infinite query support for updateCachedData by [@&#8203;alexmotoc](https://github.com/alexmotoc) in https://github.com/reduxjs/redux-toolkit/pull/4905 - add infinite query skip support by [@&#8203;alexmotoc](https://github.com/alexmotoc) in https://github.com/reduxjs/redux-toolkit/pull/4906 - Cache initial state in injected scenarios by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4908 - Rewrite providedTags handling for better perf by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4910 - Allow standard schemas to validate endpoint values by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4864 - fix(rtk-query): `useQuery` hook does not refetch after `resetApiState` by [@&#8203;juniusfree](https://github.com/juniusfree) in https://github.com/reduxjs/redux-toolkit/pull/4758 - Drop TS 5.0 from compat matrix by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4925 - Add duplicate middleware dev check to configureStore by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4927 - Improve duplicate middleware error and save build output by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4928 - Add meta handling for infinite queries by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4939 - improve stability of useInfiniteQuerySubscription's return value by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4937 - Add `catchSchemaFailure`, and docs for RTKQ schema features by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4934 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.6.1...v2.7.0 ### [`v2.6.1`](https://github.com/reduxjs/redux-toolkit/releases/tag/v2.6.1) [Compare Source](https://github.com/reduxjs/redux-toolkit/compare/v2.6.0...v2.6.1) This **bugfix release** fixes several assorted types issues with the initial infinite query feature release, and adds support for an optional signal argument to `createAsyncThunk`. #### Changelog ##### Infinite Query Fixes We've fixed several types issues that were reported with infinite queries after the 2.6.0 release: - `matchFulfilled` and `providesTags` now get the correct response types - We've added pre-typed `Type*` types to represent infinite queries, similar to the existing pre-defined types for queries and mutations - `selectCachedArgsForQuery` now supports fetching args for infinite query endpoints - We fixed some TS type portability issues with infinite queries that caused errors when generating TS declarations - `useInfiniteQueryState/Subscription` now correctly expect just the query arg, not the combined `{queryArg, pageParam}` object ##### Other Improvements `createAsyncThunk` now accepts an optional `{signal}` argument. If provided, the internal AbortSignal handling will tie into that signal. `upsertQueryEntries` now correctly generates provided tags for upserted cache entries. #### What's Changed - Fix assorted infinite query types by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4869 - Add providesTags handling for upsertQueryEntries by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4872 - add infinite query type support for selectCachedArgsForQuery by [@&#8203;alexmotoc](https://github.com/alexmotoc) in https://github.com/reduxjs/redux-toolkit/pull/4880 - add more Typed wrappers and make sure they're all exported by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4866 - Fix infinite query type portability issues by [@&#8203;markerikson](https://github.com/markerikson) in https://github.com/reduxjs/redux-toolkit/pull/4881 - support passing an external abortsignal to createAsyncThunk by [@&#8203;EskiMojo14](https://github.com/EskiMojo14) in https://github.com/reduxjs/redux-toolkit/pull/4860 **Full Changelog**: https://github.com/reduxjs/redux-toolkit/compare/v2.6.0...v2.6.1 </details> <details> <summary>clap-rs/clap (clap)</summary> ### [`v4.5.53`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4553---2025-11-19) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.52...v4.5.53) ##### Features - Add `default_values_if`, `default_values_ifs` ### [`v4.5.52`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4552---2025-11-17) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.51...v4.5.52) ##### Fixes - Don't panic when `args_conflicts_with_subcommands` conflicts with an `ArgGroup` ### [`v4.5.51`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4551---2025-10-29) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.50...v4.5.51) ##### Fixes - *(help)* Correctly calculate padding for short flags that take a value - *(help)* Don't panic on short flags using `ArgAction::Count` ### [`v4.5.50`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4550---2025-10-20) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.49...v4.5.50) ##### Features - Accept `Cow` where `String` and `&str` are accepted ### [`v4.5.49`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4549---2025-10-13) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.48...v4.5.49) ##### Fixes - *(help)* Correctly wrap when ANSI escape codes are present ### [`v4.5.48`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4548---2025-09-19) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.47...v4.5.48) ##### Documentation - Add a new CLI Concepts document as another way of framing clap - Expand the `typed_derive` cookbook entry ### [`v4.5.47`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4547---2025-09-02) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.46...v4.5.47) ##### Features - Added `impl FromArgMatches for ()` - Added `impl Args for ()` - Added `impl Subcommand for ()` - Added `impl FromArgMatches for Infallible` - Added `impl Subcommand for Infallible` ##### Fixes - *(derive)* Update runtime error text to match `clap` ### [`v4.5.46`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4546---2025-08-26) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.45...v4.5.46) ##### Features - Expose `StyledStr::push_str` ### [`v4.5.45`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4545---2025-08-12) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.44...v4.5.45) ##### Fixes - *(unstable-v5)* `ValueEnum` variants now use the full doc comment, not summary, for `PossibleValue::help` ### [`v4.5.44`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4544---2025-08-11) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.43...v4.5.44) ##### Features - Add `Command::mut_subcommands` ### [`v4.5.43`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4543---2025-08-06) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.42...v4.5.43) ##### Fixes - *(help)* In long help, list Possible Values before defaults, rather than after, for a more consistent look ### [`v4.5.42`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4542---2025-07-30) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.41...v4.5.42) ##### Fixes - Include subcommand visible long aliases in `--help` ### [`v4.5.41`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4541---2025-07-09) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.40...v4.5.41) ##### Features - Add `Styles::context` and `Styles::context_value` to customize the styling of `[default: value]` like notes in the `--help` ### [`v4.5.40`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4540---2025-06-09) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.39...v4.5.40) ##### Features - Support quoted ids in `arg!()` macro (e.g. `arg!("check-config": ...)`) ### [`v4.5.39`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4539---2025-05-27) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.38...v4.5.39) ##### Fixes - *(help)* Show short flag aliases before long - *(help)* Merge the short and long flag alias lists ### [`v4.5.38`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4538---2025-05-11) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.37...v4.5.38) ##### Fixes - *(help)* When showing aliases, include leading `--` or `-` ### [`v4.5.37`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4537---2025-04-18) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.36...v4.5.37) ##### Features - Added `ArgMatches::try_clear_id()` ### [`v4.5.36`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4536---2025-04-11) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.35...v4.5.36) ##### Fixes - *(help)* Revert 4.5.35's "Don't leave space for shorts if there are none" for now ### [`v4.5.35`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4535---2025-04-01) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.34...v4.5.35) ##### Fixes - *(help)* Align positionals and flags when put in the same `help_heading` - *(help)* Don't leave space for shorts if there are none ### [`v4.5.34`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4534---2025-03-27) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.33...v4.5.34) ##### Fixes - *(help)* Don't add extra blank lines with `flatten_help(true)` and subcommands without arguments ### [`v4.5.33`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4533---2025-03-26) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.32...v4.5.33) ##### Fixes - *(error)* When showing the usage of a suggestion for an unknown argument, don't show the group ### [`v4.5.32`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#4532---2025-03-10) [Compare Source](https://github.com/clap-rs/clap/compare/v4.5.31...v4.5.32) ##### Features - Add `Error::remove` ##### Documentation - *(cookbook)* Switch from `humantime` to `jiff` - *(tutorial)* Better cover required vs optional ##### Internal - Update `pulldown-cmark` </details> <details> <summary>kulshekhar/ts-jest (ts-jest)</summary> ### [`v29.4.6`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2946-2025-12-01) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.5...v29.4.6) ##### Bug Fixes - log hybrid module as warning instead of failing tests ([#&#8203;5144](https://github.com/kulshekhar/ts-jest/issues/5144)) ([528d37c](https://github.com/kulshekhar/ts-jest/commit/528d37c125a392a4a6e44a1bf399943410298390)), closes [#&#8203;5130](https://github.com/kulshekhar/ts-jest/issues/5130) ### [`v29.4.5`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2945-2025-10-10) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.4...v29.4.5) ##### Bug Fixes - allow filtering modern module warning message with diagnostic code ([c290d4d](https://github.com/kulshekhar/ts-jest/commit/c290d4d7f68b47bc4f31b26f241b93ef667dcb72)), , closes [#&#8203;5013](https://github.com/kulshekhar/ts-jest/issues/5013) ### [`v29.4.4`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2944-2025-09-19) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.3...v29.4.4) ##### Bug Fixes - revert **29.4.3** changes ([25cb706](https://github.com/kulshekhar/ts-jest/commit/25cb7065528f7a43b6c6ee5bb33fc3f940932ccd)), closes [#&#8203;5049](https://github.com/kulshekhar/ts-jest/issues/5049) ### [`v29.4.3`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2943-2025-09-17) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.2...v29.4.3) ##### Bug Fixes - introduce `transpilation` option to replace `isolatedModules` option ([#&#8203;5044](https://github.com/kulshekhar/ts-jest/issues/5044)) ([5868761](https://github.com/kulshekhar/ts-jest/commit/58687615142d89a559ada89d12029fe29bb981f2)) ### [`v29.4.2`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2942-2025-09-15) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.1...v29.4.2) ### [`v29.4.1`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2941-2025-08-03) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.4.0...v29.4.1) ### [`v29.4.0`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2940-2025-06-11) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.3.4...v29.4.0) ##### Features - feat: support Jest 30 ([84e093e](https://github.com/kulshekhar/ts-jest/commit/84e093e)) ### [`v29.3.4`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2934-2025-05-16) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.3.3...v29.3.4) ##### Bug Fixes - fix: fix `TsJestTransformerOptions` type ([3b11e29](https://github.com/kulshekhar/ts-jest/commit/3b11e29)), closes [#&#8203;4247](https://github.com/kulshekhar/ts-jest/issues/4247) - fix(cli): fix wrong path for preset creator fns ([249eb2c](https://github.com/kulshekhar/ts-jest/commit/249eb2c)) - fix(config): disable `rewriteRelativeImportExtensions` always ([9b1f472](https://github.com/kulshekhar/ts-jest/commit/9b1f472)), closes [#&#8203;4855](https://github.com/kulshekhar/ts-jest/issues/4855) ### [`v29.3.3`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2933-2025-05-14) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.3.2...v29.3.3) ##### Bug Fixes - fix(cli): init config with preset creator functions ([cdd3039](https://github.com/kulshekhar/ts-jest/commit/cdd3039)), closes [#&#8203;4840](https://github.com/kulshekhar/ts-jest/issues/4840) - fix(config): disable `isolatedDeclarations` ([5d6b35f](https://github.com/kulshekhar/ts-jest/commit/5d6b35f)), closes [#&#8203;4847](https://github.com/kulshekhar/ts-jest/issues/4847) ### [`v29.3.2`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2932-2025-04-12) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.3.1...v29.3.2) ##### Bug Fixes - fix: transpile `js` files from `node_modules` whenever Jest asks ([968370e](https://github.com/kulshekhar/ts-jest/commit/968370e)), closes [#&#8203;4637](https://github.com/kulshekhar/ts-jest/issues/4637) ### [`v29.3.1`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2931-2025-03-31) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.3.0...v29.3.1) ##### Bug Fixes - fix: allow `isolatedModules` mode to have `ts.Program` under `Node16/Next` ([25157eb](https://github.com/kulshekhar/ts-jest/commit/25157eb)) - fix: improve message for `isolatedModules` of `ts-jest` config ([547eb6f](https://github.com/kulshekhar/ts-jest/commit/547eb6f)) ### [`v29.3.0`](https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2930-2025-03-21) [Compare Source](https://github.com/kulshekhar/ts-jest/compare/v29.2.6...v29.3.0) ##### Features - feat: support hybrid `module` values for `isolatedModules: true` ([f372121](https://github.com/kulshekhar/ts-jest/commit/f372121)) ##### Bug Fixes - fix: set `customConditions` to `undefined` in `TsCompiler` ([b091d70](https://github.com/kulshekhar/ts-jest/commit/b091d70)), closes [#&#8203;4620](https://github.com/kulshekhar/ts-jest/issues/4620) ##### Code Refactoring - refactor: remove manual version checker ([89458fc](https://github.com/kulshekhar/ts-jest/commit/89458fc)) - refactor: remove patching deps based on version checker ([bac4c43](https://github.com/kulshekhar/ts-jest/commit/bac4c43)) - refactor: deprecate `RawCompilerOptions` interface ([2b1b6cd](https://github.com/kulshekhar/ts-jest/commit/2b1b6cd)) - refactor: deprecate transform option `isolatedModules` ([7dfef71](https://github.com/kulshekhar/ts-jest/commit/7dfef71)) </details> <details> <summary>microsoft/TypeScript (typescript)</summary> ### [`v5.9.3`](https://github.com/microsoft/TypeScript/releases/tag/v5.9.3): TypeScript 5.9.3 [Compare Source](https://github.com/microsoft/TypeScript/compare/v5.9.2...v5.9.3) Note: this tag was recreated to point at the correct commit. The npm package contained the correct content. For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-9/) - [fixed issues query for Typescript 5.9.0 (Beta)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.9.0%22+is%3Aclosed+). - [fixed issues query for Typescript 5.9.1 (RC)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.9.1%22+is%3Aclosed+). - *No specific changes for TypeScript 5.9.2 (Stable)* - [fixed issues query for Typescript 5.9.3 (Stable)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.9.3%22+is%3Aclosed+). Downloads are available on: - [npm](https://www.npmjs.com/package/typescript) ### [`v5.9.2`](https://github.com/microsoft/TypeScript/releases/tag/v5.9.2): TypeScript 5.9 [Compare Source](https://github.com/microsoft/TypeScript/compare/v5.8.3...v5.9.2) Note: this tag was recreated to point at the correct commit. The npm package contained the correct content. For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-9/) - [fixed issues query for Typescript 5.9.0 (Beta)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.9.0%22+is%3Aclosed+). - [fixed issues query for Typescript 5.9.1 (RC)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.9.1%22+is%3Aclosed+). - *No specific changes for TypeScript 5.9.2 (Stable)* Downloads are available on: - [npm](https://www.npmjs.com/package/typescript) ### [`v5.8.3`](https://github.com/microsoft/TypeScript/releases/tag/v5.8.3): TypeScript 5.8.3 [Compare Source](https://github.com/microsoft/TypeScript/compare/v5.8.2...v5.8.3) Note: this tag was recreated to point at the correct commit. The npm package contained the correct content. For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-5-8/). - [fixed issues query for Typescript 5.8.0 (Beta)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.8.0%22+is%3Aclosed+). - [fixed issues query for Typescript 5.8.1 (RC)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.8.1%22+is%3Aclosed+). - [fixed issues query for Typescript 5.8.2 (Stable)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.8.2%22+is%3Aclosed+). - [fixed issues query for Typescript 5.8.3 (Stable)](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93\&q=milestone%3A%22TypeScript+5.8.3%22+is%3Aclosed+). Downloads are available on: - [npm](https://www.npmjs.com/package/typescript) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMTUuMiIsInVwZGF0ZWRJblZlciI6IjM5LjI2NC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
kjuulh added 1 commit 2025-03-26 00:25:40 +01:00
Update all dependencies 20f7c5ff1c
kjuulh force-pushed renovate/all from 20f7c5ff1c to 262e6bc3ae 2025-03-26 20:49:24 +01:00 Compare
kjuulh force-pushed renovate/all from 262e6bc3ae to cc5c60c7c3 2025-03-26 21:22:20 +01:00 Compare
kjuulh force-pushed renovate/all from cc5c60c7c3 to 44d610cfe7 2025-03-27 02:50:04 +01:00 Compare
kjuulh force-pushed renovate/all from 44d610cfe7 to 7b90be6a0d 2025-03-27 03:22:23 +01:00 Compare
kjuulh force-pushed renovate/all from 7b90be6a0d to 9fd566308f 2025-03-27 04:56:31 +01:00 Compare
kjuulh force-pushed renovate/all from 9fd566308f to 377846d555 2025-04-01 02:48:53 +02:00 Compare
kjuulh force-pushed renovate/all from 377846d555 to 943b34be77 2025-04-02 02:54:17 +02:00 Compare
kjuulh force-pushed renovate/all from 943b34be77 to d83335f49b 2025-04-03 02:51:50 +02:00 Compare
kjuulh force-pushed renovate/all from d83335f49b to 7b6b189662 2025-04-05 02:49:47 +02:00 Compare
kjuulh force-pushed renovate/all from 7b6b189662 to 9481e452ff 2025-04-12 02:55:07 +02:00 Compare
kjuulh force-pushed renovate/all from 9481e452ff to d7b1f830ec 2025-04-14 02:48:45 +02:00 Compare
kjuulh force-pushed renovate/all from d7b1f830ec to ba88705f7c 2025-04-17 02:47:50 +02:00 Compare
kjuulh force-pushed renovate/all from ba88705f7c to 05537190b5 2025-04-19 02:51:30 +02:00 Compare
kjuulh force-pushed renovate/all from 05537190b5 to df260e7982 2025-04-19 05:48:51 +02:00 Compare
kjuulh force-pushed renovate/all from df260e7982 to 6952790e86 2025-04-25 02:52:14 +02:00 Compare
kjuulh force-pushed renovate/all from 6952790e86 to b7b20d5fe8 2025-04-26 02:51:34 +02:00 Compare
kjuulh force-pushed renovate/all from b7b20d5fe8 to ccd06b7037 2025-04-29 02:56:50 +02:00 Compare
kjuulh force-pushed renovate/all from ccd06b7037 to 19cfdbd434 2025-05-06 02:49:18 +02:00 Compare
kjuulh force-pushed renovate/all from 19cfdbd434 to 3131ad6266 2025-05-06 05:48:40 +02:00 Compare
kjuulh force-pushed renovate/all from 3131ad6266 to be6431b02b 2025-05-07 02:53:09 +02:00 Compare
kjuulh force-pushed renovate/all from be6431b02b to a062a312c6 2025-05-08 02:50:31 +02:00 Compare
kjuulh force-pushed renovate/all from a062a312c6 to f5773bea06 2025-05-08 05:47:11 +02:00 Compare
kjuulh force-pushed renovate/all from f5773bea06 to 5070020dfa 2025-05-09 02:48:58 +02:00 Compare
kjuulh force-pushed renovate/all from 5070020dfa to 4e7e9c5289 2025-05-11 05:50:24 +02:00 Compare
kjuulh force-pushed renovate/all from 4e7e9c5289 to 3b1b385faa 2025-05-12 02:52:40 +02:00 Compare
kjuulh force-pushed renovate/all from 3b1b385faa to 821da9afcf 2025-05-15 02:49:18 +02:00 Compare
kjuulh force-pushed renovate/all from 821da9afcf to 0a2eadc428 2025-05-17 02:48:48 +02:00 Compare
kjuulh force-pushed renovate/all from 0a2eadc428 to 98aa123b31 2025-05-19 02:48:12 +02:00 Compare
kjuulh force-pushed renovate/all from 98aa123b31 to 6e2c651ad5 2025-05-21 02:49:46 +02:00 Compare
kjuulh force-pushed renovate/all from 6e2c651ad5 to 4ddec1f004 2025-05-28 02:55:17 +02:00 Compare
kjuulh force-pushed renovate/all from 4ddec1f004 to 982f7bf03f 2025-05-29 02:51:39 +02:00 Compare
kjuulh force-pushed renovate/all from 982f7bf03f to 15ace0135d 2025-05-30 02:52:47 +02:00 Compare
kjuulh force-pushed renovate/all from 15ace0135d to c850390a35 2025-05-31 02:52:02 +02:00 Compare
kjuulh force-pushed renovate/all from c850390a35 to ec86469337 2025-06-06 02:54:39 +02:00 Compare
kjuulh force-pushed renovate/all from ec86469337 to 7924f5db18 2025-06-10 02:59:55 +02:00 Compare
kjuulh force-pushed renovate/all from 7924f5db18 to 972683d5ad 2025-06-10 05:56:10 +02:00 Compare
kjuulh force-pushed renovate/all from 972683d5ad to aa92a58060 2025-06-13 02:56:14 +02:00 Compare
kjuulh force-pushed renovate/all from aa92a58060 to a4fed7ae23 2025-06-18 02:52:50 +02:00 Compare
kjuulh force-pushed renovate/all from a4fed7ae23 to 49b37aef8f 2025-06-25 02:51:22 +02:00 Compare
kjuulh force-pushed renovate/all from 49b37aef8f to 684541d930 2025-06-29 02:51:44 +02:00 Compare
kjuulh force-pushed renovate/all from 684541d930 to 37f8cf6090 2025-07-02 03:13:37 +02:00 Compare
kjuulh force-pushed renovate/all from 37f8cf6090 to 51dc213a36 2025-07-09 02:57:06 +02:00 Compare
kjuulh force-pushed renovate/all from 51dc213a36 to 442ad1d348 2025-07-10 02:55:14 +02:00 Compare
kjuulh force-pushed renovate/all from 442ad1d348 to 0ae0dc48e6 2025-07-10 05:53:26 +02:00 Compare
kjuulh force-pushed renovate/all from 0ae0dc48e6 to d9bd11f698 2025-07-11 02:59:40 +02:00 Compare
kjuulh force-pushed renovate/all from d9bd11f698 to 69fe70d300 2025-07-16 03:00:33 +02:00 Compare
kjuulh force-pushed renovate/all from 69fe70d300 to 2d888638ee 2025-07-19 02:59:47 +02:00 Compare
kjuulh force-pushed renovate/all from 2d888638ee to 59d20e5248 2025-11-13 03:48:50 +01:00 Compare
kjuulh force-pushed renovate/all from 59d20e5248 to 8aa4de2d4b 2025-11-13 05:52:09 +01:00 Compare
kjuulh force-pushed renovate/all from 8aa4de2d4b to fd1be0bf51 2025-11-18 03:03:46 +01:00 Compare
kjuulh force-pushed renovate/all from fd1be0bf51 to 427f997001 2025-11-18 06:03:36 +01:00 Compare
kjuulh force-pushed renovate/all from 427f997001 to 6ae4ef4a33 2025-11-20 03:04:52 +01:00 Compare
kjuulh force-pushed renovate/all from 6ae4ef4a33 to 55537ff44b 2025-11-20 06:00:56 +01:00 Compare
kjuulh force-pushed renovate/all from 55537ff44b to e57f38bca9 2025-11-24 02:59:16 +01:00 Compare
kjuulh force-pushed renovate/all from e57f38bca9 to 6be1f23cbd 2025-11-29 06:03:13 +01:00 Compare
kjuulh force-pushed renovate/all from 6be1f23cbd to 702d233f7e 2025-12-02 02:58:40 +01:00 Compare
kjuulh force-pushed renovate/all from 702d233f7e to 8a6e44cc83 2025-12-08 05:59:39 +01:00 Compare
kjuulh force-pushed renovate/all from 8a6e44cc83 to fe28cb922e 2025-12-09 03:04:56 +01:00 Compare
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/all:renovate/all
git checkout renovate/all
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kjuulh
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kjuulh/vidow#451
No description provided.
Delete Branch "renovate/all"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?