[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/pre-commit/pre-commit-hooks: v4.6.0 → v5.0.0

Summary by Sourcery

Update the pre-commit hook version to v5.0.0 to ensure the latest checks and improvements are applied.

Build:

• Update pre-commit hook version from v4.6.0 to v5.0.0 in the .pre-commit-config.yaml file.

[semanticdiff-com]

Review changes with SemanticDiff.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the pre-commit hooks version from v4.6.0 to v5.0.0 in the .pre-commit-config.yaml file. The update is automatically generated by the pre-commit.ci service.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update pre-commit hooks version	Change the 'rev' field from v4.6.0 to v5.0.0 for the pre-commit-hooks repository	.pre-commit-config.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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, pre-commit-ci[bot]!). We assume it knows what it's doing!

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

(Checks updated until commit 5f32ec8)

Action: Awesome_Lint

Failed stage: Run npx awesome-lint [❌]

Failed test name: remark-lint:awesome-list-item

Failure summary: The action failed due to multiple linting errors detected by remark-lint:awesome-list-item: Several list item descriptions did not start with valid casing. At least one list item description did not end with proper punctuation. A total of 47 errors were found, leading to the process exiting with code 1.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 545: ✖ 220:44 List item description must start with valid casing remark-lint:awesome-list-item 546: ✖ 221:64 List item description must start with valid casing remark-lint:awesome-list-item 547: ✖ 222:57 List item description must start with valid casing remark-lint:awesome-list-item 548: ✖ 223:55 List item description must start with valid casing remark-lint:awesome-list-item 549: ✖ 224:54 List item description must start with valid casing remark-lint:awesome-list-item 550: ✖ 228:63 List item description must start with valid casing remark-lint:awesome-list-item 551: ✖ 231:71 List item description must start with valid casing remark-lint:awesome-list-item 552: ✖ 240:103 List item description must end with proper punctuation remark-lint:awesome-list-item 553: 47 errors 554: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.