maple3142 / maple3142/mapleutil

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

Open
#8 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

greenkeeper
Dominant language
JavaScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## The devDependency [karma](https://github.com/karma-runner/karma) was updated from `3.1.1` to `3.1.2`.

🚨 [View failing branch](https://github.com/maple3142/mapleutil/compare/master...maple3142:greenkeeper%2Fkarma-3.1.2).

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

karma 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](https://travis-ci.org/maple3142/mapleutil/builds/462225077?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v3.1.2

Bug Fixes



Features


Commits

The new version differs by 11 commits.



  • 7d4d347 chore: release v3.1.2

  • 5077c18 chore: update contributors

  • fb05fb1 fix(server): use flatted for json.stringify (#3220)

  • 2682bff feat(docs): callout the key debug strategies. (#3219)

  • 4e87902 fix(changelog): remove release which does not exist (#3214)

  • 30ff73b fix(browser): report errors to console during singleRun=false (#3209)

  • 5334d1a fix(file-list): do not preprocess up-to-date files (#3196)

  • dc5f5de fix(deps): upgrade sinon-chai 2.x -> 3.x (#3207)

  • d38f344 fix(package): bump lodash version (#3203)

  • ffb41f9 refactor(browser): log state transitions in debug (#3202)

  • 240209f fix(dep): Bump useragent to fix HeadlessChrome version (#3201)


See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the project's karma devDependency and reproduce the failure from the Greenkeeper failing branch or Travis CI build 462225077. Compare the build behavior between karma 3.1.1 and 3.1.2, then verify that the project build and tests pass with the resolved dependency state.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.