Cargo.lock must be updated too for version

[lfdominguez]

Description

In rust when you change the version of the app, the Cargo.lock file must be changed too.

Possible Solution

Using the same toml parser, must change the package->name = <same that Cargo.toml>->version

Additional context

No response

Additional context

No response

[marcusalstrom]

Is the issue that the Cargo.lock file is not being changed at all or is the issue that Cargo.lock is not being added to the commit?

[woile]

The Cargo.lock is not being changed at all.

[marcusalstrom]

I attempted to reproduce this in my Rust project. After creating a commit with cz commit, I executed cz bump to update the version, and both the Cargo.toml and Cargo.lock files correctly reflected the version change.
How exactly can I reproduce this bug?

[woile]

Normally if your editor is running, it will pick up changes to the folder, and run cargo commands which automatically update the .lock. That's why if you update the Cargo.toml manually, you will see it in the .lock.

Fixing this is actually a bit hard because of workspaces, and because you can define workspaces with globs, and exclude like:

[workspace]
members = ["crates/*"]
exclude = ["crates/foo"]

so you'd have to use glob.glob from python to include, and then exclude those matching the exclude, and afterwards filter from all the found crates those with version = { workspace = true }, and finally, the resulting crates should be updated on the .lock