Skip to content

Refresh phpstan-laravel integration lock for pinned fixture - #15536

Closed
Gabrieljr42 wants to merge 1 commit into
phpstan:2.3.xfrom
Gabrieljr42:fix/phpstan-laravel-integration-lock
Closed

Gabrieljr42 wants to merge 1 commit into
phpstan:2.3.xfrom
Gabrieljr42:fix/phpstan-laravel-integration-lock

Conversation

@Gabrieljr42

Copy link
Copy Markdown

Both phpstan-laravel integration jobs now check out calebdw/phpstan-laravel@1797c66, but their shared lock still contains Laravel 13.35.0, PHPStan 2.3.1 and structarmed 0.18.11. These versions do not satisfy the pinned fixture’s current requirements, so Composer exits before either job can run. See the installation failure in phpstan-src#6760.

Refresh the integration lock with a targeted Composer update: Laravel 13.38.0, PHPStan 2.3.2 and structarmed 0.19.9. All other package versions stay unchanged.

Validation with PHP 8.5.12 and the pinned fixture:

  • Reproduced the original Composer install failure; the updated lock installs successfully.
  • composer run-script test:unit: 3,031 tests and 3,852 assertions pass.
  • The existing integration analysis configuration passes for all 232 files, using the PHAR and matching Turbo artifacts from phpstan-src#6760, run 40207520595.

AI assistance was used to prepare and validate this dependency update.

@ondrejmirtes

Copy link
Copy Markdown
Member

Already did it, thanks anyway.

@Gabrieljr42
Gabrieljr42 deleted the fix/phpstan-laravel-integration-lock branch October 25, 2026 16: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.

2 participants