chore: upgrade Pest to v5 - #28
Merged
Merged
Conversation
Bumps the dev requirement from ^4.0 to ^5.0 (resolves to v5.0.3, which brings PHPUnit 13). No test changes were needed. Verified by replicating the CI workflow against a fresh Laravel app: 25 tests, 63 assertions, all passing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the
pestphp/pestdev requirement from^4.0to^5.0.composer update pestphp/pest --with-all-dependenciesresolves to v5.0.3, which brings PHPUnit 12.5 → 13.2 along with thearch,mutate, andprofanityplugins at^5.0.composer.lockis gitignored, so the diff is a single line.No test code changes were needed — nothing in the suite hits a Pest 4 → 5 breaking change.
Verification
The suite can't run standalone in this repo (no
phpunit.xml/Pest.php— there's no app to boot), so I replicated.github/workflows/test.ymlexactly against a fresh Laravel app:laravel new --pest→ local path repo →composer require sweetalert2/laravel:@dev→ copy tests and views →./vendor/bin/pest.The CI workflow itself needed no edit: the Laravel installer already provisions Pest 5 in fresh apps, which is what CI actually runs against.
🤖 Generated with Claude Code