build(deps-dev): bump eslint-plugin-react-hooks from 4.6.2 to 5.0.0 in /lineage-panel

[dependabot[bot]]

Bumps eslint-plugin-react-hooks from 4.6.2 to 5.0.0.

Release notes

Sourced from eslint-plugin-react-hooks's releases.

eslint-plugin-react-hooks@5.0.0 (Oct 11, 2024)

This release only contains eslint-plugin-react-hooks. Notably, new violations and support for ESLint v9 were added.

eslint-plugin-react-hooks

• New Violations: Component names now need to start with an uppercase letter instead of a non-lowercase letter. This means _Button or _component are no longer valid. (@​kassens) in #25162

• Add support for ESLint v9. (@​eps1lon in #28773)
• Consider dispatch from useActionState stable. (@​eps1lon in #29665)
• Accept as expression in callback. (@​StyleShit in #28202)
• Accept as expressions in deps array. (@​StyleShit in #28189)
• Treat React.use() the same as use(). (@​kassens in #27769)
• Move use() lint to non-experimental. (@​kassens in #27768)
• Support Flow as expressions. (@​cpojer in #27590)
• Allow useEffect(fn, undefined). (@​kassens in #27525)
• Disallow hooks in async functions. (@​acdlite in #27045)
• Rename experimental useEvent to useEffectEvent. (@​sebmarkbage in #25881)
• Lint for presence of useEvent functions in dependency lists. (@​poteto in #25512)
• Check useEvent references instead. (@​poteto in #25319)
• Update RulesOfHooks with useEvent rules. (@​poteto in #25285)

Changelog

Sourced from eslint-plugin-react-hooks's changelog.

5.0.0

• New Violations: Component names now need to start with an uppercase letter instead of a non-lowercase letter. This means _Button or _component are no longer valid. (@​kassens) in #25162

• Consider dispatch from useActionState stable. (@​eps1lon in #29665)
• Add support for ESLint v9. (@​eps1lon in #28773)
• Accept as expression in callback. (@​StyleShit in #28202)
• Accept as expressions in deps array. (@​StyleShit in #28189)
• Treat React.use() the same as use(). (@​kassens in #27769)
• Move use() lint to non-experimental. (@​kassens in #27768)
• Support Flow as expressions. (@​cpojer in #27590)
• Allow useEffect(fn, undefined). (@​kassens in #27525)
• Disallow hooks in async functions. (@​acdlite in #27045)
• Rename experimental useEvent to useEffectEvent. (@​sebmarkbage in #25881)
• Lint for presence of useEvent functions in dependency lists. (@​poteto in #25512)
• Check useEvent references instead. (@​poteto in #25319)
• Update RulesOfHooks with useEvent rules. (@​poteto in #25285)

4.6.0

4.5.0

• Fix false positive error with large number of branches. (@​scyron6 in #24287)

4.4.0

• No changes, this was an automated release together with React 18.

4.3.0

• Support ESLint 8. (@​MichaelDeBoey in #22248)
• Fix a crash with an empty effect. (@​ChrisRu in #20385)
• Improve the error message. (@​callmetwan in #20692)
• Handle optional chained methods as dependency. (@​AriPerkkio in #20247)
• Assume the new useTransition signature in the rule. (@​rickhanlonii in #20976)

4.2.0

• No changes, this was an automated release together with React 17.

4.1.2

• Fix a crash with the TypeScript 4.x parser. (@​eps1lon in #19815)

4.1.1

• Improve support for optional chaining. (@​pfongkye in #19680)
• Fix a false positive warning for TypeScript parameters. (@​NeoRaider in #19751)

4.1.0

• New Violations: Warn when dependencies change on every render. (@​captbaritone in #19590)

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by eps1lon, a new releaser for eslint-plugin-react-hooks since your current version.

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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show 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)

[github-actions[bot]]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either: - Register at [Qodana Cloud](https://qodana.cloud/) and [configure the action](https://github.com/jetbrains/qodana-action#qodana-cloud) - Use [GitHub Code Scanning with Qodana](https://github.com/jetbrains/qodana-action#github-code-scanning) - Host [Qodana report at GitHub Pages](https://github.com/JetBrains/qodana-action/blob/3a8e25f5caad8d8b01c1435f1ef7b19fe8b039a0/README.md#github-pages) - Inspect and use `qodana.sarif.json` (see [the Qodana SARIF format](https://www.jetbrains.com/help/qodana/qodana-sarif-output.html#Report+structure) for details) To get `*.log` files or any other Qodana artifacts, run the action with `upload-result` option set to `true`, so that the action will upload the files as the job artifacts: ```yaml - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2024.2.3 with: upload-result: true ```

Contact Qodana team

Contact us at [qodana-support@jetbrains.com](mailto:qodana-support@jetbrains.com) - Or via our issue tracker: https://jb.gg/qodana-issue - Or share your feedback: https://jb.gg/qodana-discussions