fix(deps): update all non-major dependencies#1633
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
6624fd7 to
27f1af0
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
27f1af0 to
f3377c0
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
f3377c0 to
85ee723
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
85ee723 to
e863513
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
e863513 to
293a208
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
293a208 to
4cd3075
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
4cd3075 to
f036757
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
f036757 to
bc80e20
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
bc80e20 to
9794c3d
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
9794c3d to
0e808f9
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
0e808f9 to
594dec3
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
594dec3 to
86b0b62
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
86b0b62 to
7279d2f
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
7279d2f to
fd5c1af
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
f74a0ac to
e08674a
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
e08674a to
d22b924
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
d22b924 to
6b2c77d
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
6b2c77d to
134239a
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
134239a to
2db45e4
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
2db45e4 to
22d5cf2
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
22d5cf2 to
51ba5e9
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
51ba5e9 to
267aeb6
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
267aeb6 to
ad6806f
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
ad6806f to
3cfae53
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
3cfae53 to
2b33dcd
Compare
|
🚀 Storybook has been deployed to staging: https://unraid-ui-storybook-staging.unraid-workers.workers.dev |
|
This plugin has been deployed to Cloudflare R2 and is available for testing. |
This PR contains the following updates:
9.34.0->9.35.04.5.1->4.5.24.6.3->4.7.00.25.0->0.25.14.0.0-alpha.0->4.0.0-alpha.12.8.2->2.9.04.49.0->4.50.19.1.3->9.1.59.1.3->9.1.59.1.3->9.1.59.1.3->9.1.54.1.12->4.1.134.1.12->4.1.1322.18.0->22.18.17.7.0->7.7.18.41.0->8.43.013.8.0->13.9.013.8.0->13.9.013.8.0->13.9.013.8.0->13.9.05.6.0->5.6.21.11.14->1.11.184.0.7->4.0.817.2.1->17.2.29.34.0->9.35.09.1.3->9.1.54.2.0->4.3.05.5.0->5.6.014.4.7->14.4.814.4.7->14.4.814.4.7->14.4.86.0.13->6.1.06.0.13->6.1.06.0.13->6.1.016.1.5->16.1.60.542.0->0.543.03.19.0->3.19.122.18.0->22.19.022.18.0->22.19.022.18.0-bookworm-slim->22.19.0-bookworm-slim6.6.4->6.7.19.9.0->9.9.46.0.8->6.0.1010.15.0->10.15.110.15.0->10.15.110.15.0->10.15.18.1.0->8.1.19.1.3->9.1.54.1.12->4.1.134.1.12->4.1.135.43.1->5.44.01.3.7->1.3.81.3.7->1.3.88.41.0->8.43.07.1.3->7.1.53.5.20->3.5.213.5.20->3.5.2111.1.11->11.1.123.9.6->3.9.74.33.0->4.34.0Release Notes
eslint/eslint (@eslint/js)
v9.35.0Compare Source
dotansimha/graphql-code-generator (@graphql-codegen/typescript-resolvers)
v4.5.2Compare Source
Patch Changes
2fc3869Thanks @chdanielmueller! - Fix enum resolver for partially mapped enumValuesianvs/prettier-plugin-sort-imports (@ianvs/prettier-plugin-sort-imports)
v4.7.0Compare Source
What's Changed
This project began as a fork because I wanted a plugin that would not move side-effect imports around and mess with my CSS cascade. So its first and most distinguishing feature is that side-effect imports do not move, and other imports are not sorted across them.
This works fine in most cases, but some people have side-effect imports that they know can be sorted safely. For those, there is now an "escape hatch" option named
importOrderSafeSideEffects. It is an array of glob pattern strings (similar toimportOrder) which, when they match against a side-effect import, allow that import to be sorted as if it were a standard import.Suggestions for safe use:
^at the start of your pattern and$at the end, to avoid accidentally matching part of an import name. For example,"^server-only$", to avoid matching againstimport "not-server-only".// prettier-ignoreto stop sorting a particular import that would otherwise be sorted.Feedback on this feature is welcome.
Features
importOrderSafeSideEffectsoption by @IanVS in IanVS#240Internal
Full Changelog: IanVS/prettier-plugin-sort-imports@v4.6.3...v4.7.0
Thinkmill/manypkg (@manypkg/cli)
v0.25.1Compare Source
Patch Changes
5854938Thanks @jasekiw! - Keep detected line endings flavor ofpackage.jsonfiles on Windows when updating those filesnuxt/ui (@nuxt/ui)
v4.0.0-alpha.1Compare Source
⚠ BREAKING CHANGES
nullifymodifier tonullableand addoptional(#4838)Accordion(#4734)PageMarquee(#4741)ButtonGroup(#4596)ai-sdkto v5 (#4698)Features
nullifymodifier tonullableand addoptional(#4838) (83b0306)ai-sdkto v5 (#4698) (de7822f)ButtonGroup(#4596) (a0963eb)@nuxt/ui-procomponents (#4675) (5cb65cf)PageMarquee(#4741) (b6edce2)Accordion(#4734) (f70a3ff)Bug Fixes
errorfrom form field (#4738) (00dfb6b)ui.modalwork (946c2ec)[@source](https://redirect.github.com/source)on components (a16465f), closes #4773reduxjs/redux-toolkit (@reduxjs/toolkit)
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 #5049Full Changelog: reduxjs/redux-toolkit@v2.8.2...v2.9.0
rollup/rollup (@rollup/rollup-linux-x64-gnu)
v4.50.1Compare Source
2025-09-07
Bug Fixes
Pull Requests
v4.50.0Compare Source
2025-08-31
Features
Bug Fixes
Pull Requests
storybookjs/storybook (@storybook/addon-docs)
v9.1.5Compare Source
satisfies x as ysyntax - #32169, thanks @diagramatics!v9.1.4Compare Source
docgenoption to disable docgen processing - #32319, thanks @copilot-swe-agent!@sveltejs/vite-plugin-sveltev6 - #32320, thanks @JReinhold!tailwindlabs/tailwindcss (@tailwindcss/cli)
v4.1.13Compare Source
Changed
Fixed
visibilitywhen usingtransition(#18795)matchVariantvalues (#18798)clipwithclip-pathinsr-only(#18769)matchUtilities(#18820).vercelfolders by default (can be overridden by@source …rules) (#18855)@-to be invalid (e.g.@-2xl:flex) (#18869)-or_(#18867, #18872)ariatheme keys to@custom-variant(#18815)datatheme keys to@custom-variant(#18816)supportstheme keys to@custom-variant(#18817)typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.43.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
[
v8.42.0](https://redirect.github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.