by staz on 6/13/22, 9:19 AM with 2 comments
by staz on 6/13/22, 9:21 AM
by krautsourced on 6/13/22, 9:40 AM
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.