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
Could not parse version constraint @dev: Invalid version string "@dev" #109
Comments
The
Please don't remove it for now though, but really this is a weird constraint as it literally equals to |
The reason it fails I assume is that when combined with |
Oh cricky... that was one of my old attempts to solve the recursive dependency issue you helped me with the other week. The branch was pushed at the time (a year ago) as I needed it available for tests with the other repos at that time, but I have since removed it (some time last week), now I have it properly solved/fixed and IIRC I have removed every one of the other test branches I had related to my earlier attempts in other repos as well. So, how come Packagist is still showing that branch ? Do removed branches not get scrubbed automatically ? I never even thought to look for weird dependency constraints in branches which are no longer available and never made it into a Thank you so much for finding the problem and fixing it. I imagine there may be more people with weird versions in temporary/test branches, so at least it's one less thing which can go wrong. |
Oh and another question: why did it break with three out of five repos using this dependency, but not for the other two ? |
IIRC, they get removed only after 1 week, because in the past (when starting packagist years ago), the github API was a lot less reliable and could result into branches being missed during an update while they were still there. |
note that as a maintainer, you can force the removal of a version on packagist (if the version you remove still exists in your github repo, that's silly because the next update will recreate it. but it is useful to delete a version from a removed branch in a faster way if it causes issues) |
I'm aware of that, but would hope I wouldn't have to do that manually for the hundreds/thousands of PR feature branches I pull to various repos, though from your comment I gather they get removed after a week, so that branch should automatically be removed either today or tomorrow. I hadn't touched it manually for now as @Seldaek asked above not to:
|
Ah feel free to remove it now :) as for why it broke with some, it might be because not all versions were loaded depending on context, where the package was required etc |
@Seldaek Thanks for your response and thanks again for getting this fixed. I've (manually) removed the problem branch now from Packagist.
As far as I can see, the context was the same for all: none of these repos have a committed |
Follow up on #107
I still have some projects running into problems with Composer 1.10.12 / Semver 3.1.0. For the time being, I've solved it by downgrading Composer to 1.10.10, so no rush.
I can't seem to figure out what the problem version constraint is though.
The problem seems to be with
phpcsstandards/phpcsdevtools
.phpcsstandards/phpcsdevtools composer.json
Running
composer install
results in the following error output:Additional information
@dev
, so I can't pinpoint the problem.composer install
/composer update
on nearly all of the individual dependencies of the project (save forroave/security-advisories
andphpunit/phpunit
) and they all install without problems.phpcsstandards/phpcsdevtools
, three are running into problems with the above mentioned error:wp-coding-standards/wpcs
,phpcsstandards/phpcsextra
andyoast/yoastcs
.phpcompatibility/php-compatibility
andwptrt/wpthemereview
The text was updated successfully, but these errors were encountered: