canjs/can-compile

An in-range update of grunt-contrib-jshint is breaking the build 🚨

Opened this issue Β· 2 comments

The devDependency grunt-contrib-jshint was updated from 1.1.0 to 2.0.0.

🚨 View failing branch.

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

grunt-contrib-jshint 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 failed (Details).

Commits

The new version differs by 9 commits.

  • 2fce871 v2.0.0.
  • d9212b7 Document reporterOutputRelative option (#268)
  • d4fe674 Merge pull request #283 from gruntjs/dev
  • 35036cc Update deps, use https, fix failing test.
  • f1114ed Update mgol's name in AUTHORS, add .mailmap (#276)
  • 39daf69 Removing reference to dead jslinterrors.com site (#279)
  • debd964 v1.2.0 (#281)
  • 1f3519f Update deps (#280)
  • 2d237ee updated package grunt-contrib-internal from 1.1.0 to 1.2.3 (#273)

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 🌴

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

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 5 commits.

  • cfd9ade Merge pull request #290 from gruntjs/ver
  • 12045c1 v2.1.0
  • ed6586e Merge pull request #289 from gruntjs/deps
  • 7e529b4 Update deps
  • ed84ab8 Merge pull request #285 from gruntjs/v2.0.0

See the full diff