Closed Ancient77 closed 5 months ago
Hello!
I know why this issue appends but still seems strange to me. I am trying to reproduce it.
@Ancient77 you can try to get the pre-released I just rolled out cargo install atac@=0.13.0-bis
Having the same issue with fresh v0.13.0 install, 0.13.0-bis fix it
The weird thing here is that the v0.13.0 was published yesterday at 22:00 (paris time) but I have updated the postman_collection_import
crate to v0.2.3 and the code using it on the main branch today at around 10:00 (still paris time).
@Ancient77 you can try to get the pre-released I just rolled out
cargo install atac@=0.13.0-bis
this works! Thank you very much for the quick fix ❤️
The weird thing here is that the v0.13.0 was published yesterday at 22:00 (paris time) but I have updated the
postman_collection_import
crate to v0.2.3 and the code using it on the main branch today at around 10:00 (still paris time).
The explaination is that parse_postman_collection = "0.2.2" mean postman_collection = "^0.2.2", you sould have used "=0.2.2" or more elegantly use "0.3.0" for postman_collection to notify the API incompatibility
No the problem was the other way around, the crates.io atac code has been updated today without me publishing it...
If the postman import lib handles the Javascript body content-type or not, it would have changed nothing. The problem is the main atac code trying to handle Javascript which was not bundled in v0.13.0 Weird
When I am trying to upgrade from 0.12 to 0.13 using
cargo install atac
, I get this error: