# Add a CI check that Cargo.lock is up to date \(\#35111\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/bf8e4272bcbaf7225922ecea20c7ec60e356447b)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: bf8e4272bcbaf7225922ecea20c7ec60e356447b

Requested commit: bf8e4272bcbaf7225922ecea20c7ec60e356447b

Commit: bf8e4272bcbaf7225922ecea20c7ec60e356447b

Tree: a9da735db1b95fc1c2d0557ade534e166352822a

Author: Cole Miller

Committer: GitHub

## Message

```
Add a CI check that Cargo.lock is up to date (#35111)

Should catch cases like #33667 where a dependency was bumped in
Cargo.toml without a corresponding lockfile update. (This can happen
when committing from outside of Zed or if rust-analyzer isn't running.)
Passing `--frozen --workspace` should ensure this doesn't fail just
because there's a newer patch version of some third-party dependency,
and prevent it from taking long.

We only need to run this on macOS because Cargo.lock is
platform-independent.

Release Notes:

- N/A
```

## Parents

- [f787f7d2913e99238c020f2e875ea6c87e4bfe3b](https://git.cafe/gitcafe/zed/commit/f787f7d2913e99238c020f2e875ea6c87e4bfe3b?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/bf8e4272bcbaf7225922ecea20c7ec60e356447b?format=markdown)