Should v0.18.1 dependencies be updated to v0.18.1 too (replacing v0.18.0)

[peterhirn]

Hi,

I'm wondering if dependencies like bevy_internal should be set to the same version as the meta package?

eg. https://github.com/bevyengine/bevy/blob/release-0.18.1/Cargo.toml#L714

I'm new to this so not sure if this is intended.

Using Renovate to manage crate versions this creates PRs where only the bevy crate is updated, but all dependencies stay at v0.18.0.

[MukundaKatta]

This is intentional but confusing — Bevy uses =0.18.0 on internal crates so a 0.18.1 patch publish doesn't force a breaking resolve on downstream users. The meta crate re-exports bevy_internal with a looser range. For Renovate, either ignore bevy_internal/bevy_* sub-crates (they come along for the ride via bevy), or add a grouping rule so all bevy_* crates bump together.