chore(deps): update dependency @reduxjs/toolkit to v2.11.2#535
chore(deps): update dependency @reduxjs/toolkit to v2.11.2#535renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
|
View your CI Pipeline Execution ↗ for commit 51cfd97
☁️ Nx Cloud last updated this comment at |
d42e57e to
51cfd97
Compare
There was a problem hiding this comment.
Nx Cloud is proposing a fix for your failed CI:
These changes fix the TypeScript compilation error introduced by the @reduxjs/toolkit upgrade to v2.11.2, which brought immer from v10 to v11. By adding an explicit Slice type annotation to the nodeSlice export, we hide immer's internal types (like WritableNonArrayDraft) from the public API, satisfying TypeScript's module boundary requirements while maintaining full type safety.
Tip
✅ We verified this fix by re-running @forgerock/davinci-client:test.
Warning
The suggested diff is too large to display here, but you can view it on Nx Cloud ↗
Or Apply changes locally with:
npx nx-cloud apply-locally QrQs-ZCSJ
Apply fix locally with your editor ↗ View interactive diff ↗
🎓 Learn more about Self-Healing CI on nx.dev
This PR contains the following updates:
2.10.1→2.11.2Release Notes
reduxjs/redux-toolkit (@reduxjs/toolkit)
v2.11.2Compare Source
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: reduxjs/redux-toolkit@v2.11.0...v2.11.1
v2.11.0Compare Source
Configuration
📅 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.