build(deps-dev): Bump @eslint-react/eslint-plugin from 5.10.0 to 5.11.3

[dependabot]

Bumps @eslint-react/eslint-plugin from 5.10.0 to 5.11.3.

Release notes

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

v5.11.3 (2026-07-07)

What's Changed

🐞 Fixes

• Fixed FunctionComponentDetectionHint.DoNotIncludeFunctionDefinedAsClassProperty checking for object Property nodes instead of class PropertyDefinition nodes, so functions defined as class fields are now correctly excluded when the hint is set. (#1890)

🏗️ Internal

• Renamed fix helpers and formatted MessageID types.
• Inlined local string constants in rule implementations.
• Bumped eslint-plugin-jsdoc, typedoc, undici and pnpm.

Full Changelog: Rel1cx/eslint-react@v5.11.2...v5.11.3

Attestation

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

v5.11.2 (2026-07-05)

What's Changed

📝 Documentation

• Updated rule documentation for React introspection APIs (react-x/no-children-count, react-x/no-children-for-each, react-x/no-children-map, react-x/no-children-only, react-x/no-children-to-array, and react-x/no-clone-element) with clearer guidance on why child introspection creates fragile component coupling and links to Astryx's no-react-introspection rule. (#1889)
• Updated the function-component collector sequence diagram on the website.
• Updated THIRD-PARTY-LICENSE file.

Full Changelog: Rel1cx/eslint-react@v5.11.0...v5.11.2

Attestation

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

v5.11.0 (2026-07-05)

What's Changed

✨ New

• react-x/refs now detects ref mutations/reads inside helper functions that are called (directly, or through a simple variable alias) during render, closing a gap where any nested function was previously treated as a safe boundary regardless of whether it was actually invoked during render.
• react-x/refs now reports a second guarded ref initialization: only a single if (ref.current == null) { ref.current = ... } guarded initialization is allowed per ref per component/hook, and a second guarded write (in the same or a different if block) is reported as duplicateRefInit.
• react-x/refs now supports .current accesses whose base is a member expression that looks like a ref (e.g. props.ref.current), not just a plain identifier.

🏗️ Internal

... (truncated)

Changelog

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

v5.11.3 (2026-07-07)

🐞 Fixes

• Fixed FunctionComponentDetectionHint.DoNotIncludeFunctionDefinedAsClassProperty checking for object Property nodes instead of class PropertyDefinition nodes, so functions defined as class fields are now correctly excluded when the hint is set. (#1890)

🏗️ Internal

• Renamed fix helpers and formatted MessageID types.
• Inlined local string constants in rule implementations.
• Bumped eslint-plugin-jsdoc, typedoc, undici and pnpm.

Full Changelog: Rel1cx/eslint-react@v5.11.2...v5.11.3

v5.11.2 (2026-07-05)

📝 Documentation

• Updated rule documentation for React introspection APIs (react-x/no-children-count, react-x/no-children-for-each, react-x/no-children-map, react-x/no-children-only, react-x/no-children-to-array, and react-x/no-clone-element) with clearer guidance on why child introspection creates fragile component coupling and links to Astryx's no-react-introspection rule. (#1889)
• Updated the function-component collector sequence diagram on the website.
• Updated THIRD-PARTY-LICENSE file.

Full Changelog: Rel1cx/eslint-react@v5.11.0...v5.11.2

v5.11.0 (2026-07-05)

✨ New

• react-x/refs now detects ref mutations/reads inside helper functions that are called (directly, or through a simple variable alias) during render, closing a gap where any nested function was previously treated as a safe boundary regardless of whether it was actually invoked during render.
• react-x/refs now reports a second guarded ref initialization: only a single if (ref.current == null) { ref.current = ... } guarded initialization is allowed per ref per component/hook, and a second guarded write (in the same or a different if block) is reported as duplicateRefInit.
• react-x/refs now supports .current accesses whose base is a member expression that looks like a ref (e.g. props.ref.current), not just a plain identifier.

🏗️ Internal

• Added unit tests for packages/ast/src/check.ts.
• Bumped @effect/language-service to ^0.86.4 and preact to ^10.29.4.
• Refactored react-x/static-components internals without changing behavior: findVariableForIdentifier now delegates to @typescript-eslint/utils/ast-utils's findVariable instead of a hand-rolled scope-chain walk, resolveDynamicValue was split into findDynamicCreationSite and findReassignmentCreationSite, and render-boundary/JSX-candidate handling was extracted into dedicated helpers.
• Unified the signatures of Check.isDirective and Check.isIdentifier in @eslint-react/ast: both now take the node as the first argument and an optional name as the second, replacing the previous curried (name) => (node) => boolean shape. Removed Check.isStringLiteral; use ts-pattern's isMatching or an inline type guard instead.

Full Changelog: Rel1cx/eslint-react@v5.10.4...v5.11.0

v5.10.4 (2026-07-04)

🐞 Fixes

• Fixed react-x/no-misused-capture-owner-stack not recognizing process.env.NODE_ENV checks wrapped in TypeScript type expressions such as (process.env as any).NODE_ENV. (#1813)
• Fixed Extract.getFullyQualifiedName to unwrap TSAsExpression, TSTypeAssertion, TSNonNullExpression, and ChainExpression before resolving names. This improves name resolution for rules that identify React APIs or collect component/hook names through type-wrapped expressions.

Full Changelog: Rel1cx/eslint-react@v5.10.3...v5.10.4

... (truncated)

Commits

• dfd7e76 release: 5.11.3
• 0f8d356 release: 5.11.2
• 787aba5 refactor(ast)!: remove direct is/isOneOf re-exports and use Check namespace
• 76c0b1e release: 5.11.0
• 499b5e6 release: 5.10.4
• a4130ee release: 5.10.3
• fa53e93 chore(eslint-plugin): update package description
• 3d6f501 release: 5.10.2
• ecb5626 release: 5.10.1
• 9973045 fix: static-components rule is missing from `disable-conflict-eslint-plugin...
• 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)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
github-stats-extended-backend	Ready	Preview, Comment	Jul 15, 2026 12:35am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
github-stats-extended-frontend	Ignored		Jul 15, 2026 12:35am