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 jasmine-core is breaking the build 🚨 #131

Closed
greenkeeper bot opened this issue Apr 4, 2019 · 2 comments
Closed

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

greenkeeper bot opened this issue Apr 4, 2019 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Apr 4, 2019

The devDependency jasmine-core was updated from 3.3.0 to 3.4.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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 40 commits.

  • 8fca3b4 Fix links in 3.4 release notes
  • e636f5f Bump version to 3.4
  • 74fd0e0 No fit in the suite
  • 618e24b Handle WebSocket events in IE when detecting Errors
  • 5c7e25e Allow excluded specs in CI without breaking the output
  • 54af109 Merge branch 'wood1986-fix/npm-audit-dependencies-and-fast-glob-only-failed-tests'
  • 873a237 Consolidate some dev dependencies and use more maintained versions
  • 8ca4463 Make node execution default and override for browsers
  • 449eb51 Fix sauce status codes and try travis built-in node support
  • a5df5a6 Use the correct env var from travis for tunnels
  • be58323 bump dependencies for security fixes
  • d389d3c Merge branch 'wood1986-features/no-ruby'
  • 994d11d update node CI script to work with SauceLabs
  • 828d14f Use node.js for browser-based CI
  • f5663a9 Merge branch 'johnjbarton-duration'

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

greenkeeper bot commented Apr 4, 2019

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 21, 2019

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

Your tests are still failing with this version. Compare changes

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

@pvdlg pvdlg closed this as completed Oct 18, 2019
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