let RenovateBot manage all depdendencies #449
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RenovateBot was configured to ignore the dependencies, which are part of the default blueprint for Ember applications. Motivation was to update the Ember version, the blueprints and all default dependencies in one go.
Ember has gotten more flexible to support different combinations of dependency versions. Especially the latest versions are often working well together with recent versions of other dependencies.
In contrast updating all dependencies in a single step has been proven to be more difficult. E.g. we currently need to lock
ember-data
to an old version but can use latest versions ofember-source
andember-cli
. Updating that two (and most of the other dependencies) do not require any change. Buteslint-plugin-ember
may introduce new rules in its recommended set, which require some refactoring. It's easier to handle all of that in small, independent tasks rather than in one big change.Also Ember CLI Update was improved so that even
ember-cli
package and blueprints can be upgraded independently.Long story short: I don't see any reason anymore to not manage all dependencies by RenovateBot.