Can't use an old version of Bevy.

[crabdancing]

If I try to use an old version of Bevy, like say, this:

bevy = { version = "=0.15.0", features = [
  "bevy_animation",
  "bevy_asset",
  "bevy_audio",
  "bevy_color",
  "bevy_core_pipeline",
 . . .
] }

It somehow ends up pulling in Bevy 0.15.3 as a dependency for all the sub-crates.

> cargo tree -p bevy
bevy v0.15.0
├── bevy_dylib v0.15.3
│   └── bevy_internal v0.15.3
│       ├── bevy_a11y v0.15.3
│       │   ├── accesskit v0.17.1
│       │   ├── bevy_app v0.15.3
. . .

My hypothesis is that it's because the bevy main crate doesn't do =0.15.0 for its own deps on other Bevy modules, thus Cargo ends up fetching the latest ones. What's the community's recommended solution to this?

[alice-i-cecile]

You could always manually modify and then commit your Cargo.lock file.

[crabdancing]

That was my first thought, but it seems too hacky to be considered best practice, and plus, there are hashes in there for each entry.

[mockersf]

you can add each crates you need to your cargo.toml with their exact version

for example:

bevy = { version = "=0.15.0", features = [
  "bevy_animation",
  "bevy_asset",
  "bevy_audio",
  "bevy_color",
  "bevy_core_pipeline",
  ...
] }
bevy_a11y = "=0.15.0"
bevy_asset = "=0.15.0"
...

[crabdancing]

@mockersf Hmm. How does Cargo know to pin the deps at the versions of the child packages, for the bevy package itself? In my experience, you very much can have a bunch of different versions, with the alternate versions coming from nested dependencies.