davesag/ir-api

An in-range update of @stryker-mutator/javascript-mutator is breaking the build 🚨

Closed this issue · 1 comments

greenkeeper commented

The devDependency @stryker-mutator/javascript-mutator was updated from 2.4.0 to 2.5.0.

🚨 View failing branch.

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

@stryker-mutator/javascript-mutator 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
  • ❌ ci/circleci: build: Your tests failed on CircleCI (Details).
Commits

The new version differs by 41 commits.

  • 4324efe v2.5.0
  • 9f591f2 build(deps-dev): force sinon-chai version (#1960)
  • 2074653 build(deps-dev): Bump eslint-plugin-import from 2.19.1 to 2.20.0
  • ca9ae3f build(deps): Bump commander from 4.0.1 to 4.1.0 (#1954)
  • 6254582 build(deps-dev): Bump @types/node from 10.11.7 to 10.17.13
  • 665937d build(deps-dev): Bump install-local from 1.0.0 to 2.0.0 (#1940)
  • e5bda9c build(deps): Bump typed-rest-client from 1.5.0 to 1.7.1 (#1929)
  • b287bde build(deps-dev): Bump karma-jasmine from 2.0.1 to 3.0.1 (#1953)
  • 59b59fb build(deps-dev): Bump @typescript-eslint/eslint-plugin
  • 5dce38a build(deps-dev): Bump @typescript-eslint/parser from 2.14.0 to 2.15.0
  • a690a8a build(deps-dev): Bump @typescript-eslint/parser from 2.13.0 to 2.14.0
  • 6e15cf1 build(deps-dev): Bump eslint-config-prettier from 6.8.0 to 6.9.0
  • 5927a4c build(deps-dev): Bump eslint-config-prettier from 6.7.0 to 6.8.0
  • c1daa87 build(deps-dev): Bump @typescript-eslint/parser from 2.12.0 to 2.13.0
  • 4f6b1e4 build(deps-dev): Bump @typescript-eslint/eslint-plugin

There are 41 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 commented

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