The Cargo.lock format is changing over time (and is practically guaranteed to continue changing) and the most recent change has brought up ideas again about possibly encoding a version number into Cargo.lock. There's a number of comments on that thread weighing some pros and cons (including this one).
One possible way to implement this would be to add a field to the [metadata] table. Every version of Cargo ever preserves the [metadata] table, and so we can add a version number in there practically any time and have it preserved by older Cargo while recognized by newer Cargo.
The
Cargo.lockformat is changing over time (and is practically guaranteed to continue changing) and the most recent change has brought up ideas again about possibly encoding a version number intoCargo.lock. There's a number of comments on that thread weighing some pros and cons (including this one).One possible way to implement this would be to add a field to the
[metadata]table. Every version of Cargo ever preserves the[metadata]table, and so we can add a version number in there practically any time and have it preserved by older Cargo while recognized by newer Cargo.