pnpm logs error only to stdout when fails due to strict peer dependencies #14904
Labels
status:requirements
Full requirements are not yet known, so implementation should not be started
type:bug
Bug fix of existing functionality
How are you running Renovate?
WhiteSource Renovate hosted app on github.com
If you're self-hosting Renovate, tell us what version of Renovate you run.
No response
Please select which platform you are using if self-hosting.
No response
If you're self-hosting Renovate, tell us what version of the platform you run.
No response
Was this something which used to work for you, and then stopped?
I never saw this working
Describe the bug
If pnpm is configured with
strict-peer-dependencies = true
(which I hear is going to be the default in pnpm 7), and a package update adds a new peer dependency, renovate fails. That part is expected.What's not expected is that the "artifact update problem" comment is completely unhelpful:
There's no indication that pnpm is what failed, much less why. The message there makes it sounds like npm having a minor update is somehow the problem. I don't know what it would say if npm didn't whine about its update.
The reason can be found by digging into the logs, of course.
Minimal reproduction repo: https://github.com/anomiex/renovate-test-2
Failing update: anomiex/renovate-test-2#6
Relevant debug logs
Logs
Have you created a minimal reproduction repository?
I have linked to a minimal reproduction repository in the bug description
The text was updated successfully, but these errors were encountered: