Cross dependent packages cause subsequent MR fails
📄 Question
Is there an existing issue for this?
-
I have searched the existing issues - Haven't found one looking for keywords: conflict
,resolve
,could not resolve
Question
When Angular releases new versions we got this kind of errors on each MR made by dependabot. This happens for npm i
and npm ci
as well. npm i -f
would work
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @angular/animations@15.2.8
npm ERR! Found: @angular/core@15.2.7
npm ERR! node_modules/@angular/core
npm ERR! @angular/core@"^15.2.7" from the root project
npm ERR! peer @angular/core@"^15.0.0 || ^16.0.0" from @angular/cdk@15.2.7
npm ERR! node_modules/@angular/cdk
npm ERR! @angular/cdk@"^15.2.6" from the root project
npm ERR! peer @angular/cdk@"15.2.7" from @angular/material@15.2.7
npm ERR! node_modules/@angular/material
npm ERR! @angular/material@"^15.2.7" from the root project
npm ERR! 1 more (@angular/material-date-fns-adapter)
npm ERR! 1 more (ngx-scrollbar)
npm ERR! 17 more (@angular/compiler, @angular/forms, @angular/material, ...)
I think I understand the cause - that one package needs another in specific version. But is there a way that dependabot can detect and handle it ? Otherwise We have 6-8 MR and ideally each should be checked out, force installed, run all tests and merged. Or at least all merged to one branch blindly and then tested and merged to master.
Maybe increase-if-necessary
will work?