Pieter Hoste
Pieter Hoste
Hey @spankevich Sorry for the delay, I was in holiday some weeks ago and am still catching up on certain things that happened while I was away, like this report....
@sgeleon: please edit your post and remove the `repositories` section, because it's full of passwords you probably don't want to leak to the outside... As for the issue you are...
It's not expected behavior, I'm sure this was not implemented with this in mind. People won't generate static assets after every cache flush, that's just ridiculous. This needs to be...
Possibly fixed by: https://github.com/magento/magento2/commit/38501f017f24c4c4deb9bbbcfe2563fd51cf4341 ? At least the second problem from the report. Not sure about the first problem.
Adobe posted a KB article about this some hours ago and it contains a patch: https://experienceleague.adobe.com/en/docs/commerce-knowledge-base/kb/troubleshooting/known-issues-patches-attached/backwards-incompatible-changes-for-graphql-placeorder-api-in-adobe-commerce-2-4-6-p8
Was fixed by internal Adobe devs in https://github.com/magento/magento2/commit/18dee3d979ed8ee68a44324e892e6b7f570c987c, so we can probably close this PR?
Some quick feedback from me. I've tested phpstan 1.11.3 in combination with this module (hacked it using `"phpstan/phpstan": "1.11.3 as 1.10.67"` in composer). Tried it on 4 different Magento modules...
Out of curiosity, have you tried this with [composer 2.9.2](https://github.com/composer/composer/releases/tag/2.9.2)? As it contains this fix: > Fixed partial updates failing when another package in the lock file has a known...
Make sure to take over the changes done to the `composer.json` file from core magento, the diff between 2.4.6-p7 and 2.4.7-p2 is this: ```diff --- magento246-p7-test/composer.json 2024-08-06 05:26:14 +++ magento247-p2-test/composer.json...
You are free to do with the `composer.json` like you want, you are the owner of that file. See the default one Magento creates as a base and as something...