see also
https://github.com/actions/cache/issues/820Looks like the package servers are having troubles. Apparently a workaround is to use the `cache: npm` parameter for the setup-node action. Won't help when you rely on other actions or docker builds etc.