Bump @typescript-eslint/rule-tester from 7.16.0 to 8.20.0

[dependabot]

Bumps @typescript-eslint/rule-tester from 7.16.0 to 8.20.0.

Release notes

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

v8.20.0

8.20.0 (2025-01-13)

🚀 Features

• standardize debug namespaces to file paths (#10599)
• eslint-plugin: [no-misused-spread] add new rule (#10551)
• eslint-plugin: [no-deprecated] add allow options (#10585)
• eslint-plugin: [consistent-type-assertions] add arrayLiteralTypeAssertions options (#10565)

🩹 Fixes

• eslint-plugin: [no-shadow] ignore ordering of type declarations (#10593)
• eslint-plugin: [no-unnecessary-condition] don't flag optional chaining for union types with an unconstrained type parameters (#10602)

❤️ Thank You

• Josh Goldberg ✨
• Ronen Amiel
• YeonJuan @​yeonjuan

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

v8.19.1

8.19.1 (2025-01-06)

🩹 Fixes

• eslint-plugin: [no-base-to-string] check array generic type (#10437)
• eslint-plugin: [no-shadow] report correctly on parameters of functions declared with the declare keyword (#10543)
• eslint-plugin: [strict-boolean-expressions] remove remaining (unsafe) autofixes (#10548)
• eslint-plugin: [no-deprecated] doesn't report on shorthand property in an object expression (#10550)

❤️ Thank You

• Kirk Waiblinger
• mdm317
• Ronen Amiel
• Yukihiro Hasegawa @​y-hsgw

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

v8.19.0

8.19.0 (2024-12-30)

🚀 Features

• eslint-plugin: [strict-boolean-expressions] check array predicate functions' return statements (#10106)

🩹 Fixes

... (truncated)

Changelog

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

8.20.0 (2025-01-13)

🚀 Features

• eslint-plugin: [no-misused-spread] add new rule (#10551)

❤️ Thank You

• Josh Goldberg ✨

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

8.19.1 (2025-01-06)

This was a version bump only for rule-tester to align it with other projects, there were no code changes.

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

8.19.0 (2024-12-30)

This was a version bump only for rule-tester to align it with other projects, there were no code changes.

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

8.18.2 (2024-12-23)

This was a version bump only for rule-tester to align it with other projects, there were no code changes.

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

8.18.1 (2024-12-16)

This was a version bump only for rule-tester to align it with other projects, there were no code changes.

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

8.18.0 (2024-12-09)

This was a version bump only for rule-tester to align it with other projects, there were no code changes.

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

8.17.0 (2024-12-02)

This was a version bump only for rule-tester to align it with other projects, there were no code changes.

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

8.16.0 (2024-11-25)

... (truncated)

Commits

• ea6fbea chore(release): publish 8.20.0
• 04166e0 feat(eslint-plugin): [no-misused-spread] add new rule (#10551)
• 328b7df chore(release): publish 8.19.1
• e19f30f chore(release): publish 8.19.0
• 157b781 chore(release): publish 8.18.2
• b2ce158 chore(release): publish 8.18.1
• c60dbab chore(release): publish 8.18.0
• 0d65f17 chore: enforce repo nullish check style (#10419)
• 2c8a75e chore(release): publish 8.17.0
• f74a8fa chore(release): publish 8.16.0
• 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)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 29da9d0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.