bevy ecs version conflict when compiling with Bevy 0.18.0

[smurfer]

using bevy_framepace v0.20.1 with bevy 0.18.0 leads to a compile error as there are conflicting versions of the Bevy ECS: 0.18.0 and 0.17.2

note: there are multiple different versions of cratebevy_ecs in the dependency graph

cargo tree shows

├── bevy_framepace v0.20.1
│   ├── bevy_app v0.17.2
│   │   ├── bevy_derive v0.17.2 (proc-macro)
│   │   │   ├── bevy_macro_utils v0.17.2
│   │   │   │   ├── parking_lot v0.12.5
│   │   │   │   │   ├── lock_api v0.4.14
│   │   │   │   │   │   └── scopeguard v1.2.0
│   │   │   │   │   └── parking_lot_core v0.9.12 (*)
│   │   │   │   ├── proc-macro2 v1.0.92 (*)
│   │   │   │   ├── quote v1.0.37 (*)
│   │   │   │   ├── syn v2.0.114 (*)
│   │   │   │   └── toml_edit v0.23.7 (*)
│   │   │   ├── quote v1.0.37 (*)
│   │   │   └── syn v2.0.114 (*)
│   │   ├── bevy_ecs v0.17.2

[streifen-dev]

bevy_framepace 0.20.* only supports Bevy 0.17.*

However, since the version bump in PR #75 seems to be working fine™ you can just replace the dependency on bevy_framepace in your Cargo.toml file with the following line:

bevy_framepace = { git = "https://github.com/aevyrie/bevy_framepace", branch = "main" }

This will pull the latest commit from this project's main branch, instead of the official versioned crates from crates.io. Beware that when pulling crates directly from git repos you will fetch the latest commit on the specificed branch by default. Those commits might not work at all for some time and reflect a WIP state of the crate. And manually cherry-picking commits once something breaks can be a real pain.

There is probably a reason that 0.21 is not officially out yet. Though stuff on main *ought to be* in a *somewhat* workable state, there are no guarantees.

If you just cannot wait then go for it, but I'd advise that you check periodically whether 0.21 is officially out and grab it from crates.io instead of the git repo asap.

[smurfer]

Thanks for the info and suggestion. For the time being, I am not using the frame rate reduction, as it is more of a hygiene factor in my app. Will wait until the updated version will be official.