Why does composer pick an older version of the package? #12274

bilogic · 2025-01-13T02:50:00Z

bilogic
Jan 13, 2025

Using Composer version 2.8.4
I have package A that has "filament/filament": "^3"
I have project B that has "me/package-a": "^10"
Together, composer downloads and uses filament v3.2.130
The problem is, filament v3.2.133 is the latest
If I were to force package A to ^3.2.133, it works and downloads the latest version (but I can't keep being on the lookout for this)

And for the strangest of reasons, filament/spatie-laravel-media-library-plugin made it to 3.2.133, see bottom

Why does composer pick the older version when both works?

Here is what I have done so far

checked that filament on packagist looks ok
composer update -W did not fix the problem
deleting composer.lock
deleting vendor/filament
deleting ~/.cache/composer

based on this, I also don't think filament is limited to v3.2.130 by another package

$ composer why-not filament/filament 3.2.133
filament/filament         v3.2.133 requires         filament/actions (self.version)                    
me/project-b 10.x-dev does not require filament/actions (but v3.2.130 is installed)       
filament/filament         v3.2.133 requires         filament/forms (self.version)                      
me/project-b 10.x-dev does not require filament/forms (but v3.2.130 is installed)         
filament/filament         v3.2.133 requires         filament/infolists (self.version)                  
me/project-b 10.x-dev does not require filament/infolists (but v3.2.130 is installed)     
filament/filament         v3.2.133 requires         filament/notifications (self.version)              
me/project-b 10.x-dev does not require filament/notifications (but v3.2.130 is installed) 
filament/filament         v3.2.133 requires         filament/support (self.version)                    
me/project-b 10.x-dev does not require filament/support (but v3.2.130 is installed)       
filament/filament         v3.2.133 requires         filament/tables (self.version)                     
me/project-b 10.x-dev does not require filament/tables (but v3.2.130 is installed)        
filament/filament         v3.2.133 requires         filament/widgets (self.version)                    
me/project-b 10.x-dev does not require filament/widgets (but v3.2.130 is installed)       
Not finding what you were looking for? Try calling `composer update "filament/filament:3.2.133" --dry-run` to get another view on the problem.

$ composer update "filament/filament:3.2.133" --dry-run
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
    - Root composer.json requires me/package-1 ^10 -> satisfiable by me/package-1[10.x-dev].
    - me/package-1 10.x-dev requires me/package-a ^10 -> satisfiable by me/package-a[10.x-dev].
    - me/package-a 10.x-dev requires filament/filament ^3 -> satisfiable by filament/filament[v3.2.133].
    - filament/filament v3.2.133 requires filament/actions v3.2.133 -> found filament/actions[v3.2.133] but the package is fixed to v3.2.130 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

# composer show
...
filament/actions                             3.2.130  Easily add beautiful action modals to any Livewire component.
filament/filament                            3.2.130  A collection of full-stack components for accelerated Laravel app development.
filament/forms                               3.2.130  Easily add beautiful forms to any Livewire component.
filament/infolists                           3.2.130  Easily add beautiful read-only infolists to any Livewire component.
filament/notifications                       3.2.130  Easily add beautiful notifications to any Livewire app.
filament/spatie-laravel-media-library-plugin 3.2.133  Filament support for `spatie/laravel-medialibrary`.
filament/support                             3.2.130  Core helper methods and foundation code for all Filament packages.
filament/tables                              3.2.130  Easily add beautiful tables to any Livewire component.
filament/widgets                             3.2.130  Easily add beautiful dashboard widgets to any Livewire component.
...

Answered by bilogic

Jan 13, 2025

I found the issue, package A and project B both require livewire/livewire, by using the latest version of livewire for project B, it forced package A back to an older version, see filamentphp/filament#15062

View full answer

bilogic · 2025-01-13T03:26:35Z

bilogic
Jan 13, 2025
Author

I found the issue, package A and project B both require livewire/livewire, by using the latest version of livewire for project B, it forced package A back to an older version, see filamentphp/filament#15062

7 replies

bilogic Jan 13, 2025
Author

Ok thanks, let me think about it, off hand my approach is:

Latest is most secured, so if I'm not on the latest, I want to know why
Downgrade is worse, it means something is asking specifically for this, I also want to know why (and check on the offending package)

Seldaek Jan 13, 2025
Maintainer

Yeah essentially if you see a downgrade of foo/a from 2.0.0 to 1.9.0 for example you can run composer why-not foo/a 2.0.0 after and it should explain what conflicted with it.

bilogic Jan 13, 2025
Author

Ah you reminded me, I would not know if a version is the latest unless I know the package inside out or watching composer output carefully.. (I normally don't watch carefully because of the confidence in composer 🤣)

So perhaps, it makes senses to inform developer which packages are not at their latest versions? Perhaps if not latest minor or not latest patch?

xabbuh Jan 13, 2025

You can get that output using composer outdated.

bilogic Jan 13, 2025
Author

@xabbuh nice thanks!

Uh oh!

Why does composer pick an older version of the package? #12274

Uh oh!

Uh oh!

bilogic Jan 13, 2025

Why does composer pick the older version when both works?

Replies: 1 comment · 7 replies

Uh oh!

bilogic Jan 13, 2025 Author

Uh oh!

Uh oh!

bilogic Jan 13, 2025 Author

Uh oh!

Seldaek Jan 13, 2025 Maintainer

Uh oh!

Uh oh!

bilogic Jan 13, 2025 Author

Uh oh!

xabbuh Jan 13, 2025

Uh oh!

bilogic Jan 13, 2025 Author

bilogic
Jan 13, 2025

Replies: 1 comment 7 replies

bilogic
Jan 13, 2025
Author

bilogic Jan 13, 2025
Author

Seldaek Jan 13, 2025
Maintainer

bilogic Jan 13, 2025
Author

bilogic Jan 13, 2025
Author