Closed tobias-kuendig closed 6 years ago
Thank you @tobias-kuendig . though it was solved before you make this issue. BTW, now you can try version v3.2.1
v3.2.1? 😕
Is it possible to create a new tag 5.2.2 that includes the fix? You re-tagged 5.2.1 and I don't think packagist will trigger a new build if the version number is not elevated (it's not ideal anyways since there might be users that have already installed the bad 5.2.1 release).
I also deleted this tag from packagist and re-fetch it. May it'll be work fine. But if you face any type of issue with this, please let me know. I'll create a new tag.
Sorry for my bad English
Could you please publish a new bugfix to packagist since 5.2.1 currently contains an unwanted dump statement. :smile:
Thank you!