search

latticework / jali

Semantics-driven serverless microservice DevOps framework and infrastructure
http://jali-ms.io/
MIT License
1 stars 1 forks source link

An in-range update of babel-plugin-espower is breaking the build 🚨 #176

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 2.4.0 of babel-plugin-espower was just published.

Branch Build failing 🚨
Dependency babel-plugin-espower
Current Version 2.3.2
Type devDependency

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

babel-plugin-espower 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 - ✅ **dependency-ci** Dependencies checked [Details](https://dependencyci.com/builds/389258) - ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/latticework/jali/branches/greenkeeper-babel-plugin-espower-2-4-0/builds/1)
Commits

The new version differs by 6 commits.

  • bf0ffe9 2.4.0
  • 4aba0a9 docs(CHANGELOG): add CHANGELOG for 2.4.0
  • 968f828 chore(travis): update Node version matrix
  • 658c90d Merge pull request #25 from power-assert-js/with-experimental-syntax
  • c840ac1 feat: bridge module for babel-preset-power-assert to enable embedAst option by default
  • 5bda37d test: update expected output

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 Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

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