Problem/Motivation
phpstan/phpstan 1.8.7 and above throw errors when running analysis, https://github.com/phpstan/phpstan/issues/8139
Proposed resolution
Introduce a conflict section in composer.json for phpstan >=1.8.7 until an upstream fix is released
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 3314774-2.patch | 868 bytes | spokje |
Comments
Comment #2
spokjeComment #3
spokjeOpened #3314873: Remove PHPStan conflict section in composer.json, bump to ^1.8.10 as a follow-up to update/remove the conflict section when a fix lands in a PHPStan release.
Comment #4
spokjeTest failures are all unrelated JS failures (at least that's what it looks like me), triggered retest.
More importantly:
PHP 8.1 & MySQL 5.7 updated depsnow doesn't returnCustom Commands Failedbefore even starting any tests.Comment #6
spokjeTestBot is having a bad JS-test day apparently. Not wasting any more test-cycles on it.
Comment #8
spokjeFrequent random JS test failures => back to NR
Comment #9
longwaveRTBC, given https://www.drupal.org/pift-ci-job/2498079 and local testing that produced the same failed result with PHPStan 1.8.8.
Comment #11
spokjeComment #13
catchCommitted/pushed to 10.1.x and cherry-picked to 10.0.x, thanks!