build(deps-dev): bump phpunit/phpunit from 9.5.28 to 13.1.11#360
build(deps-dev): bump phpunit/phpunit from 9.5.28 to 13.1.11#360dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit) from 9.5.28 to 13.1.11. - [Release notes](https://github.com/sebastianbergmann/phpunit/releases) - [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.1.11/ChangeLog-13.1.md) - [Commits](sebastianbergmann/phpunit@9.5.28...13.1.11) --- updated-dependencies: - dependency-name: phpunit/phpunit dependency-version: 13.1.11 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Pull Request Overview
This PR attempts to upgrade PHPUnit from version 9 to 13. This change is not mergeable in its current state. Primarily, PHPUnit 13 has not been released (version 11 is the current stable major), meaning the dependency resolution will fail. Furthermore, the jump from version 9 to 10+ involves significant breaking changes, including a complete rewrite of the internal event system and a new requirement for PHP 8.2+. The absence of accompanying updates to the phpunit.xml configuration file and test annotations means the test suite will be entirely broken.
About this PR
- Upgrading across four major versions of PHPUnit (9 to 13) without updating the phpunit.xml schema or migrating test annotations from docblocks to PHP attributes will result in a non-functional test suite. PHPUnit 10+ requires a mandatory configuration migration.
Test suggestions
- Run the existing test suite using PHPUnit 13 to verify compatibility with major breaking changes
- Validate that the phpunit.xml configuration file is migrated to the schema required for PHPUnit 10 and above
- Verify that test metadata and mocks are updated for compatibility with PHPUnit 13
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Run the existing test suite using PHPUnit 13 to verify compatibility with major breaking changes
2. Validate that the phpunit.xml configuration file is migrated to the schema required for PHPUnit 10 and above
3. Verify that test metadata and mocks are updated for compatibility with PHPUnit 13
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
| }, | ||
| "require-dev": { | ||
| "phpunit/phpunit": "^9.0", | ||
| "phpunit/phpunit": "^13.1", |
There was a problem hiding this comment.
🔴 HIGH RISK
This major version jump (9 to 13) breaks compatibility with existing phpunit.xml configurations and requires a newer PHP version (PHPUnit 11+ requires PHP 8.2+). Additionally, PHPUnit 13 is not currently available as a stable release, which will cause the build to fail during dependency resolution. Try running the following prompt in your coding agent: > Migrate the PHPUnit configuration and test cases from version 9 to 11, including updating the phpunit.xml schema and converting annotations (like @ExpectedException) to PHP attributes.
|
Superseded by #361. |
Bumps phpunit/phpunit from 9.5.28 to 13.1.11.
Release notes
Sourced from phpunit/phpunit's releases.
... (truncated)
Changelog
Sourced from phpunit/phpunit's changelog.
... (truncated)
Commits
0f54097Prepare release5a05e6cMerge branch '12.5' into 13.1e78c9adPrepare release88a2bfaUpdate dependencies52c51eaMerge branch '12.5' into 13.17aae6a0Update dependencies3737450Merge branch '12.5' into 13.11dc3edbQuote PHP setting values containing "=" before forwarding via -dc6f7bb3Merge branch '12.5' into 13.106304c2Update expectationsDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)