Renovate refuses to update angular monorepo from v21.2.7 to v21.2.9 #42734
Replies: 1 comment
-
|
Well, Renovate has successfully updated the angular monorepo to a version later than v21.2.9 now. So I think this discussion can be closed. It isn't relevant any longer. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
A Mend.io-hosted app
Which platform you running Renovate on?
GitHub.com
Which version of Renovate are you using?
43.123.8
Please tell us more about your question or problem
There is a pending update for the
angularmonorepo, from v21.2.7 to v21.2.9. I can see it on the Renovate Dependency Dashboard for my project, both the GitHub.com issue and the Dashboard visible on thedeveloper.mend.iowebsite. But this particular update keeps showing up either under Rate-Limited Updates or under Other Updates. I have tried repeatedly to force Renovate to actually create the Pull Request by checking the appropriate checkbox and (ondeveloper.mend.io) clickingCreate/Rebase. But no luck. The update PR never actually gets created.At first, it was hitting a rate limit of 2 PRs per hour maximum. Now it's past that, and hitting a different problem. npm is spitting out a bunch of errors about conflicting peer dependencies. I don't understand why that's happening. Normally Renovate handles the angular-monorepo very intelligently, and doesn't have any trouble, except on major version upgrades.
See log excerpt below for the npm error messages.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions