[Snyk] Upgrade @reduxjs/toolkit from 2.9.1 to 2.9.2 #100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade @reduxjs/toolkit from 2.9.1 to 2.9.2.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 1 version ahead of your current version.
The recommended version was released a month ago.
Release notes
Package name: @reduxjs/toolkit
-
2.9.2 - 2025-10-22
- Fix potential subscription leakage in SSR environments by @ markerikson in #5111
- Improve
- Respect maxRetries for unexpected errors by @ markerikson in #5113
- fix: update graphql-request dependency to include version ^7.0.0 by @ eyesfocus in #4987
- Add
- Don't create subscriptions for prefetch calls by @ markerikson in #5116
-
2.9.1 - 2025-10-17
- fix(entityAdapter): ensure sorted addMany keeps first occurrence of duplicate ids by @ demyanm in #5097
- fix(entityAdapter): ensure sorted setMany keeps just unique IDs in state.ids by @ demyanm in #5107
- fix(types): ensure non-undefined
- Allow executing effects that have become unsubscribed to be canceled by
from @reduxjs/toolkit GitHub release notesThis bugfix release fixes a potential internal data leak in SSR environments, improves handling of headers in
fetchBaseQuery, improvesretryhandling for unexpected errors and request aborts, and fixes a longstanding issue withprefetchleaving an unused subscription. We've also shipped a newgraphqlRequestBaseQueryrelease 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
createApiitself. 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.
fetchBaseQueryHeadersWe've updated
fetchBaseQueryto avoid settingcontent-typein cases where a non-JSONifiable value likeFormDatais being passed as the request body, so that the browser can set that content type itself. It also now sets theacceptheader based on the selectedresponseHandler(JSON or text).retryBehavior and CleanupThe
retryutil now respects themaxRetriesoption when catching unknown errors in addition to the existing known errors logic. It also now checks the request'sAbortSignaland will stop retrying if aborted.In conjunction with that, dispatching
resetApiStatewill now abort all in-flight requests.The
prefetchutil andusePrefetchhook 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 thekeepUnusedDataForperiod 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).graphqlRequestBaseQueryWe've published
@ rtk-query/graphql-request-base-queryv2.3.2, which updates thegraphql-requestdep 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
fetchBaseQuerydefault headers handling by @ markerikson in #5112retryabort handling and abort onresetApiStateby @ markerikson in #5114Full Changelog: v2.9.1...v2.9.2
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
datafield is handled, and adds better cleanup for long-running listener middleware effects.What's Changed
dataon isSuccess withexactOptionalPropertyTypesby @ CO0Ki3 in #5088listenerMiddleware.clearListenersby @ chris-chambers in #5102Full Changelog: v2.9.0...v2.9.1
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: