chore(deps-dev): bump @typescript-eslint/eslint-plugin from 8.15.0 to 8.16.0

[dependabot]

Bumps @typescript-eslint/eslint-plugin from 8.15.0 to 8.16.0.

Release notes

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

v8.16.0

8.16.0 (2024-11-25)

🚀 Features

• support TypeScript 5.7 (#10372)
• eslint-plugin: [max-params] add function overload and function type support (#10312)
• eslint-plugin: [no-base-to-string] check Array.prototype.join (#10287)

🩹 Fixes

• typescript-estree: update conditions for unsupported version warning (#10385)

❤️ Thank You

• Inga @​inga-lovinde
• Josh Goldberg ✨
• Kim Sang Du @​developer-bandi
• YeonJuan @​yeonjuan

You can read about our versioning strategy and releases on our website.

Changelog

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

8.16.0 (2024-11-25)

🚀 Features

• eslint-plugin: [no-base-to-string] check Array.prototype.join (#10287)
• eslint-plugin: [max-params] add function overload and function type support (#10312)

❤️ Thank You

• Kim Sang Du @​developer-bandi
• YeonJuan @​yeonjuan

You can read about our versioning strategy and releases on our website.

Commits

• f74a8fa chore(release): publish 8.16.0
• 2e2433b feat(eslint-plugin): [no-base-to-string] check Array.prototype.join (#10287)
• 88e4c66 docs(eslint-plugin): add missing > in array-type.mdx (#10371)
• 71243db chore: correct lint errors in CI (#10370)
• cdbc669 feat(eslint-plugin): [max-params] add function overload and function type sup...
• cac88ca chore: set no-else-return allowIfElse to false (#10325)
• 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 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 <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)

[socket-security]

Report too large to display inline

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	npm/babel-traverse@6.26.0	CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: No patched versions	package-lock.json package.json ui/package-lock.json	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/babel-traverse@6.26.0