The yarn-cache directory will grow infinitely big if it is restored every run and never cleared. A large cache will slow down builds, and might lead to increased storage costs. GitHub also offers no way to manually purge the cache, so there is no manual workaround either.

I choose weekly since I figured it's long enough have cache hits for most builds, but not too long for the cache to grow gigantic.