chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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

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

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.71%. Comparing base (8ee1236) to head (1eff77e).
⚠️ Report is 13 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #313   +/-   ##
=========================================
  Coverage     95.71%   95.71%           
  Complexity       21       21           
=========================================
  Files             6        6           
  Lines            70       70           
=========================================
  Hits             67       67           
  Misses            3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock

Command failed: composer update --ignore-platform-req=ext-* --ignore-platform-req=lib-* --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires pestphp/pest ^2.34 -> satisfiable by pestphp/pest[v2.34.0, ..., v2.36.0].
    - brianium/paratest[v7.9.0, ..., v7.11.2] require php ~8.3.0 || ~8.4.0 -> your php version (8.5.1) does not satisfy that requirement.
    - brianium/paratest v7.12.0 requires phpunit/phpunit ^12.3.6 -> found phpunit/phpunit[12.3.6, ..., 12.5.4] but it conflicts with your root composer.json require (^10.5).
    - brianium/paratest v7.13.0 requires phpunit/phpunit ^12.3.9 -> found phpunit/phpunit[12.3.9, ..., 12.5.4] but it conflicts with your root composer.json require (^10.5).
    - brianium/paratest v7.14.0 requires phpunit/phpunit ^12.3.15 -> found phpunit/phpunit[12.3.15, ..., 12.5.4] but it conflicts with your root composer.json require (^10.5).
    - brianium/paratest v7.14.1 requires phpunit/phpunit ^12.4.0 -> found phpunit/phpunit[12.4.0, ..., 12.5.4] but it conflicts with your root composer.json require (^10.5).
    - brianium/paratest v7.14.2 requires phpunit/phpunit ^12.4.1 -> found phpunit/phpunit[12.4.1, ..., 12.5.4] but it conflicts with your root composer.json require (^10.5).
    - brianium/paratest v7.15.0 requires phpunit/phpunit ^12.4.4 -> found phpunit/phpunit[12.4.4, ..., 12.5.4] but it conflicts with your root composer.json require (^10.5).
    - brianium/paratest v7.16.0 requires phpunit/phpunit ^12.5.2 -> found phpunit/phpunit[12.5.2, 12.5.3, 12.5.4] but it conflicts with your root composer.json require (^10.5).
    - brianium/paratest v7.16.1 requires phpunit/phpunit ^12.5.4 -> found phpunit/phpunit[12.5.4] but it conflicts with your root composer.json require (^10.5).
    - brianium/paratest v7.3.1 requires php ~8.1.0 || ~8.2.0 || ~8.3.0 -> your php version (8.5.1) does not satisfy that requirement.
    - brianium/paratest[v7.4.0, ..., v7.5.7] require php ~8.2.0 || ~8.3.0 -> your php version (8.5.1) does not satisfy that requirement.
    - brianium/paratest[v7.4.8, ..., v7.8.4] require php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.5.1) does not satisfy that requirement.
    - brianium/paratest v7.8.5 requires phpunit/phpunit ^11.5.46 -> found phpunit/phpunit[11.5.46] but it conflicts with your root composer.json require (^10.5).
    - pestphp/pest[v2.34.0, ..., v2.36.0] require brianium/paratest ^7.3.1 -> satisfiable by brianium/paratest[v7.3.1, ..., v7.16.1].
    - pestphp/pest v2.34.3 requires brianium/paratest ^7.4.3 -> satisfiable by brianium/paratest[v7.4.3, ..., v7.16.1].