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
Require command unable to detect latest stable #3900
Comments
|
Found out why; this line returns false, because the array index of @Seldaek can you confirm that the Edit: another way to confirm this suspicion, running works just fine. |
|
composer package names are always lowercased. |
|
I'll get right on that. |
* master: (66 commits) Fix regression with non-SPDX licenses in show command, refs composer#3885 Add comment about --, refs composer#3853 [bugfix] Fixed undefined var in DiagnoseCommand::execute(). Add BC method for old usage, refs composer#3857 Update contributing Add multiline_array_tailing_comma fix Add PHPCSFixer config CS fixes Update changelog Ignore all .git dirs in the vendor dir recursively Link to semver version constraint tester Fix typo in aliases.md [bugfix] Updated ```DiagnoseCommand::execute()``` and ```DiagnoseCommand::getGithubRateLimit()``` Silence symlink() error Fixes composer#3900 Remove unused variable Unused variable Fix composer#3903 Readme: 00-intro - use __DIR__ Update 04-schema.md ...
Composer seems to be unable to detect the latest stable release when running:
But the following does work:
composer require beberlei/DoctrineExtensions "~1.0"Packagist and other services seems seem happy that
1.0.1is the latest stable, but the require command isn't happy? Wondering if it's to do with thevtag prefix?https://github.com/beberlei/DoctrineExtensions/issues/145
The text was updated successfully, but these errors were encountered: