Version 7.0.13 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.12
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.0.2 of @angular/platform-browser just got published.

Branch	Build failing 🚨
Dependency	@angular/platform-browser
Current Version	4.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/platform-browser is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.2.2 of @angular/platform-browser just got published.

Branch	Build failing 🚨
Dependency	@angular/platform-browser
Current Version	4.2.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

@angular/platform-browser is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
• ✅ codecov/patch Coverage not affected when comparing 4da4d8c...c760dbf Details
• ❌ codecov/project 90.74% (-0.52%) compared to 4da4d8c Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 5.1.2 of protractor just got published.

Branch	Build failing 🚨
Dependency	protractor
Current Version	5.1.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As protractor is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 35 commits0.

• ea72d55 chore(release): version bump and changelog for 5.1.2
• a0a1fac chore(deps): Updating webdriver-manager and jasminewd2
• 1a47076 fix(ci): Use latest pip on CircleCI
• fd59c78 fix(elementexplorer): Set script breakpoints with cross-platform safe
• 42846ec docs(asyncAwait): fix link in asyncAwait/README.md
• 8bb0874 docs(developers): add fixes and links to api-overview.md
• 2fbf993 chore(ci): Upgrade typescript in install test.
• d0bfa6e chore(ci): Fix Circle CI.
• 5cba564 chore(deps): Update typescript to fix tsc error.
• 160a04b docs(phantomjs): Add deprecation notice for PhantomJS
• 1250278 fix(cli): Correctly parse list chromeOptions
• a655d45 Updated documentation for ignoreSynchronization
• dd2ccbb feat(saucelabs): Add Sauce Labs protocol customization support
• 183cd80 fix(browser): Fix browser.angularAppRoot()
• aaba0f6 docs: fixed dead pre-requisites link & added link to release.md

There are 35 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.0.2 of @angular/forms just got published.

Branch	Build failing 🚨
Dependency	@angular/forms
Current Version	4.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/forms is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.0.2 of @angular/compiler-cli just got published.

Branch	Build failing 🚨
Dependency	@angular/compiler-cli
Current Version	4.0.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/compiler-cli is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

The devDependency codecov was updated from 3.6.4 to 3.6.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

codecov is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ ci/circleci: build: Your tests failed on CircleCI (Details).

---

Commits

The new version differs by 2 commits.

• ebe132e 3.6.5
• 02cf13d [CE-1330] Escaping args (#167)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Version 4.0.2 of @angular/compiler just got published.

Branch	Build failing 🚨
Dependency	@angular/compiler
Current Version	4.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/compiler is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 2.6.3 of jasmine-core just got published.

Branch	Build failing 🚨
Dependency	jasmine-core
Current Version	2.6.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As jasmine-core is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
• ❌ codecov/project 87.19% (-0.7%) compared to 2055686 Details
• ✅ codecov/patch Coverage not affected when comparing 2055686...92a97f9 Details

---

Release Notes

2.6.3

Please see the release notes

Commits

The new version differs by 2 commits.

• ca5b1de bump version to 2.6.3
• a3bc747 Make sure the queue runner goes async for async specs

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.0.1 of @angular/common just got published.

Branch	Build failing 🚨
Dependency	@angular/common
Current Version	4.0.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/common is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

• ✅ codecov/patch Coverage not affected when comparing bb6cebf...f662dac Details

• ❌ codecov/project 87.88% (-0.7%) compared to bb6cebf Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

The dependency ngx-bootstrap was updated from 3.0.1 to 3.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ngx-bootstrap is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ ci/circleci: build: Your tests failed on CircleCI (Details).

---

Release Notes for v3.1.1

• 3.1.1 (17a3eba)
• chore(changelog): update [skip ci] (8f71cc8)
• feat(docs): update docs according to ng add feature (#4703) (b51c21f), closes #4703

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

The devDependency karma-jasmine-html-reporter was updated from 1.3.1 to 1.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

karma-jasmine-html-reporter is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ ci/circleci: build: Your tests failed on CircleCI (Details).

---

Commits

The new version differs by 1 commits.

• baa99b5 Upgrade to Jasmine 3.3

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Version 4.0.2 of @angular/platform-browser-dynamic just got published.

Branch	Build failing 🚨
Dependency	@angular/platform-browser-dynamic
Current Version	4.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/platform-browser-dynamic is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

The dependency chart.js was updated from 2.9.0 to 2.9.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

chart.js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ ci/circleci: build: Your tests failed on CircleCI (Details).

---

Release Notes for v2.9.1

Bug Fixes

• #6603 Fix deprecation warnings for horizontal bar charts
• #6608 Fix zoom plugin by no longer clipping scale.getDecimalForPixel to the chart area
• #6617 Non numeric Y axes did not work

Documentation

• #6613 Add link to performance documentation

Development

• #6609 - Tests no longer use deprecated options

Thanks to the maintainers and collaborators for their help to improve and test Chart.js (@nagix, @kurkle, @benmccann, @etimberg and @simonbrunel).

Commits

The new version differs by 2 commits ahead by 2, behind by 1.

• f1d12dc Release 2.9.1
• a92dd7b Release v2.9.1 (#6618)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Version 4.2.2 of @angular/forms just got published.

Branch	Build failing 🚨
Dependency	@angular/forms
Current Version	4.2.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

@angular/forms is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
• ❌ codecov/project 90.74% (-0.52%) compared to 4da4d8c Details
• ✅ codecov/patch Coverage not affected when comparing 4da4d8c...a8ca679 Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Complete the readme indicating:

• how to obtain and install
• simple instructions on usage with pointer to angular-cli
• the basic layout of the project
• any other info

Version 4.0.2 of @angular/core just got published.

Branch	Build failing 🚨
Dependency	@angular/core
Current Version	4.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/core is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

The dependency jquery was updated from 3.3.1 to 3.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

jquery is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ ci/circleci: build: Your tests failed on CircleCI (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Version 4.0.2 of @angular/router just got published.

Branch	Build failing 🚨
Dependency	@angular/router
Current Version	4.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/router is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 1.3.0 of karma-coverage-istanbul-reporter just got published.

Branch	Build failing 🚨
Dependency	karma-coverage-istanbul-reporter
Current Version	1.2.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As karma-coverage-istanbul-reporter is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
• ❌ codecov/project 87.19% (-0.7%) compared to b5a16c4 Details
• ✅ codecov/patch Coverage not affected when comparing b5a16c4...33f09c6 Details

---

Commits

The new version differs by 5 commits.

• e419a63 chore(release): 1.3.0
• 4f534c0 chore: fix reporter on node 4
• 1a894f0 feat(thresholds): allow overriding per file thresholds
• 2de647c feat(thresholds): allow threshold logs not to be emitted as errors
• bc957a1 chore: upgrade dependencies

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.0.1 of @angular/forms just got published.

Branch	Build failing 🚨
Dependency	@angular/forms
Current Version	4.0.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/forms is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

• ✅ codecov/patch Coverage not affected when comparing bb6cebf...c4b127f Details

• ❌ codecov/project 87.88% (-0.7%) compared to bb6cebf Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 0.8.5 of zone.js just got published.

Branch	Build failing 🚨
Dependency	zone.js
Current Version	0.8.4
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As zone.js is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

• ❌ codecov/project 88.19% (-0.7%) compared to b341399 Details

• ✅ codecov/patch Coverage not affected when comparing b341399...0fe3364 Details

Commits

The new version differs by 8 commits .

• e11d9ff chore: release v0.8.5
• 291d5a0 fix(REVERT): remove zone internal stack frames in error.stack (#632) (#690)
• 61aee2e feat(dom): fix #664, patch window,document,SVGElement onProperties (#687)
• 5635ac0 fix(jasmine): modify jasmine test ifEnvSupports message (#689)
• 5c4e24d fix(event): fix #667, eventHandler should return result (#682)
• 81297ee fix: add support for subclassing of Errors
• 6010557 fix: improve long-stack-trace stack format detection
• eeaab91 fix: remove left over console.log

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

The dependency ng2-charts was updated from 2.2.3 to 2.2.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ng2-charts is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ ci/circleci: build: Your tests failed on CircleCI (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

The dependency ngx-bootstrap was updated from 4.3.0 to 4.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ngx-bootstrap is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ ci/circleci: build: Your tests failed on CircleCI (Details).

---

Release Notes for v4.2.0

• 4.2.0 (910b1c3)
• chore(changelog): update [skip ci] (3302c21)
• fix(tests): remove deprecated Init event (closes #5005) (#5182) (3f87b84), closes #5005 #5182

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Version 2.2.2 of typescript just got published.

Branch	Build failing 🚨
Dependency	typescript
Current Version	2.2.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

• ✅ codecov/patch Coverage not affected when comparing b341399...5a834ed Details

• ❌ codecov/project 88.19% (-0.7%) compared to b341399 Details

Release Notes

TypeScript 2.2.2

This release include a set of bug fixes reported against TypeScript 2.2.1. For the complete list of fixed issues, check out the fixed issues query for TypeScript 2.2.2.

Download:

• npm
• Visual Studio 2015 plugin
• NuGet package

Commits

The new version differs by 6 commits .

• d89553f Update LKG
• 7ea8d9f Fix Per Request Cancellation Tokens
• 8f41444 send error if obtaining of types-registry package failed (#14573) (#14585)
• 6e8c44f Ports #14566 to release-2.2 (#14571)
• f6b1738 Update LKG
• e440dbb Update version

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 1.1.0 of karma-coverage-istanbul-reporter just got published.

Branch	Build failing 🚨
Dependency	karma-coverage-istanbul-reporter
Current Version	1.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As karma-coverage-istanbul-reporter is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits .

• ddc1777 1.1.0
• d9cec03 Upgrade tslint
• cf6a042 yarn upgrade
• c2989ee Add the skipFilesWithNoCoverage option
• db2dd3e Explicit upgrade of istanbul-api
• 0c409a8 Add yarn.lock

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.0.2 of @angular/common just got published.

Branch	Build failing 🚨
Dependency	@angular/common
Current Version	4.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/common is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 5.3.1 of rxjs just got published.

Branch	Build failing 🚨
Dependency	rxjs
Current Version	5.3.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

rxjs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/DouglasWebster/angular-cli-sb2-bs4/builds/228108437?utm_source=github_status&utm_medium=notification)

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.0.2 of @angular/http just got published.

Branch	Build failing 🚨
Dependency	@angular/http
Current Version	4.0.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/http is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 2.2.0 of codecov just got published.

Branch	Build failing 🚨
Dependency	codecov
Current Version	2.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As codecov is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v2.2.0

Added: Support for Jenkins Blue Ocean
Added: Clear function to remove all discovered reports after uploading
Fix for Gitlab CI

Commits

The new version differs by 8 commits0.

• 7f8a29b v2.2.0
• 576b9fe add CI_REPOSITORY_URL to gitlab detection, fix #60
• 74a44f2 added -C to unlink reports after uploading
• d1bf5e4 Merge pull request #56 from rochdev/blue-ocean
• 0a3cea3 Add support for Jenkins Blue Ocean
• b365cd8 Merge pull request #57 from codecov/fix/cleanup
• 7f220cc Removing old execSync code from tests
• 4ba4609 v2.1.0

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 7.0.10 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.9
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

• ❌ codecov/project 88.19% (-0.7%) compared to b341399 Details

• ✅ codecov/patch Coverage not affected when comparing b341399...807d1d9 Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.0.1 of @angular/compiler-cli just got published.

Branch	Build failing 🚨
Dependency	@angular/compiler-cli
Current Version	4.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/compiler-cli is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

• ❌ codecov/project 87.19% (-1.39%) compared to bb6cebf Details

• ✅ codecov/patch Coverage not affected when comparing bb6cebf...4a07961 Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 7.0.22 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.21
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
• ❌ codecov/project 86.5% (-1.39%) compared to b5a16c4 Details
• ✅ codecov/patch Coverage not affected when comparing b5a16c4...343bc99 Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 3.0.3 of ts-node just got published.

Branch	Build failing 🚨
Dependency	ts-node
Current Version	3.0.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As ts-node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/DouglasWebster/angular-cli-sb2-bs4/builds/228513193?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 6 commits0.

• 1856f71 3.0.3
• 491ce93 Delete config options after TypeScript parse (#321)
• f3ce9a5 Add Greenkeeper badge 🌴 (#316)
• c18692a Update Travis CI build matrix (#303)
• 8e3c7e5 Update TSLint
• 8146c91 Add info about tsconfig-paths to readme (#295)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 4.0.1 of @angular/compiler just got published.

Branch	Build failing 🚨
Dependency	@angular/compiler
Current Version	4.0.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As @angular/compiler is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

• ✅ codecov/patch Coverage not affected when comparing bb6cebf...eed3c25 Details

• ❌ codecov/project 87.88% (-0.7%) compared to bb6cebf Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴