Closed rparrett closed 3 months ago
@rparrett thanks for letting me know! I definitely should have done that. Full transparency, I have just been incrementing the minor version number because I wasn't sure when to increment major numbers. Now I know for future use!
Do you have the link to the help thread?
No worries! Users can always pin specific versions with =0.1.10
, but it can definitely cause confusion when all your stuff breaks after a cargo update
.
The user's issue turned out to be unrelated, but this is just something I noticed while scrutinizing their Cargo.toml
.
https://discord.com/channels/691052431525675048/1261446980001861694
Hello, not a user, but noticed this situation in a Bevy discord help thread.
Users with e.g.
Who run
cargo update
will get version0.1.11
, which is not compatible with Bevy 0.13.The version supporting Bevy 0.14 should have been released as
0.2
.