You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using the latest version which was running the lock file at version 4, and a quick look shows yours is on version 3, the fix was downgrading the version on my end.
Just to make it easier on everyone I think it would be better if it was updated on your build end instead of every user having to do so.
Logs:
remote: [build] > lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?
remote: [build] Error: process "/bin/sh -c cargo build --release --target-dir=/tmp/codecrafters-git-target" did not complete successfully: exit code: 101.
remote: [build] > error: failed to parse lock file at: /app/Cargo.lock
remote: [build] >
remote: [build] > Caused by:
remote: [build] > lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?
remote: [build] Build failed. Check the logs above for the reason.
The text was updated successfully, but these errors were encountered:
ziggybaz
changed the title
Cargo lock file version
Cargo lock file version (RUST)
Dec 1, 2024
Rare case though, only happened because I had to rm the Cargo.lock file provided while tinkering and therefore recompiled with a new build, obviously if I had kept the original wouldn't have encountered the problem.
Kindly update rustup to the latest version.
I was using the latest version which was running the lock file at version 4, and a quick look shows yours is on version 3, the fix was downgrading the version on my end.
Just to make it easier on everyone I think it would be better if it was updated on your build end instead of every user having to do so.
Logs:
The text was updated successfully, but these errors were encountered: