basics / blueprint-npm-module

MIT License
0 stars 0 forks source link

An in-range update of rollup-plugin-babel-minify is breaking the build 🚨 #32

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency rollup-plugin-babel-minify was updated from 9.1.0 to 9.1.1.

🚨 View failing branch.

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

rollup-plugin-babel-minify 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 is in progress ([Details](https://travis-ci.org/basics/blueprint-npm-module/builds/609980635?utm_source=github_status&utm_medium=notification)). - ❌ **continuous-integration/appveyor/branch:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/StephanGerbeth/blueprint-npm-module/builds/28750755)).

Commits

The new version differs by 13 commits.

  • b9ad5ca chore(dist): clean after release [ci skip]
  • 90ca409 9.1.1
  • 5da10bd Merge pull request #195 from Comandeer/t/193
  • 53f012d docs(changelog): add entry
  • fa758d6 chore(package): update dependencies
  • 3875d42 Setup GHA (#192)
  • 228b5d1 docs(readme): replace Travis badge with GHA one
  • 34abf03 chore(package): force update of deep deps
  • 86977b6 chore(package): update dependencies
  • 377ceff ci(travis): disable
  • 72776d8 ci(gha): add config
  • 6ddaf14 chore(docs): rebuild & ensure that .nojekyll is always there
  • 398bbcb chore(docs): switch off Jeykll

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 5 years ago

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