chore(deps): update dependency @smartive/eslint-config to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@smartive/eslint-config	3.3.0 -> 6.4.0

---

Release Notes

smartive/eslint-config (@​smartive/eslint-config)

v6.4.0

Compare Source

Features

• add configuration for Next.js and export configs using a function (#​39) (2f56861)

v6.3.2

Compare Source

Bug Fixes

• remove rules for Next.js since they break existing projects that aren't using Next.js (#​38) (ace8d02)

v6.3.1

Compare Source

Bug Fixes

• rename next to nextjs (4e54a29)

v6.3.0

Compare Source

Features

• add configuration for Next.js (#​37) (9adebc0)

v6.2.0

Compare Source

Features

• disable rule @​typescript-eslint/prefer-regexp-exec (#​36) (2eb1d23)

v6.1.0

Compare Source

Features

• disable type checking for JavaScript files (#​35) (19cccd0)

v6.0.0

Compare Source

Features

• update ESLint to v9 (#​30) (82e0d48)

BREAKING CHANGES

• due to the upgrade of various ESLint plugins, the minimum supported version
  TypeScript and Node.js has been increased. This should not affect most users, but if you are using
  an older version of TypeScript or Node.js, you may need to upgrade.
  Furthermore there are some adjustments on how to use the legacy config. For more information
  have a look at the README file.

v5.2.0

Compare Source

Features

• Allow console.debug() (#​33) (1c56a19)

v5.1.0

Compare Source

Features

• allow floating promises for JSX attributes (#​21) (9d9f0f8)

v5.0.0

Compare Source

Bug Fixes

• disable @​typescript-eslint/no-unsafe-enum-comparison rule (9c7bc6b)
• disable rule @​typescript-eslint/consistent-type-definitions (d63e040)

Features

• add new ESLint rules (e2c9855)
• use type checked recommended rules (2a993ba)

BREAKING CHANGES

• Use @​typescript-eslint/recommended-type-checked and
  @​typescript-eslint/stylistic-type-checked rules instead of @​typescript-eslint/recommended
• Add new rules for @​typescript-eslint/no-explicit-any, prefer-const, no-else-return,
  no-extra-semi, curly, eqeqeq, default-case-last

v4.0.1

Compare Source

Bug Fixes

• @​typescript-eslint/no-floating-promises rule not working due to missing TS project config (#​19) (ce4e600)

v4.0.0

Compare Source

Bug Fixes

• check if husky is installed (#​18) (8889b95)
• fix the check that checks if Husky is installed (5f5c469)
• only run husky in development environment (#​17) (702fb42)

chore

• drop support for old versions of ESLint (#​15) (dadd751)

Features

• add new more restrictive rules (#​16) (52fa585)

BREAKING CHANGES

• Drop support for ESLint v7 and @​typescript-eslint/* v5
• Add new rules for array-callback-return, no-debugger, no-alert,
  newline-before-return, @​typescript-eslint/no-unused-vars,
  @​typescript-eslint/no-floating-promises, no-constant-binary-expression and no-console

---

Configuration

📅 Schedule: Branch creation - "after 9pm,before 6am" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.