Seen several people report that GitHub actions are failing because the caching service return 503. Github status still report that everything is normal
Looks 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.
2 comments
[ 3.5 ms ] story [ 9.3 ms ] threadLooks 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.