fix(deps): update all dependencies #458
Loading…
x
Reference in New Issue
Block a user
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?
This PR contains the following updates:
2.6.0
->2.8.2
12.4.1
->12.5.0
10.4.20
->10.4.21
1.8.1
->1.9.0
7.0.6
->7.0.7
8.5.3
->8.5.4
8.5.7
->8.5.9
5.8.2
->5.8.3
Release Notes
reduxjs/redux-toolkit (@reduxjs/toolkit)
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
.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 newbrowser
package exports condition we'd added to better support JSPM, finding an ESM file containing theexport
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
browser
exports
condition by @aryaemami59 in https://github.com/reduxjs/redux-toolkit/pull/4973Full 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.Changelog
Package Exports and React Native Compatibility
Expo and the Metro bundler have been adding improved support for the
exports
field inpackage.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: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 theuseInfiniteQuery
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:
If desired, you can also configure schema error handling with the
catchSchemaFailure
option. You can also disable actual runtime validation withskipSchemaValidation
(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:
lifecycleApi.updateCachedData
method is now correctly availableskip
option now correctly works for infinite query hooksfulfilled
actions now include themeta
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 forrefetch
and thefetchNext/PreviousPage
methodsupsertQueryEntries
, Tags Performance and API State StructureWe recently published a fix to actually process per-endpoint
providedTags
when usingupsertQueryEntries
. 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 newstate.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 addingbaseApi.middleware
andinjectedApi.middlweware
- these are actually the same object and same middleware).Unlike the other dev-mode checks, this is part of
configureStore
itself, notgetDefaultMiddleware()
.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 dispatchingresetApiState
.What's Changed
useQuery
hook does not refetch afterresetApiState
by @juniusfree in https://github.com/reduxjs/redux-toolkit/pull/4758catchSchemaFailure
, and docs for RTKQ schema features by @EskiMojo14 in https://github.com/reduxjs/redux-toolkit/pull/4934Full 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
andprovidesTags
now get the correct response typesType*
types to represent infinite queries, similar to the existing pre-defined types for queries and mutationsselectCachedArgsForQuery
now supports fetching args for infinite query endpointsuseInfiniteQueryState/Subscription
now correctly expect just the query arg, not the combined{queryArg, pageParam}
objectOther 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
jbogard/MediatR (Mediatr)
v12.5.0
What's Changed
Nullable
property fromMediatR.Contracts
by @jithu7432 in https://github.com/jbogard/MediatR/pull/1061New Contributors
Full Changelog: https://github.com/jbogard/MediatR/compare/v12.4.1...v12.5.0
postcss/autoprefixer (autoprefixer)
v10.4.21
Compare Source
-moz-
prefix for:placeholder-shown
(by @Marukome0743).axios/axios (axios)
v1.9.0
Compare Source
Bug Fixes
getSetCookie
by using 'get' method for caseless access; (#6874) (d4f7df4)Features
Contributors to this release
1.8.4 (2025-03-19)
Bug Fixes
allowAbsoluteUrls: false
withoutbaseURL
(#6833) (f10c2e0)Contributors to this release
1.8.3 (2025-03-10)
Bug Fixes
allowAbsoluteUrls
tobuildFullPath
inxhr
andfetch
adapters (#6814) (ec159e5)Contributors to this release
1.8.2 (2025-03-07)
Bug Fixes
Contributors to this release
1.8.1 (2025-02-26)
Bug Fixes
generateString
to platform utils to avoid importing crypto module into client builds; (#6789) (36a5a62)Contributors to this release
v1.8.4
Compare Source
Bug Fixes
allowAbsoluteUrls: false
withoutbaseURL
(#6833) (f10c2e0)Contributors to this release
v1.8.3
Compare Source
Bug Fixes
allowAbsoluteUrls
tobuildFullPath
inxhr
andfetch
adapters (#6814) (ec159e5)Contributors to this release
v1.8.2
Compare Source
Bug Fixes
Contributors to this release
cssnano/cssnano (cssnano)
v7.0.7
Compare Source
What's Changed
Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@7.0.6...cssnano@7.0.7
postcss/postcss (postcss)
v8.5.4
Compare Source
Andarist/react-textarea-autosize (react-textarea-autosize)
v8.5.9
Compare Source
Patch Changes
#417
cbced4f
Thanks @threepointone! - Addededge-light
andworkerd
conditions topackage.json
manifest to better serve users using Vercel Edge and Cloudflare Workers.This lets tools like Wrangler and the Cloudflare Vite Plugin pick up the right version of the built module, preventing issues like https://github.com/cloudflare/workers-sdk/issues/8723.
v8.5.8
Compare Source
Patch Changes
d12e6a5
Thanks @benjaminwaterlot! - Fixed a race condition leading to an error caused by textarea being unmounted before internalrequestAnimationFrame
's callback being firedmicrosoft/TypeScript (typescript)
v5.8.3
: TypeScript 5.8.3Compare Source
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.
This PR has been generated by Renovate Bot.
d9170c3827
to5db1e7c6f2
5db1e7c6f2
toa45f3caa87
a45f3caa87
to4bac2aa259
4bac2aa259
toec2f0d5fc5
ec2f0d5fc5
to0e1dbacd5e
0e1dbacd5e
tofb9ee60e06
fb9ee60e06
to0006e76229
0006e76229
tofa1e6f4b99
fa1e6f4b99
to583eadafd5
Checkout
From your project repository, check out a new branch and test the changes.