-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Figure out how to manage patches with cweagans/composer-patches 2.x (or alternative) #2612
Figure out how to manage patches with cweagans/composer-patches 2.x (or alternative) #2612
Comments
2023-07-26 Meeting discussion@tadean pointed out that we don't actually need the full functionality provided by composer-patches. We really only need to apply patches from the @trackleft Pointed out that some of our other az-digital projects also add patches (e.g. |
Promising new update from cweagans! |
What is the problem that we want to solve?
The maintainer of cweagans/composer-patches has announced that the
2.0.0
version of his composer-patches plugin will no longer provide dependency patch resolution (i.e. discovering and applying patches defined by dependencies rather than in the root levelcomposer.json
file).https://www.cweagans.net/2023/07/dependency-patch-resolution/
We currently rely heavily on this feature of composer-patches
1.x
since we maintain most of our patches in the az-digital/az_quickstart repo which is used as a dependency in project-specificcomposer.json
files (e.g. az-digital/az-quickstart-scaffolding and az-digital/az-quickstart-pantheon).We'll need to figure out a plan for how to deal with this change. Some high-level options include:
1.x
(which will stop being supported soon after2.0.0
is released)2.x
to restore the dependency resolution functionality (or find a new composer plugin that extends composer-patches in this way)The text was updated successfully, but these errors were encountered: