-
Notifications
You must be signed in to change notification settings - Fork 259
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
Composer installation fail #25
Comments
I forced the update on packagist so it should be fixed now |
Yes it works. I forced the update too, but it was without effect... Maybe the last PR fixed the reference commit (I've configured the Packagist GH hook). |
When I say, "I forced the update", it was on packagist.org, not from the hook (even if I tried too). |
@willdurand yeah, the point is that the github API was still giving the old commit even when forcing packagist to recrawl (as the force push did not seem to trigger it). It is fixed now because I merged another PR and so added new commits |
Hey,
We can't install the bundle using composer. Composer tries to find the commit
63c990abc320828376671a0bd0ed861db6b9ad69
that does not exist on master.The text was updated successfully, but these errors were encountered: