-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Broken composer package in 5.2.0 #17661
Comments
Hi @fliespl This is a duplicate of #17570 in some way. Maybe the release script should write also the version in This is all because of Roave/SecurityAdvisories#76 |
Thanks, I am not sure how I missed that ticket :) I do believe adding version tag is the way to go, cause every package that will set "conflicts" with mention to phpmyadmin would cause such issue. |
@MauricioFauth @ibennetch does it seem okay to you to set at release time the version, or keep it written all the time like |
Ref: Roave/SecurityAdvisories#76 Fixes: phpmyadmin#17661 Signed-off-by: William Desportes <williamdes@wdes.fr>
Ref: Roave/SecurityAdvisories#76 Fixes: phpmyadmin#17661 Signed-off-by: William Desportes <williamdes@wdes.fr>
Installing with composer this still happens to me. So I have to do now:
|
Yes, it still happens until 5.2.1 is out, you can subscribe to #17830 |
Describe the bug
Cannot install additional package with zipped file.
I know that composer packages are preinstalled, but adding new package was working just fine with version 5.1.1.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Successful install of package.
What happens
composer fails with:
What I think is happening - composer.json is missing explicit version declaration.
Yeap, explicitly adding
"version": "5.2.0"
to composer.json worked.Probably worth rethinking zip strategy?
The text was updated successfully, but these errors were encountered: