Update phpunit/phpunit from 8.3.4 to 8.5.44

[violinist-bot]

If you have a high test coverage index, and your tests for this pull request are passing, it should be both safe and recommended to merge this update.

Updated packages

Some times an update also needs new or updated dependencies to be installed. Even if this branch is for updating one dependency, it might contain other installs or updates. All of the updates in this branch can be found here:

• phpdocumentor/reflection-common 1.0.1 (package was removed)
• phpdocumentor/reflection-docblock 4.3.1 (package was removed)
• phpdocumentor/type-resolver 0.4.0 (package was removed)
• phpspec/prophecy 1.8.1 (package was removed)
• webmozart/assert 1.4.0 (package was removed)
• doctrine/instantiator: 1.5.0 (updated from 1.2.0)
• myclabs/deep-copy: 1.13.4 (updated from 1.9.3)
• phar-io/manifest: 2.0.4 (updated from 1.0.3)
• phar-io/version: 3.2.1 (updated from 2.0.1)
• phpunit/php-code-coverage: 7.0.17 (updated from 7.0.7)
• phpunit/php-file-iterator: 2.0.6 (updated from 2.0.2)
• phpunit/php-timer: 2.1.4 (updated from 2.1.2)
• phpunit/php-token-stream: 3.1.3 (updated from 3.1.0)
• phpunit/phpunit: 8.5.44 (updated from 8.3.4)
• sebastian/code-unit-reverse-lookup: 1.0.3 (updated from 1.0.1)
• sebastian/comparator: 3.0.6 (updated from 3.0.2)
• sebastian/diff: 3.0.6 (updated from 3.0.2)
• sebastian/environment: 4.2.5 (updated from 4.2.2)
• sebastian/exporter: 3.1.6 (updated from 3.1.1)
• sebastian/global-state: 3.0.6 (updated from 3.0.0)
• sebastian/object-enumerator: 3.0.5 (updated from 3.0.3)
• sebastian/object-reflector: 1.1.3 (updated from 1.1.1)
• sebastian/recursion-context: 3.0.3 (updated from 3.0.0)
• sebastian/resource-operations: 2.0.3 (updated from 2.0.1)
• sebastian/type: 1.1.5 (updated from 1.1.3)
• theseer/tokenizer: 1.2.3 (updated from 1.1.3)

Working with this branch

If you find you need to update the codebase to be able to merge this branch (for example update some tests or rebuild some assets), please note that violinist will force push to this branch to keep it up to date. This means you should not work on this branch directly, since you might lose your work. Read more about branches created by violinist.io here.

---

This is an automated pull request from Violinist: Continuously and automatically monitor and update your composer dependencies. Have ideas on how to improve this message? All violinist messages are open-source, and can be improved here.

Summary by CodeRabbit

• Chores

  • Updated the test framework development dependency to the latest patch version.

• Tests

  • Synchronized the test suite with the updated dependency; test execution remains consistent.

• No User-Facing Changes

  • No changes to features, behavior, or public APIs.

[coderabbitai]

Walkthrough

Bumped the PHPUnit development dependency in composer.json from version 8.3.4 to 8.5.44. No other files or public interfaces were modified.

Changes

Cohort / File(s)	Summary
Dependency version bump composer.json	Update dev dependency phpunit/phpunit from 8.3.4 to 8.5.44

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I thump my paw—dependencies align,
A tiny hop from eight-point-three to nine… (well, five!)
Composer hums, tests ready to thrive,
Carrots compiled, our suites come alive,
With whiskered grin, I press “phpunit” and jive.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

composer.json (2)

12-16: Add an explicit PHP platform constraint.

PHPUnit 8 requires PHP ≥7.2. Make the PHP version explicit in composer.json to fail fast on unsupported environments and keep CI/composer resolution clear.

Apply this diff:

   "require": {
+        "php": "^7.2",
         "guzzlehttp/guzzle": "6.3.*",
         "symfony/dotenv": "4.3.*",
         "ext-json": "*"
   },

If your CI supports newer PHP versions, adjust the constraint accordingly (e.g., "^7.4 || ^8.0").

---

23-23: Consider a looser constraint to receive future 8.5.x patches automatically.

If you prefer automatic patch updates without editing composer.json each time, switch to a series constraint.

Proposed change:

-        "phpunit/phpunit": "8.5.44",
+        "phpunit/phpunit": "8.5.*",

Keep the exact pin if you value strict reproducibility over convenience (composer.lock already provides determinism in CI).

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 0041136 and f573833.

⛔ Files ignored due to path filters (1)

• composer.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• composer.json (1 hunks)

🔇 Additional comments (2)

composer.json (2)

17-25: Dev Dependencies Verified: No Prophecy Usage or Stray Transitive Packages

All checks passed—no further action required:

• Tests scanned for any direct or trait-based Prophecy usage (Prophecy, prophesize(), ProphecyTrait) and none was found.
• composer.lock was inspected: no references to the removed transitive packages (phpdocumentor/*, phpspec/prophecy, webmozart/assert) remain.
• Dev tool versions in composer.lock match those in composer.json (brianium/paratest 3.0.0; phpunit/phpunit 8.5.44).

---

23-23: Update PHPUnit Verification Instructions

The pinned PHPUnit version is confirmed in composer.lock (8.5.44). To verify and run your tests locally, please install dependencies and check the version:

# Install dependencies (vendor/bin/phpunit will be created)
composer install --no-interaction --prefer-dist

# Verify the PHPUnit version
./vendor/bin/phpunit --version

# Run the full test suite
./vendor/bin/phpunit

Ensure that ./vendor/bin/phpunit --version outputs 8.5.44 and that your test suite passes both locally and in CI.