fix(deps): update all dependencies #458
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.11.112.4.1->14.0.09.0.2->10.0.010.4.20->10.4.221.8.1->1.13.27.0.6->7.1.28.5.3->8.5.616.1.0->16.1.13.5.3->3.7.48.5.7->8.5.95.8.2->5.9.3Release Notes
reduxjs/redux-toolkit (@reduxjs/toolkit)
v2.11.1Compare Source
This bugfix release fixes an issue with our internal
AbortSignalhandling 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
tsgorelease. 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
resetApiStateandretry()could lead to an error calling anAbortController. We've restructured ourAbortControllerhandling 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.0Compare Source
This feature release upgrades our Immer dependency to v11 to pick up the additional recent performance optimizations, adds a new
refetchCachedPagesoption 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:
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
refetchCachedPagesOptionRTK 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
refetchCachedPagesflag. This can be defined as part of infinite query endpoints, passed as an option to infinite query hooks, or passed as an option ininitiate()calls or hookrefetch()methods. If set torefetchCachedPages: 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
ignoredPathregexes 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.1Compare Source
This bugfix release fixes an issue with
windowaccess 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.0Compare 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
combineSlicestype 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
createSlicedirectly 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
setUseStrictIterationoption to allow only copying string keys in objects (usingObject.keys()instead ofReflect.ownKeys()), but keeps the option asstrict: truefor 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
combineSlicesnow better handles cases wherePreloadedStatemight 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.2Compare Source
This 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 https://github.com/reduxjs/redux-toolkit/pull/5112retryabort handling and abort onresetApiStateby @markerikson in https://github.com/reduxjs/redux-toolkit/pull/5114Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.9.1...v2.9.2
v2.9.1Compare 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
datafield is handled, and adds better cleanup for long-running listener middleware effects.What's Changed
dataon isSuccess withexactOptionalPropertyTypesby @CO0Ki3 in https://github.com/reduxjs/redux-toolkit/pull/5088listenerMiddleware.clearListenersby @chris-chambers in https://github.com/reduxjs/redux-toolkit/pull/5102Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.9.0...v2.9.1
v2.9.0Compare Source
This feature release rewrites RTK Query's internal subscription and polling systems and the
useStableQueryArgshook for better perf, adds automaticAbortSignalhandling to requests still in progress when a cache entry is removed, fixes a bug with thetransformResponseoption for queries, adds a newbuilder.addAsyncThunkmethod, 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 useMaps 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
useStableQueryArgshook to avoid callingserializeQueryArgson its value, which can avoid potential perf issues when a query takes a very large object as its cache key.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 theAbortSignalattached to thebaseQuery. The handling at that point depends on your app -fetchBaseQueryshould handle that, a custombaseQueryorqueryFnwould need to listen to theAbortSignal.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
createReducerandcreateSlice.extraReducersnow hasbuilder.addAsyncThunkavailable, which allows handling specific actions from a thunk in the same way that you could define a thunk insidecreateSlice.reducers:createApiand individual endpoint definitions now accept askipSchemaValidationoption with an array of schema types to skip, ortrueto 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
transformResponseif provided, including if you were usingupsertQueryData(), 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.providedstructure broke our handling ofextractRehydrationInfo- we've updated that to handle the changed structure.The infinite query status fields like
hasNextPageare now a looser type ofbooleaninitially, rather than strictlyfalse.TS Types
We now export Immer's
WritableDrafttype to fix another non-portable types issue.We've added an
api.endpoints.myEndpoint.types.RawResultTypetypes-only field to match the other available fields.What's Changed
transformResponsewhen aqueryis used by @markerikson in https://github.com/reduxjs/redux-toolkit/pull/5049Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v2.8.2...v2.9.0
v2.8.2Compare 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/toolkitcore 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.1Compare 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-jsdomwas looking at the newbrowserpackage exports condition we'd added to better support JSPM, finding an ESM file containing theexportkeyword, 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
browserexportscondition 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.0Compare Source
This feature release improves React Native compatibility by updating our package exports definitions, and adds
queryArgas 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
exportsfield inpackage.jsonfiles, 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/PreviousPageParamfunctions has been:This came directly from React Query's API and implementation.
We've had some requests to make the endpoint's
queryArgavailable in page param functions. For React Query, that isn't necessary because the callbacks are defined inline when you call theuseInfiniteQueryhook, 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
queryArgas 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.0Compare 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
catchSchemaFailureoption. 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
createApireference 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.updateCachedDatamethod is now correctly availableskipoption now correctly works for infinite query hooksfulfilledactions now include themetafield 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.useInfiniteQuerySubscriptionnow returns stable references forrefetchand thefetchNext/PreviousPagemethodsupsertQueryEntries, Tags Performance and API State StructureWe recently published a fix to actually process per-endpoint
providedTagswhen 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.provideddata 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.provideddefinitions.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
configureStorenow 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.middlewareandinjectedApi.middlweware- these are actually the same object and same middleware).Unlike the other dev-mode checks, this is part of
configureStoreitself, notgetDefaultMiddleware().This can be configured via the new
duplicateMiddlewareCheckoption.Other Changes
createEntityAdapternow correctly handles adding an item and then applying multiple updates to it.The generated
combineSlicesselectors will now return the same placeholder initial state reference for a given slice, rather than returning a new initial state reference every time.useQueryhooks should now correctly refetch after dispatchingresetApiState.What's Changed
useQueryhook does not refetch afterresetApiStateby @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.1Compare 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:
matchFulfilledandprovidesTagsnow get the correct response typesType*types to represent infinite queries, similar to the existing pre-defined types for queries and mutationsselectCachedArgsForQuerynow supports fetching args for infinite query endpointsuseInfiniteQueryState/Subscriptionnow correctly expect just the query arg, not the combined{queryArg, pageParam}objectOther Improvements
createAsyncThunknow accepts an optional{signal}argument. If provided, the internal AbortSignal handling will tie into that signal.upsertQueryEntriesnow 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
LuckyPennySoftware/MediatR (Mediatr)
v14.0.0What's Changed
Full Changelog: https://github.com/LuckyPennySoftware/MediatR/compare/v13.1.0...v14.0.0
v13.1.0What's Changed
LightInject,StashBox,Lamarby @jithu7432 in https://github.com/LuckyPennySoftware/MediatR/pull/1137New Contributors
Full Changelog: https://github.com/LuckyPennySoftware/MediatR/compare/v13.0.0...v13.1.0
v13.0.0Full Changelog: https://github.com/LuckyPennySoftware/MediatR/compare/v12.5.0...v13.0.0
To set your license key:
You can obtain your license key at MediatR.io
v12.5.0What's Changed
Nullableproperty fromMediatR.Contractsby @jithu7432 in https://github.com/jbogard/MediatR/pull/1061New Contributors
Full Changelog: https://github.com/jbogard/MediatR/compare/v12.4.1...v12.5.0
dotnet/dotnet (Microsoft.AspNetCore.Authentication.OpenIdConnect)
v9.0.7: .NET 9.0.7You can build .NET 9.0 from the repository by cloning the release tag
v9.0.7and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v9.0.6: .NET 9.0.6You can build .NET 9.0 from the repository by cloning the release tag
v9.0.6and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v9.0.5: .NET 9.0.5You can build .NET 9.0 from the repository by cloning the release tag
v9.0.5and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v9.0.4: .NET 9.0.4You can build .NET 9.0 from the repository by cloning the release tag
v9.0.4and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v9.0.3: .NET 9.0.3You can build .NET 9.0 from the repository by cloning the release tag
v9.0.3and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
postcss/autoprefixer (autoprefixer)
v10.4.22Compare Source
stretchprefixes on new Can I Use database.fraction.js.v10.4.21Compare Source
-moz-prefix for:placeholder-shown(by @Marukome0743).axios/axios (axios)
v1.13.2Compare Source
Bug Fixes
Performance Improvements
Contributors to this release
v1.13.1Compare Source
Bug Fixes
Contributors to this release
v1.13.0Compare Source
Bug Fixes
Features
Contributors to this release
1.12.2 (2025-09-14)
Bug Fixes
Contributors to this release
1.12.1 (2025-09-12)
Bug Fixes
Contributors to this release
v1.12.2Compare Source
Bug Fixes
Contributors to this release
v1.12.1Compare Source
Bug Fixes
Contributors to this release
v1.12.0Compare Source
Bug Fixes
Features
Contributors to this release
v1.11.0Compare Source
Bug Fixes
Contributors to this release
v1.10.0Compare Source
Bug Fixes
Features
Contributors to this release
v1.9.0Compare Source
Bug Fixes
getSetCookieby using 'get' method for caseless access; (#6874) (d4f7df4)Features
Contributors to this release
1.8.4 (2025-03-19)
Bug Fixes
allowAbsoluteUrls: falsewithoutbaseURL(#6833) (f10c2e0)Contributors to this release
1.8.3 (2025-03-10)
Bug Fixes
allowAbsoluteUrlstobuildFullPathinxhrandfetchadapters (#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
generateStringto platform utils to avoid importing crypto module into client builds; (#6789) (36a5a62)Contributors to this release
v1.8.4Compare Source
Bug Fixes
allowAbsoluteUrls: falsewithoutbaseURL(#6833) (f10c2e0)Contributors to this release
v1.8.3Compare Source
Bug Fixes
allowAbsoluteUrlstobuildFullPathinxhrandfetchadapters (#6814) (ec159e5)Contributors to this release
v1.8.2Compare Source
Bug Fixes
Contributors to this release
cssnano/cssnano (cssnano)
v7.1.2: v7.1.2Compare Source
What's Changed
Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@7.1.1...cssnano@7.1.2
v7.1.1: v71.1.1Compare Source
Bug Fixes
linear()from stripping%from value 0 by @cernymatej in https://github.com/cssnano/cssnano/pull/1720Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@7.1.0...cssnano@7.1.1
v7.1.0Compare Source
Changes
v7.0.7Compare 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.6Compare Source
ContainerWithChildrentype discriminating (by @Goodwine).v8.5.5Compare Source
package.json→exportscompatibility with some tools (by @JounQin).v8.5.4Compare Source
postcss/postcss-import (postcss-import)
v16.1.1Compare Source
prettier/prettier (prettier)
v3.7.4Compare Source
diff
LWC: Avoid quote around interpolations (#18383 by @kovsu)
TypeScript: Fix comment inside union type gets duplicated (#18393 by @fisker)
TypeScript: Fix unstable comment print in union type comments (#18395 by @fisker)
v3.7.3Compare Source
diff
API: Fix
prettier.getFileInfo()change that breaks VSCode extension (#18375 by @fisker)An internal refactor accidentally broke the VSCode extension plugin loading.
v3.7.2Compare Source
diff
JavaScript: Fix string print when switching quotes (#18351 by @fisker)
JavaScript: Preserve quote for embedded HTML attribute values (#18352 by @kovsu)
TypeScript: Fix comment in empty type literal (#18364 by @fisker)
v3.7.1Compare Source
diff
API: Fix performance regression in doc printer (#18342 by @fisker)
Prettier 3.7.0 can be very slow when formatting big files, the regression has been fixed.
v3.7.0Compare Source
diff
🔗 Release Notes
v3.6.2Compare Source
diff
Markdown: Add missing blank line around code block (#17675 by @fisker)
v3.6.1Compare Source
diff
TypeScript: Allow const without initializer (#17650, #17654 by @fisker)
Miscellaneous: Avoid closing files multiple times (#17665 by @43081j)
When reading a file to infer the interpreter from a shebang, we use the
n-readlineslibrary to read the first line in order to get the shebang.This library closes files when it reaches EOF, and we later try close the same
files again. We now close files only if
n-readlinesdid not already closethem.
v3.6.0Compare Source
diff
🔗 Release Notes
Andarist/react-textarea-autosize (react-textarea-autosize)
v8.5.9Compare Source
Patch Changes
#417
cbced4fThanks @threepointone! - Addededge-lightandworkerdconditions topackage.jsonmanifest 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.8Compare Source
Patch Changes
d12e6a5Thanks @benjaminwaterlot! - Fixed a race condition leading to an error caused by textarea being unmounted before internalrequestAnimationFrame's callback being firedmicrosoft/TypeScript (typescript)
v5.9.3: TypeScript 5.9.3Compare 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.9Compare 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.3Compare 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.
This PR has been generated by Renovate Bot.
d9170c3827to5db1e7c6f25db1e7c6f2toa45f3caa87a45f3caa87to4bac2aa2594bac2aa259toec2f0d5fc5ec2f0d5fc5to0e1dbacd5e0e1dbacd5etofb9ee60e06fb9ee60e06to0006e762290006e76229tofa1e6f4b99fa1e6f4b99to583eadafd5583eadafd5toc9fdddac10c9fdddac10tod7469c81c7d7469c81c7tobac47bfd6cbac47bfd6ctod4c8ba67f7d4c8ba67f7to02a20c35df02a20c35dfto85a4f5757385a4f57573tobf4ca19d21bf4ca19d21tob216d52007b216d52007to60f128d14360f128d143toc076c81439c076c81439to47565a761647565a7616to5b9e914a015b9e914a01to8e7097e8d78e7097e8d7toe916b96df4e916b96df4to71c143ff8171c143ff81tobe8bc32f43View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.