The version 1.0.5 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of @angular/cli.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notesv1.0.5
Bug Fixes
@angular/cli: allow e2e tests to run if no-serve and port is provided (ce54caf)
@angular/cli: fix issue of folder getting generated on dry run (6395129)
@angular/cli: fix leading digit in file names from generate command (0ecaa2d)
@angular/cli: fix package name fetching from package.json (9c83f3b)
@angular/cli: remove broken script after eject (41d8522)
@ngtools/json-schema: only values in enum should be allowed to update (456361d)
@ngtools/webpack: fix aot builds using npm packages that have lazy loaded modules (fd002df), closes #5594
@ngtools/webpack: fix paths-plugin to allow '*' as alias (0f24e04), closes #5033
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 1.0.5 of @angular/cli just got published.
The version 1.0.5 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of @angular/cli. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v1.0.5Bug Fixes
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: