Yarn failing #25836
-
How are you running Renovate?Self-hosted If you're self-hosting Renovate, tell us what version of Renovate you run.using the renovate/renovate:37-full container If you're self-hosting Renovate, select which platform you are using.github.com Was this something which used to work for you, and then stopped?I never saw this working Wanted end result.I'm running into an issue in a repo using yarn to manage dependencies. Renovate is correctly identifying that yarn needs to be called to update lockfiles after Renovate updates a This shows in the debug logs, but Renovate appears to be getting to the "fetch step" in the yarn update and then the yarn process exits 1? However, if I run the same steps locally, yarn completes cleanly What you tried so far.I've pulled the same container that renovate is running in and ran the same Relevant debug logsLogs
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
It's indicating that the child process exited with a non zero exit code but not why. It's doesn't seem to be due to a timeout |
Beta Was this translation helpful? Give feedback.
-
it's probably related to the npmjs registry outages today |
Beta Was this translation helpful? Give feedback.
it's probably related to the npmjs registry outages today