An in-range update of jasmine is breaking the build 🚨

[greenkeeper]

Version 2.7.0 of jasmine just got published.

Branch	Build failing 🚨
Dependency	jasmine
Current Version	2.6.0
Type	devDependency

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

As jasmine 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 is in progress Details
• ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

---

Release Notes

2.7.0

Please see the release notes.

Commits

The new version differs by 5 commits.

• 9503fb3 bump version to 2.7.0
• 86dde9b Merge branch 'seed-reporting' of https://github.com/sgravrock/jasmine-npm into sgravrock-seed-reporting
• 418ecbd Merge branch 'donmccurdy-patch-1'
• 67f151a Fix linebreak between jasmine config examples.
• bc71117 Report the random seed at the beginning and end of execution

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 🌴

[greenkeeper]

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

[greenkeeper]

Version 2.8.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

2.8.0

Please see the release notes.

Commits

The new version differs by 2 commits.

• a24f6ea bump version to 2.8.0
• 7ccbf71 Update readme with docs link and copyright year

See the full diff