Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of tslint-plugin-prettier is breaking the build 🚨 #1161

Closed
greenkeeper bot opened this issue Mar 14, 2020 · 1 comment
Closed

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Mar 14, 2020


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency tslint-plugin-prettier was updated from 2.1.0 to 2.2.0.

🚨 View failing branch.

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

tslint-plugin-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).

Commits

The new version differs by 7 commits.

  • a0578cc chore(release): 2.2.0
  • e979ae1 feat: support tslint@6 (#355)
  • 3e07afa chore(deps-dev): bump typescript from 3.1.6 to 3.8.3 (#354)
  • f8c9625 chore(deps-dev): bump @types/prettier from 1.13.2 to 1.19.0 (#353)
  • d7fcbd2 chore(deps-dev): bump prettier from 1.15.2 to 1.19.1 (#307)
  • 7249010 chore(deps-dev): bump codecov from 3.1.0 to 3.6.5 (#341)
  • 6516e1d chore(deps): [security] bump handlebars from 4.1.2 to 4.5.3 (#325)

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
Copy link
Contributor Author

greenkeeper bot commented Mar 14, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant