Cargo.lock missing

[Snektron]

The current version seems to lack a Cargo.lock file. Its typical to commit this file to the repository so that everybody who tries to build the project uses the exact same version of dependencies that you do.

I'm missing it because I'm trying to bump Gersemi in NixOS, but in order to build it properly, it needs the lock file.

[BlankSpruce]

I'll see to it soon. I'm new to Rust development so I've thought that versions specified in Cargo.toml are enough.

[Snektron]

Thanks!

I'm new to Rust development so I've thought that versions specified in Cargo.toml are enough.

If you specify something like pyo3 = ">=0.28" cargo may pick any version that satisfies those needs, whether its 0.28.0, 0.29.1, 1.0, etc. That means that as new versions of pyo3 get released, building the project at different points in time would cause different versions to get downloaded. If those versions have API differences, then the project could fail to compile. Cargo.lock pins the exact version so that this doens't happen, and then you can update manually using cargo upgrade. I was confused at first too :)

[BlankSpruce]

I get that part but, since you've mentioned pyo3, I'm not using open ended >= version specification but I pin in Cargo.toml specific minor version with = 0.29. Of course it still allows bumps to patch versions but I've considered that to be an okay solution since patch versions aren't meant for API changes.

Nevertheless, Cargo Book says so, ruff and other useful goodies do that so I'm not going to pretend to be more clever than that.

[BlankSpruce]

I've added Cargo.lock on master branch but due to private circumstances I'm not yet publishing any official tag with new version so until then this issue will stay open. You might check if my changes satisfy build process used in NixOS.

[Snektron]

No problem, thanks for the quick response :)