chore(deps): bump @eslint/eslintrc from 2.1.4 to 3.0.0

[dependabot]

Bumps @eslint/eslintrc from 2.1.4 to 3.0.0.

Release notes

Sourced from @​eslint/eslintrc's releases.

v3.0.0

3.0.0 (2023-12-27)

⚠ BREAKING CHANGES

• Require Node.js ^18.18.0 || ^20.9.0 || >=21.1.0 (#142)
• Set default schema: [], drop support for function-style rules (#139)

Features

• Require Node.js ^18.18.0 || ^20.9.0 || >=21.1.0 (#142) (737eb25)
• Set default schema: [], drop support for function-style rules (#139) (a6c240d)

Chores

• upgrade github actions (#143) (de34faf)

Changelog

Sourced from @​eslint/eslintrc's changelog.

3.0.0 (2023-12-27)

⚠ BREAKING CHANGES

• Require Node.js ^18.18.0 || ^20.9.0 || >=21.1.0 (#142)
• Set default schema: [], drop support for function-style rules (#139)

Features

• Require Node.js ^18.18.0 || ^20.9.0 || >=21.1.0 (#142) (737eb25)
• Set default schema: [], drop support for function-style rules (#139) (a6c240d)

Chores

• upgrade github actions (#143) (de34faf)

Commits

• 0b7b6a5 chore: release 3.0.0 (#141)
• de34faf chore: upgrade github actions (#143)
• 737eb25 feat!: Require Node.js ^18.18.0 || ^20.9.0 || >=21.1.0 (#142)
• a6c240d feat!: Set default schema: [], drop support for function-style rules (#139)
• See full diff 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)

[tomarra]

Not sure how this is passing CI given that the node version needs to get updated 🤔

[alestiago]

Me neither, I've updated the node version to 20.11.0 (LTS) and let it run, it seems to be passing. We might need a Node package update policy.

[tomarra]

Talked this through with the team during a planning session. Not looking to take on this update right now as it will also update the node engine as well which we currently don't have bandwidth for.

[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.