Can't compile with mlua anymore about bevy_mod_scripting HOT 4 CLOSED

Hi, I think tealr got an update, I remember there being some issues with cargo selecting unexpected versions for it, have a look at: lenscas/tealr_doc_gen#18,
Solution is to either:

• figure out how to make cargo respect the alpha version
• update to the newest tealr version

from bevy_mod_scripting.

W.r.t bevy 0.12 I am currently heavily invested on this branch: https://github.com/makspll/bevy_mod_scripting/tree/feature/derive_macros

basically a complete re-write of the codegen + possibly allowing consumers to generate an API similarly to how we do it for Bevy (except hopefully completely automatically), and was hoping to finish that before releasing, but given it's taking me way longer than expected, I might just release a pure bevy patch (for both 0.11 and 0.12), and PR's are very much welcome!

from bevy_mod_scripting.

Right now my own project is awkwardly pinned to a bevy 0.12-dev version to clean up some issues, so I was trying to do a 0.12 patch to be able to be solidly on released bevy version. I'll see if I can do an update to just current tealr versions to get that cleaned up and then move on to the 0.12.

from bevy_mod_scripting.

Sorry about this. I didn't know (nor expected) that me releasing a non alpha version would break this. In fact, as far as I understand how cargo should resolve versions it should go for the exact version if you add stuff like --alpha after the version number. I guess I need to re read how this part work to prevent it from happening in the future.

Again, sorry that this happened. It was not at all my intention to break anything, and especially not without notice.

from bevy_mod_scripting.