build(deps-dev): bump @eslint-react/eslint-plugin from 5.21.3 to 5.23.3

[dependabot]

Bumps @eslint-react/eslint-plugin from 5.21.3 to 5.23.3.

Release notes

Sourced from @​eslint-react/eslint-plugin's releases.

v5.23.3 (2026-09-30)

What's Changed

🐞 Fixes

• react-x/immutability: reassigning a binding that resolves to component props or state (value = value + "!", count++, including destructuring and for...of rebinding forms) is now reported as a direct mutation, matching upstream react-hooks/immutability; rebinding iterator or shallow-copy bindings remains allowed. (#1979)
• react-x/set-state-in-effect: ref reads traced through intermediate local computations (ex: const dv = visible - prevVisible.current) are now recognized as ref-derived values, and a preceding early-return guard whose test is ref-derived (ex: if (dv === 0) return;) now exempts the setState calls that follow it — previously only setState nested directly inside a ref-gated if/conditional was exempted. Aligns with react-hooks 7.1.1. (#1979)

📝 Documentation

• react-x/no-unstable-context-value: documented the React 19 <Context> provider detection heuristic and its name-based limitations. (#1979)
• Updated the README badges to reference eslint-plugin-react-x.

Full Changelog: Rel1cx/eslint-react@v5.23.2...v5.23.3

Attestation

https://github.com/Rel1cx/eslint-react/attestations/51510644

v5.23.2 (2026-09-30)

What's Changed

🏗️ Internal

• Removed unused dependencies and fixed phantom dependencies across the workspace.
• Bumped next to 16.3.7, fumadocs-core and fumadocs-ui to 16.15.16, and eslint-plugin-package-json to 1.10.1.

Full Changelog: Rel1cx/eslint-react@v5.23.1...v5.23.2

Attestation

https://github.com/Rel1cx/eslint-react/attestations/51477484

v5.23.1 (2026-09-30)

What's Changed

🏗️ Internal

• Re-verified and synchronized the IMPL-SPEC diff reports for the following react-x rules. (#1977, #1978)
  • react-x/error-boundaries
  • react-x/globals
  • react-x/immutability
  • react-x/purity
  • react-x/refs
  • react-x/set-state-in-effect

... (truncated)

Changelog

Sourced from @​eslint-react/eslint-plugin's changelog.

v5.23.3 (2026-09-30)

🐞 Fixes

• react-x/immutability: reassigning a binding that resolves to component props or state (value = value + "!", count++, including destructuring and for...of rebinding forms) is now reported as a direct mutation, matching upstream react-hooks/immutability; rebinding iterator or shallow-copy bindings remains allowed. (#1979)
• react-x/set-state-in-effect: ref reads traced through intermediate local computations (ex: const dv = visible - prevVisible.current) are now recognized as ref-derived values, and a preceding early-return guard whose test is ref-derived (ex: if (dv === 0) return;) now exempts the setState calls that follow it — previously only setState nested directly inside a ref-gated if/conditional was exempted. Aligns with react-hooks 7.1.1. (#1979)

📝 Documentation

• react-x/no-unstable-context-value: documented the React 19 <Context> provider detection heuristic and its name-based limitations. (#1979)
• Updated the README badges to reference eslint-plugin-react-x.

Full Changelog: Rel1cx/eslint-react@v5.23.2...v5.23.3

v5.23.2 (2026-09-30)

🏗️ Internal

• Removed unused dependencies and fixed phantom dependencies across the workspace.
• Bumped next to 16.3.7, fumadocs-core and fumadocs-ui to 16.15.16, and eslint-plugin-package-json to 1.10.1.

Full Changelog: Rel1cx/eslint-react@v5.23.1...v5.23.2

v5.23.1 (2026-09-30)

🏗️ Internal

• Re-verified and synchronized the IMPL-SPEC diff reports for the following react-x rules. (#1977, #1978)
  • react-x/error-boundaries
  • react-x/globals
  • react-x/immutability
  • react-x/purity
  • react-x/refs
  • react-x/set-state-in-effect
  • react-x/set-state-in-render
  • react-x/use-memo
• Bumped typescript-eslint to 8.71.0, tsl-dx to 0.13.7, and pnpm to 12.8.1.

📝 Documentation

• Added argo-cd, griffel, tanstack/table, and eslint-config-studio to the website's community lists.

Full Changelog: Rel1cx/eslint-react@v5.23.0...v5.23.1

v5.23.0 (2026-09-30)

✨ New

• react-x/static-components: dynamic creation-site tracing now follows both sides of logical expressions (ex: const C = DefaultComponent || (() => <div />)) and the last element of sequence expressions (ex: const C = (setup(), () => <div />)), in initializers and reassignments alike. (#1975)

... (truncated)

Commits

• 4d35170 release: 5.23.3
• 8b74307 docs: update README badges to reference eslint-plugin-react-x
• b993085 release: 5.23.2
• 0148902 chore: remove unused dependencies and fix phantom dependencies
• 427feff release: 5.23.1
• cdad818 release: 5.23.0
• d0c3687 release: 5.22.1
• bfb935d docs: shorten the optional peer dependency note in the READMEs
• 4dcdace release: 5.22.0
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mergify]

Automatically approving dependabot

[mergify]

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.