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

[greenkeeper]

The devDependency jasmine-core was updated from 3.4.0 to 3.5.0.

🚨 View failing branch.

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

jasmine-core 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 117 commits.

• 99799f7 Still need some ruby stuff around to release the jasmine-core gem
• e8263e3 bump version to 3.5.0
• 53561ae Show details of syntax (etc) errors when loading Jasmine's own specs
• 68f25a7 Don't create env instances in beforeEach
• 96ba66a Built distribution
• ba4a8d1 Fixed jsdocs
• 65d9e93 Removed broken & long-disabled JsApiReporter integration specs
• 2d3ac38 toBeRejectedWithError can expect the error to be Error, not just a subtype
• 5a219da Added basic integration tests for all built-in matchers
• f056f3b Fixed indentation
• aeb0b73 Merge branch 'dtychshenko-1740-fail-on-no-expectations'
• 7263a38 Adds new configuration option to failSpecWithNoExpectations that will report specs without expectations as failures if enabled
• e8870db Merge branch 'fix-missing-asynchronous-stacktrace' of https://github.com/prantlf/jasmine into prantlf-fix-missing-asynchronous-stacktrace
• 35d1508 Show argument diffs in toHaveBeenCalledWith failure messages
• 19292e4 Stop testing against PhantomJS

There are 117 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 3.4.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.