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 gulp-tslint is breaking the build 🚨 #45

Closed
greenkeeper bot opened this issue Feb 21, 2019 · 1 comment
Closed

An in-range update of gulp-tslint is breaking the build 🚨 #45

greenkeeper bot opened this issue Feb 21, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Feb 21, 2019

The devDependency gulp-tslint was updated from 8.1.3 to 8.1.4.

🚨 View failing branch.

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

gulp-tslint 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/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 8 commits.

  • bdea3ff Release 8.1.4
  • b424288 Update dependencies.
  • 316e799 Merge pull request #150 from ebugusey/fix/plugin-return-type
  • a95aa30 Fix plugin return type
  • 2000237 Merge pull request #149 from hekyofficial/code-example-fix
  • aa76d7a code example fix
  • a50569c Merge pull request #146 from Silic0nS0ldier/master
  • 54bba37 Moved to ansi-colors. Lighter than chalk and common dep in Gulp v4.

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 Feb 22, 2019

After pinning to 8.1.3 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