Closed Reinmar closed 11 months ago
One thing that may make this a bad option is the amount of noise that we'll have. A single Webpack update may cause 30 new PRs.
Perhaps we could enable it for ckeditor5 only, because it has pretty much all the deps we use so once something changes in ckeditor5 we'll know that we need to change other packages too (which is ok with mgit).
I'm also curious how will it work in ckeditor5-dev with that multi-package repo.
I'm also curious how will it work in ckeditor5-dev with that multi-package repo.
It won't. ATM it would only update top-level packages.
There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.
We've closed your issue due to inactivity over the last year. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it).
https://greenkeeper.io
Manually managing dependencies of our packages requires some good time and it's yet another thing we need to remember.
Therefore, we may try automating it with a tool like Greenkeeper.