chore(deps): update all non-major dependencies to v6.8.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@typescript-eslint/eslint-plugin	6.7.5 -> 6.8.0
@typescript-eslint/parser	6.7.5 -> 6.8.0

---

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v6.8.0

Compare Source

Bug Fixes

• eslint-plugin: [consistent-type-imports] import assertion checks added (#​7722) (afdae37)
• eslint-plugin: [no-shadow] fix static class generics for class expressions (#​7724) (e5ea1d0)
• eslint-plugin: [no-unsafe-member-access] report on only the accessed property (#​7717) (f81a2da)
• eslint-plugin: [no-useless-empty-export] exempt .d.ts (#​7718) (ac397f1)

Features

• eslint-plugin: add new extended rule prefer-destructuring (#​7117) (3c6379b)

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

6.7.5 (2023-10-09)

Bug Fixes

• eslint-plugin: [prefer-string-starts-ends-with] only report slice/substring with correct range (#​7712) (db40a0a)

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

6.7.4 (2023-10-02)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

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

6.7.3 (2023-09-25)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

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

6.7.2 (2023-09-18)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

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

6.7.1 (2023-09-18)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

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

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v6.8.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

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

6.7.5 (2023-10-09)

Note: Version bump only for package @​typescript-eslint/parser

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

6.7.4 (2023-10-02)

Note: Version bump only for package @​typescript-eslint/parser

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

6.7.3 (2023-09-25)

Note: Version bump only for package @​typescript-eslint/parser

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

6.7.2 (2023-09-18)

Note: Version bump only for package @​typescript-eslint/parser

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

6.7.1 (2023-09-18)

Note: Version bump only for package @​typescript-eslint/parser

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: de8064e

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.

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

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
@typescript-eslint/eslint-plugin	6.7.5...6.8.0	None	+7/-7	4.14 MB
@typescript-eslint/parser	6.7.5...6.8.0	None	+4/-4	1.35 MB

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: All docstrings and comments should be up to date.
• Apply: Code should be properly formatted and indented.
• Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• Apply: There should be no unused imports or variables.
• Apply: Code should be free of unnecessary comments and commented-out code.
• Apply: There should be no hard-coded values or magic numbers in the code.