Update to Bevy 0.8.0
zicklag opened this issue · comments
Description
Bevy 0.8.0 was just released. It'd probably be good to update as soon as we can. We've already got dependencies such as leafwing that we have to use a Bevy 0.7.0 backport for, so even if we have to use forks for some dependencies like Bevy Egui until 0.8.0 support is merged it might not be any worse than where we are at with our dependencies now.
Updating might help us with scripting support, depending on how much we might be able to use bevy_mod_js_scriptin which is built on Bevy 0.8.0.
I'll probably try to port our stuff to Bevy 0.8 and see how difficult it will be so we can decide when we want to do that for sure.
Alternatives & Prior Art
No response
I agree with updating to 0.8 asap.
I know Loopless and LWIM both already have branches with support for bevy main.
bevy_kira_audio looks to as well.
bevy_fluent also looks like it has a branch tracking bevy main.
bevy_egui just released a 0.8 update
looks like we are waiting on or would have to update
bevy_rapier2d
bevy-parallax
Yep, along with Bevy inspector egui, which also has dependencies on rapier.
I suppose I'll just start opening pull requests. :D
Looks like rapier is the deepest dep and should be updated first.
I suppose I'll just start opening pull requests. :D
Looks like rapier is the deepest dep and should be updated first.
Thank you!
So, as I keep looking, this ends up pretty deep, when we need new releases all the way down to nalgebra, so I think it's probably better for us just to wait for some of those PRs to be merged than to try and make some git dependencies working, because keeping them up-to-date will be a pain as different maintainers may ask for changes.
That doesn't mean we can't submit PRs for the projects that don't already have them, though, and wait for those to get releases before we update.
I don't need Bevy 0.8 for the scripting MVP, either, so we aren't blocked by it just yet.
I don't have any opinion on this, so... enjoy
Hey, I just found out why Punchy was depending on crates like bevy_pbr and bevy_gltf, even though we shouldn't have needed it. They were dependencies of bevy-parallax. I'll fix that in my PR to update it to Bevy 0.8.
So, as I keep looking, this ends up pretty deep, when we need new releases all the way down to
nalgebra, so I think it's probably better for us just to wait for some of those PRs to be merged than to try and make some git dependencies working
The nalgebra change is already merged, but you're right its not yet released.
bevy-parallax
All Punchy devs should have push access to this repo, so lemme know if you don’t.
Wow, that was fast! Cool. That might get us far enough to use git dependencies for the rest. I'll be trying that out soon.
I've got a working PR to update Bevy Parallax: Corrosive-Games/bevy-parallax#10