Bump @typescript-eslint/eslint-plugin from 8.6.0 to 8.7.0 in /server

[dependabot[bot]]

Bumps @typescript-eslint/eslint-plugin from 8.6.0 to 8.7.0.

Release notes

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

v8.7.0

8.7.0 (2024-09-23)

🚀 Features

• eslint-plugin: [no-unsafe-call] check calls of Function (#10010)
• eslint-plugin: [consistent-type-exports] check export * exports to see if all exported members are types (#10006)

🩹 Fixes

• eslint-plugin: properly coerce all types to string in getStaticMemberAccessValue (#10004)
• eslint-plugin: [no-deprecated] report on imported deprecated variables (#9987)
• eslint-plugin: [no-confusing-non-null-assertion] check !in and !instanceof (#9994)
• types: add NewExpression as a parent of SpreadElement (#10024)
• utils: add missing entries to the RuleListener selectors list (#9992)

❤️ Thank You

• Abraham Guo
• auvred @​auvred
• Brian Donovan @​eventualbuddha
• Kirk Waiblinger @​kirkwaiblinger

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

Changelog

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

8.7.0 (2024-09-23)

🚀 Features

• eslint-plugin: [no-unsafe-call] check calls of Function

• eslint-plugin: [consistent-type-exports] check export * exports to see if all exported members are types

🩹 Fixes

• eslint-plugin: properly coerce all types to string in getStaticMemberAccessValue

• eslint-plugin: [no-deprecated] report on imported deprecated variables

• eslint-plugin: [no-confusing-non-null-assertion] check !in and !instanceof

❤️ Thank You

• Abraham Guo
• auvred
• Brian Donovan
• Kirk Waiblinger

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

Commits

• b88ea33 chore(release): publish 8.7.0
• cdd93f6 docs(eslint-plugin): [no-inferrable-types] do not use no-inferrable-types wit...
• d0e35d9 feat(eslint-plugin): [consistent-type-exports] check export * exports to se...
• dc1c6d3 docs: [no-unnecessary-type-parameters] add FAQ section (#9975)
• e8555a0 feat(eslint-plugin): [no-unsafe-call] check calls of Function (#10010)
• 8293546 fix(eslint-plugin): [no-confusing-non-null-assertion] check !in and !instance...
• b75d42b fix(eslint-plugin): [no-deprecated] report on imported deprecated variables (...
• c5dc755 docs: [no-floating-promises] clarify that void does not resolve promises (#9949)
• 1c183ab fix(eslint-plugin): properly coerce all types to string in `getStaticMemberAc...
• 7b149b9 docs: [strict-boolean-expressions] fix adominition (#10033)
• Additional commits viewable 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 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)

[dependabot[bot]]

Looks like @typescript-eslint/eslint-plugin is up-to-date now, so this is no longer needed.