Point at Bevy main #8
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because we're doing some things that are slightly unusual, we may need to make some small changes upstream to support our patterns. For example, I just had to open bevyengine/bevy#22024.
Because we are committing our lockfile, depending on an unstable branch should be fine, we just need to make sure that everything builds when running
cargo updateto bring in a new Bevy version.The downside here would be if we depend on third party Bevy ecosystem crates, for example
bevy_vello. However, we're not there yet and in many cases it's possible just to patch the dependency assuming there aren't major breaking changes: https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section. Ecosystem crates also always appreciate a PR to bring them up to date. (:But let's cross that bridge when we get there!