Configuration error - Next patches weren't found: ACSD-48070. -> but patch is not listed to be used.

[ProxiBlue]

Magento 2.4.4-p11

I think latest quality patches are broken. 1.1.56

no matter what command you run, it fails with error:

Configuration error - Next patches weren't found: ACSD-48070.

the noted patch is not n the wanted patch list:

01:29 $ ./vendor/bin/magento-patches apply MDVA-43167 MDVA-44660 MDVA-44703 MDVA-44100 ACSD-46146 ACSD-45754 MDVA-30106 MDVA-43983 MDVA-41628 MDVA-38626 MDVA-38728 MDVA-42269 MDVA-42237 MDVA-42410 MDVA-41136 MDVA-42950 MDVA-12304 MDVA-42689 MDVA-41229 MDVA-39605 MDVA-43824 MDVA-43601 MDVA-44188 ACSD-46404 MDVA-44887

In OptionalPool.php line 267:
                                                                                                                                                                    
  Configuration error - Next patches weren't found: ACSD-48070. Please, check with "status" command availability of these patches for the current Magento version.  
                                                                                                                                                                    

apply <list-of-patches>...

downgrade to 1.1.55 fixes issue, and patches work.

even just using the status command, breaks with same error

[ProxiBlue]

Having checked releases, I see .55 is the latest, but, composer is in fact installing .56 ?

"magento/quality-patches": "1.1.*"

update: It was noted to me that they release the new version in package manager prior to updating version in github, so that is why I see this small discrepency.

[kanevbg]

I removed each entry related to the ACSD-48070 from support-patches.json and then the version 1.1.56 worked. That was a fit for me thus sharing.

[ssx]

Also seeing this on a 2.4.6-p8 project. Pinning magento/quality-patches to 1.1.55 solves the issue temporarily.

[Paulsky]

Installing this package to fix Magento errors only to get even more errors! 🎉

[michaellehmkuhl]

Unfortunately, I'm in need of a patch that's included in 1.1.56. So I guess we're just stuck until this issue is fixed?

[ProxiBlue]

@michaellehmkuhl see what #130 (comment) did, which will allow you to continue

[michaellehmkuhl]

@ProxiBlue Thanks for the tip. Editing that file manually doesn't seem like it's going to be a workable solution for implementing into CI, but at least it gets me one step farther along.

[ProxiBlue]

@michaellehmkuhl You can use composer patches, via vamio/composer patches and patch it as it is included.

bit of effort, but will allow you to progress. who knows when they will fix this, as seems they are not minding this issue in anyway. it breaks shit, is critical, and they just don;t care. no attention to this ticket in any way.

You can utilise this great script by @MagePsycho to make the patch quick and easy: https://github.com/MagePsycho/composer-patch-creator