Skip to content

Test PHP 8.5 and 8.6 with the current Pest stack - #1224

Merged
freekmurze merged 1 commit into
mainfrom
fix/php-85-86-ci
Nov 5, 2026
Merged

freekmurze merged 1 commit into
mainfrom
fix/php-85-86-ci

Conversation

@freekmurze

@freekmurze freekmurze commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Upgrade to Pest 5 and compatible plugins/Testbench; require PHP 8.4.1+ and Laravel 13 under owner authorization to drop older unsupported targets.
  • Run stable and lowest dependencies on actual PHP 8.4, 8.5 and 8.6, with runtime assertions and fail-fast disabled.
  • Restore Livewire test coverage, update closure assertions for PHPUnit 13, migrate the XML schema, and rename two unchanged serialization snapshots for the new runner.
  • Leave production PHP behavior and Composer security blocking unchanged.

Verification

  • Full suite passed locally across all six runtime/dependency combinations, including real PHP 8.5.12 and PHP 8.6.0-dev.
  • Five rows: 1327 passed / 3619 assertions. PHP 8.6 lowest: 1318 passed plus 9 non-failing dependency deprecations / 3619 assertions. Existing 11 skipped and 1 todo retained.
  • PHPStan, targeted PHP CS Fixer, actionlint, strict Composer validation, runtime mismatch checks, and clean-base patch application passed.
  • Pest 5.3.5 currently caps PHPUnit at 13.4.5; forcing 13.4.6 would conflict.

Hosted CI verified on head a268756: all six test jobs passed in both the push run and PR run. Logs confirm actual PHP 8.5.12 and PHP 8.6.0-dev in both dependency modes, with the test counts above. PHPStan and styling also passed. No merge or deployment is requested.

Upgrade Pest and its plugins, restore Laravel 13 Livewire coverage, and verify the actual PHP runtime in every matrix job.

Amp-Thread-ID: https://ampcode.com/threads/T-01a1aafd-eb58-72c6-84d5-bef3b6f7649a
@freekmurze
freekmurze merged commit 7bda01d into main Nov 5, 2026
16 checks passed
@freekmurze
freekmurze deleted the fix/php-85-86-ci branch November 5, 2026 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant