# Invalidate Linux build caches more agressively \(\#8031\) · gitcafe/zed

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

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

Visibility: public

Requested revision: 37f6a706cc33fc97e7f1f4511db75dd6d50d1b5b

Requested commit: 37f6a706cc33fc97e7f1f4511db75dd6d50d1b5b

Commit: 37f6a706cc33fc97e7f1f4511db75dd6d50d1b5b

Tree: 48e08e1ca90cfbc50cf6b3d558ba0024a617fa6e

Author: Kirill Bulatov

Committer: GitHub

## Message

```
Invalidate Linux build caches more agressively (#8031)

We run Linux CI on regular GitHub Action runners, which have ~30GB of
disk space. This is nothing for Rust builds and, due to Cargo.lock
perturbations, we tend to accumulate enough artifacts to fill the disk
entirely since `restore-keys` alowed to keep the cache for different
lockfiles.

Instead, try to invalidate the cache more aggressively (which will cost
us more frequent ~30min Linux CI runs) to see how this will work in
comparison.

Release Notes:

- N/A
```

## Parents

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

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