An in-range update of tslint-config-prettier is breaking the build 🚨

[greenkeeper]

The devDependency tslint-config-prettier was updated from 1.16.0 to 1.17.0.

🚨 View failing branch.

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

tslint-config-prettier 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v1.17.0

1.17.0 (2018-11-27)

Features

• Switch to Yarn instead of npm (537a7ad)

Commits

The new version differs by 19 commits.

• d336552 Merge pull request #238 from lipis/yarn
• 537a7ad feat: Switch to Yarn instead of npm
• 6c38ddc chore(deps-dev): bump semantic-release from 15.12.0 to 15.12.2
• 9c13ec5 chore(deps-dev): bump vrsource-tslint-rules from 5.8.2 to 5.8.3 (#237)
• 2e1fd17 chore(deps-dev): bump tslint-immutable from 4.9.1 to 5.0.0 (#235)
• 7540e0b chore(deps-dev): bump ts-jest from 23.10.4 to 23.10.5 (#233)
• d285f6a Merge pull request #218 from prettier/readme
• c77472a Merge pull request #220 from prettier/dependabot/npm_and_yarn/semantic-release-15.12.0
• 0dc80a1 chore(deps-dev): bump typescript from 3.0.3 to 3.1.6 (#231)
• 168588a chore(deps-dev): bump tslint-misc-rules from 3.5.0 to 3.5.1 (#229)
• c53a625 chore(deps-dev): bump @types/prettier from 1.13.2 to 1.15.1 (#230)
• 4bb4e9b docs(readme): add link to conflicting rules list to README (#228)
• 9d573c6 chore(deps-dev): bump codelyzer from 4.1.0 to 4.5.0 (#225)
• 983bc18 chore: npm audit fix (#224)
• 9bda093 chore(deps-dev): bump semantic-release from 15.1.7 to 15.12.0

There are 19 commits in total.

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 🌴

[greenkeeper]

After pinning to 1.16.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.