Composer update sometimes doesn't delete obsolete files #12400
Replies: 1 comment 1 reply
-
|
That sounds incorrect to me, so either you're doing something wrong or something you're not sharing here, or there's a bug but it'd be the first time I hear of such behavior. The sometimes aspect makes it a bit difficult.. Can you try to spot a pattern here? Or ideally to share reproduction steps? Do you run a plain |
Beta Was this translation helpful? Give feedback.
-
|
@Seldaek Thank you for the reply! We did some research, so my reply took some time. Sorry for that. The issue occurs only in Gitlab CI and in the end we figured that the files are always from the cache. The timeline is the following:
The result is, if the version from the cache has a file that is not present anymore in the later version, it persists. It wont happen with composer install. However, our way to run composer update is to make sure some packages are the latest version, even if something else is specified in the lock file. Its not really how to use composer, so it might be an edge-case thats only relevant for our workflow. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
For my example, I have two projects: A Library called ABC and a project XYZ. Project XYZ installs ABC as a dependency.
Now let there be a new version of ABC which deletes a file.
Now I noticed if I run
composer update, the file might not be removed from the package invendor.composer installdeletes the file.Is this intended behavior? Or am I doing something wrong here?
Beta Was this translation helpful? Give feedback.
All reactions