Update dependency eslint to v8.57.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint (source)	8.56.0 -> 8.57.1

---

Release Notes

eslint/eslint (eslint)

v8.57.1

Compare Source

Bug Fixes

• a19072f fix: add logic to handle fixTypes in the lintText() method (#​18900) (Francesco Trotta)
• 04c7188 fix: Don't lint same file multiple times (#​18899) (Francesco Trotta)
• 87ec3c4 fix: do not throw when defining a global named __defineSetter__ (#​18898) (Francesco Trotta)
• 60a1267 fix: Provide helpful error message for nullish configs (#​18889) (Milos Djermanovic)
• a0dea8e fix: allow name in global ignores, fix --no-ignore for non-global (#​18875) (Milos Djermanovic)
• 3836bb4 fix: do not crash on error in fs.walk filter (#​18886) (Milos Djermanovic)
• 2dec349 fix: skip processor code blocks that match only universal patterns (#​18880) (Milos Djermanovic)

Documentation

• 6a5add4 docs: v8.x Add EOL banner (#​18744) (Amaresh S M)
• b034575 docs: v8.x add version support page to the dropdown (#​18731) (Amaresh S M)
• 760ef7d docs: v8.x add version support page in the side navbar (#​18740) (Amaresh S M)
• 428b7ea docs: Add Powered by Algolia label to the search (#​18658) (Amaresh S M)
• c68c07f docs: version selectors synchronization (#​18265) (Milos Djermanovic)

Build Related

• 35d366a build: Support updates to previous major versions (#​18870) (Milos Djermanovic)

Chores

• 140ec45 chore: upgrade @​eslint/js@​8.57.1 (#​18913) (Milos Djermanovic)
• bcdfc04 chore: package.json update for @​eslint/js release (Jenkins)
• 3f6ce8d chore: pin [email protected] (#​18910) (Milos Djermanovic)
• 9f07549 chore: ignore /docs/v8.x in link checker (#​18660) (Milos Djermanovic)

v8.57.0

Compare Source

Features

• 1120b9b feat: Add loadESLint() API method for v8 (#​18098) (Nicholas C. Zakas)
• dca7d0f feat: Enable eslint.config.mjs and eslint.config.cjs (#​18066) (Nitin Kumar)

Bug Fixes

• 2196d97 fix: handle absolute file paths in FlatRuleTester (#​18064) (Nitin Kumar)
• 69dd1d1 fix: Ensure config keys are printed for config errors (#​18067) (Nitin Kumar)
• 9852a31 fix: deep merge behavior in flat config (#​18065) (Nitin Kumar)
• 4c7e9b0 fix: allow circular references in config (#​18056) (Milos Djermanovic)

Documentation

• 84922d0 docs: Show prerelease version in dropdown (#​18139) (Nicholas C. Zakas)
• 5b8c363 docs: Switch to Ethical Ads (#​18117) (Milos Djermanovic)
• 77dbfd9 docs: show NEXT in version selectors (#​18052) (Milos Djermanovic)

Chores

• 1813aec chore: upgrade @​eslint/js@​8.57.0 (#​18143) (Milos Djermanovic)
• 5c356bb chore: package.json update for @​eslint/js release (Jenkins)
• f4a1fe2 test: add more tests for ignoring files and directories (#​18068) (Nitin Kumar)
• 42c0aef ci: Enable CI for v8.x branch (#​18047) (Milos Djermanovic)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[sourcery-ai]

Reviewer's Guide

This PR upgrades ESLint from v8.56.0 to v8.57.1, aligning related ESLint ecosystem packages and regenerating the lockfile to reflect updated resolutions and integrity hashes.

File-Level Changes

Change	Details	Files
Upgrade ESLint dependency to v8.57.1	Updated ESLint specifier and version in pnpm-lock.yaml importer section Bumped ESLint entry in lockfile packages to v8.57.1 Updated devDependency version in web_dashboard/package.json	web_dashboard/pnpm-lock.yaml web_dashboard/package.json
Align related ESLint ecosystem packages	Bumped @eslint/js to v8.57.1 in lockfile Updated eslint-config-next to reference [email protected] and synced peer deps Upgraded @humanwhocodes/config-array from 0.11.14 to 0.13.0	web_dashboard/pnpm-lock.yaml
Regenerate lockfile with new integrity hashes	Refreshed resolution integrity hashes for ESLint, its plugins and parser Updated transitive and peer dependency entries referencing the new ESLint version	web_dashboard/pnpm-lock.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[gitstream-cm]

🚨 gitStream Monthly Automation Limit Reached 🚨

Your organization has exceeded the number of pull requests allowed for automation with gitStream.
Monthly PRs automated: 415/250

To continue automating your PR workflows and unlock additional features, please contact LinearB.

[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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

[qodo-merge-for-open-source]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: 🧪 Build Next.js (pnpm)

Failed stage: 🟣 Setup Node.js [❌]

Failure summary: The action failed because the pnpm executable could not be found in the system. The error message indicates that the workflow is trying to use pnpm as the package manager (as specified in the cache configuration), but the executable is not installed or not available in the PATH environment variable.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 123: c6b346d43c3d00bdd66c43c4ec5fb2afb6e1ab20 124: ##[group]Run actions/setup-node@v4 125: with: 126: node-version: 20 127: cache: pnpm 128: always-auth: false 129: check-latest: false 130: token: *** 131: ##[endgroup] 132: Found in cache @ /opt/hostedtoolcache/node/20.19.1/x64 133: ##[group]Environment details 134: node: v20.19.1 135: npm: 10.8.2 136: yarn: 1.22.22 137: ##[endgroup] 138: ##[error]Unable to locate executable file: pnpm. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable. 139: Post job cleanup.