deps: bump @typescript-eslint/eslint-plugin from 7.16.1 to 7.17.0

[dependabot]

Bumps @typescript-eslint/eslint-plugin from 7.16.1 to 7.17.0.

Release notes

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

v7.17.0

7.17.0 (2024-07-22)

🚀 Features

• eslint-plugin: backport no-unsafe-function type, no-wrapper-object-types from v8 to v7 (#9507)
• eslint-plugin: [return-await] add option to report in error-handling scenarios only, and deprecate "never" (#9364)

🩹 Fixes

• eslint-plugin: [no-floating-promises] check top-level type assertions (and more) (#9043)
• eslint-plugin: [strict-boolean-expressions] consider assertion function argument a boolean context (#9074)
• eslint-plugin: [no-unnecessary-condition] false positive on optional private field (#9602)
• typescript-estree: don't infer single-run when --fix is in proces.argv (#9577)
• typescript-estree: disable single-run inference with extraFileExtensions (#9580)
• website: expose ATA types to eslint instance (#9598)

❤️ Thank You

• Armano @​armano2
• Josh Goldberg ✨
• Kirk Waiblinger @​kirkwaiblinger
• StyleShit @​StyleShit

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

Changelog

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

7.17.0 (2024-07-22)

🚀 Features

• eslint-plugin: backport no-unsafe-function type, no-wrapper-object-types from v8 to v7

• eslint-plugin: [return-await] add option to report in error-handling scenarios only, and deprecate "never"

🩹 Fixes

• eslint-plugin: [no-floating-promises] check top-level type assertions (and more)

• eslint-plugin: [strict-boolean-expressions] consider assertion function argument a boolean context

• eslint-plugin: [no-unnecessary-condition] false positive on optional private field

❤️ Thank You

• Armano
• Josh Goldberg ✨
• Kirk Waiblinger
• StyleShit

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

Commits

• 05c9cb8 chore(release): publish 7.17.0
• f6c719f fix(eslint-plugin): [no-unnecessary-condition] false positive on optional pri...
• 6647f7e chore: enable no-unreachable-loop (#9540)
• 58be99f chore: enable prefer-object-spread (#9541)
• 5d895b7 chore: enable @​typescript-eslint/no-unused-expressions (#9542)
• d8c539d chore: enable no-useless-concat (#9550)
• f043f30 fix(eslint-plugin): [strict-boolean-expressions] consider assertion function ...
• 0108e9c chore: enable no-lonely-if (#9547)
• 970f3f1 feat(eslint-plugin): [return-await] add option to report in error-handling sc...
• dd965a4 feat(eslint-plugin): backport no-unsafe-function type, no-wrapper-object-type...
• 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 <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)

[trunk-io]

😎 Merged successfully - details.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@typescript-eslint/[email protected]	None	+8	4.73 MB	bradzacher, jameshenry

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@typescript-eslint/[email protected]

View full report↗︎

Next steps

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

[dependabot]

Superseded by #1167.

[blaine-arcjet]

@SocketSecurity ignore npm/@typescript-eslint/[email protected]

I've reviewed the "manifest confusion" warnings and it seems to be related to some socket bug where they don't know about versions in the registry. This might be due to the packages being published out-of-order, but they also flagged an eslint dependency that has been released for 9 months. Very strange bug indeed.