composer outdated "drupal/*" does not report 8.x-3.14
Steps to reproduce
Drupal admin interface admin/reports/updates reports that an update is available for version 8.x-3.13.
Recommended version is 8.x-3.14.
composer outdated "drupal/*" does not report availability of version 8.x-3.14.
https://www.drupal.org/project/geocoder/releases/8.x-3.14 installation with composer advises:
composer require 'drupal/geocoder:^3.14'
But running this command installs drupal/geocoder (dev-3.x 427d69a) not 8.x-3.14.
I uninstalled the module then used composer remove.
I then ran composer require drupal/geocoder and it installed version 8.x-3.13.
Uninstall and remove then composer require 'drupal/geocoder:^3.14' installed drupal/geocoder (dev-3.x 427d69a) again.
Comments
Comment #2
itamair CreditAttribution: itamair as a volunteer commentedIf I run the following command:
composer show drupal/geocoder -a
I regularly see the availability of 3.14.0 version ... (@see report below)
Please check all this again.
I cannot replicate your issue ...
Comment #3
GrahamShepherd CreditAttribution: GrahamShepherd commentedI have removed drupal/geocoder with composer and also removed geocoder-php/google-maps-provider
When I install geocoder with composer it installs 8.x-3.13, not 8.x-3.14.
Or if I specify the version, it installs the dev version.
I have repeated the exercise on an entirely different site and I get exactly the same result.
Comment #4
GrahamShepherd CreditAttribution: GrahamShepherd commentedWhen I run composer show drupal/geocoder I get the same list of dependencies as you. I have rearranged the order to match yours but the dependencies are the same.
Comment #5
itamair CreditAttribution: itamair as a volunteer commentedI don't have your issue ... though I removed and re-required drupal/geocoder it correctly installs 3.14 version.
Be sure to have the correct requirements in your composer.json that should look like the following:
$ composer require 'drupal/geocoder:^3.14'
If it is correct then you might probably have some other cross constraint on drupal/geocoder.
This doens't look a geocoder project issue ...
Comment #6
mmjvb CreditAttribution: mmjvb as a volunteer commentedNo problem with Composer v1, problem occurs with Composer v2.
Comment #7
GrahamShepherd CreditAttribution: GrahamShepherd commentedmmjvb, you experience the same thing?
My composer version 2.0.6
Comment #8
mmjvb CreditAttribution: mmjvb as a volunteer commentedIndeed, investigated based on your report. That is when I discovered the difference in Composer version. Also saw another reporting the same thing.
EDIT: see https://www.drupal.org/project/bootstrap4/issues/3183903#comment-13911339
Recommended to report with the facade as the meta data must be ok, otherwise v1 would have the same problem.
Obviously, this is an educated guess, not knowing what is causing this. V2 works differently as repositories is concerned, so it could be either the facade or composer v2.
Comment #9
itamair CreditAttribution: itamair as a volunteer commentedWooow. Weird Composer v2 behaviour.
Let's keep this open then ... thanks @mmjvb
Comment #10
GrahamShepherd CreditAttribution: GrahamShepherd commentedOn several sites I have just run:
composer outdated "drupal/*"
and (amongst others) got the expected result:
drupal/geocoder 3.13.0 3.14.0
Running:
composer update drupal/geocoder -W
updated the module correctly as far as I can tell.
I have no idea what has changed but it looks OK now.
Comment #11
mmjvb CreditAttribution: mmjvb as a volunteer commentedConfirmed:
Noticed this to be resolved for bootstrap4 as well. Haven't found issue that resolved it upstream.