Building the library using yarn prepare impacts performance of github actions and exposes race conditions. This is because when yarn pulls the library, it runs yarn prepare and spawn many child yarn instances each trying to read and write to the same cache directories. It's never happened before, but it happens now. My guess is that the size of our custom libraries has reached a critical mass.
Building the library using yarn prepare impacts performance of github actions and exposes race conditions. This is because when yarn pulls the library, it runs yarn prepare and spawn many child yarn instances each trying to read and write to the same cache directories. It's never happened before, but it happens now. My guess is that the size of our custom libraries has reached a critical mass.