Closed prudloff-insite closed 8 months ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This doesn't happen in 2.x anymore. Re-patching is a manual step now. I'm not making further changes to 1.x at this point.
Verification
composer self-update
)composer update cweagans/composer-patches
)What were you trying to do (and why)?
I am running
composer require consolidation/robo:^3.0 --no-install
after having added patches for in ourcomposer.json
file.Our broader use case is that we have a script that adjust patches (with composer-patches-cli) and requirements (with
composer require --no-install
) without actually installing anything. And then we do a finalcomposer install
(without--no-install
) when we are sure the patches are actually compatible withe the required versions.I am using composer-patches 1.7.3 with Composer 2.5.5.
What happened? What did you expect to happen?
This package was uninstalled (and then not reinstalled because of
--no-install
):IMHO, when using
--no-install
, the intent is to only change the lock file and not the vendor folder. So composer-patches should not delete any folder when using this option.Contents of
composer.json
Contents of
patches.lock.json
Full output of
composer patches-doctor
Full output of relevant Composer command with the
-vvv
flag added