chore(cargo): check in Cargo.lock (#1434)

When kept up to date, this makes it possible to build any git version
with the same versions of crates that were used for any version, without
it, you can only use the current versions. This makes bugs in semver
compatible code difficult to detect.

The Cargo.lock file is not used by downstream consumers of the crate, so
it is safe to include it in the repository (and recommended by the Rust
docs).

See:
- https://doc.rust-lang.org/cargo/faq.html#why-have-cargolock-in-version-control
- https://blog.rust-lang.org/2023/08/29/committing-lockfiles.html
- https://github.com/rust-lang/cargo/issues/8728

Co-authored-by: Orhun Parmaksız <orhun@archlinux.org>
This commit is contained in:
Josh McKinney 2024-10-20 01:59:07 -07:00 committed by GitHub
parent 4c4851ca3d
commit 6515097434
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 3398 additions and 1 deletions

1
.gitignore vendored
View file

@ -1,5 +1,4 @@
target
Cargo.lock
*.log
*.rs.rustfmt
.gdb_history

3398
Cargo.lock generated Normal file

File diff suppressed because it is too large Load diff