Problem/Motivation
With the 1.1.31 release of mglaman/phpstan-drupal, we see our "updated deps" test-runs fail on both 10.0.x and 10.1.x.
(This is not the only reason, see #3356337: Fix incorrect type hint and make daily "updated deps" QA jobs pass )
Steps to reproduce
https://www.drupal.org/node/3060/qa
Proposed resolution
- Upgrade mglaman/phpstan-drupal to 1.1.31
- Create a new baseline
- Bump version of mglaman/phpstan-drupal in composer.lock to 1.1.31 , since the newly created baseline won't pass on 1.1.31
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 3357114-10.0.x-3.patch | 5.81 KB | spokje |
| #2 | 3357114-10.1.x-2.patch | 6.54 KB | spokje |
Comments
Comment #2
spokjeComment #3
spokjeComment #4
spokjeComment #5
smustgrave commentedSeems to have an issue for 10.1
Comment #6
spokjeNot really
- I accidentally tested the 10.0.x patch against 10.1.x: That didn't apply (of course)
- The "updated deps" run on 10.1.x still fails (although fails less), because of:
Comment #7
smustgrave commentedAh you're right. Long week.
Comment #8
mondrakeWhy is there a baseline addition? Is that related to the introduction of the TrustedCallback attribute?
Comment #9
spokjeYep, looks like a regression.
Opened https://github.com/mglaman/phpstan-drupal/issues/543
Comment #10
catchShould we wait for https://github.com/mglaman/phpstan-drupal/issues/543 or just update again when that's fixed?
Comment #11
spokjeI would say: Update now, there are also more accessCheck issues with the new version, but haven't got around to admin/fix those.
-2/+1 in the baseline seems like a win :)
Comment #12
catchNeeds a re-roll.
Comment #13
spokjeUnsure what needs re-rolling?
Both the 10.0.x and 10.1.x-patch still apply, back to RTBC.
Comment #16
catchSame confusions as #5, even though I'd already read it.
Committed/pushed the respective patches to 10.1.x and 10.0.x, thanks!