Closed BozzaDaniel closed 3 months ago
Hi @BozzaDaniel, thanks for your report!
I was able to reproduce this issue and will work on fixing this as soon as possible. In the mean time, please revert to using v2.0.0 if possible. Sorry about the inconvenience! I'll post updates as soon as I have them.
@BozzaDaniel @dcacenabes This has been fixed and released on v2.1.1
@BozzaDaniel Again, thank you so much for reporting this! It would've taken me a lot longer to realize this was broken otherwise. In the PR where I fixed this, I changed how I run integration tests (there was a bug on those), so this type of issue won't happen again 🙏
Cheers!
@BozzaDaniel @dcacenabes This has been fixed and released on v2.1.1
@BozzaDaniel Again, thank you so much for reporting this! It would've taken me a lot longer to realize this was broken otherwise. In the PR where I fixed this, I changed how I run integration tests (there was a bug on those), so this type of issue won't happen again 🙏
Cheers!
Already bumped, working like a charm!
After updating to 2.1.0 this error occurred after running the following command:
On Windows:
On macOS:
Release 2.0.0 works without any errors.