search

pvdlg / karma-postcss-preprocessor

Karma preprocessor to compile css files with postcss with sourcemap and watch support
MIT License
0 stars 0 forks source link

An in-range update of p-event is breaking the build 🚨 #83

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency p-event was updated from 2.2.0 to 2.3.0.

🚨 View failing branch.

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

p-event 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](https://ci.appveyor.com/project/pvdlg/karma-postcss-preprocessor-k43c2/builds/22296517)). - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/pvdlg/karma-postcss-preprocessor/builds/491964182?utm_source=github_status&utm_medium=notification)).
Release Notes for v2.3.0
  • Add limit option to pEvent.iterator() (#16) 8b49e21
  • Make pEvent.iterator() implement return() correctly (#20) 68d745a
  • Add support for multiple event names (#19) db3203f

v2.2.0...v2.3.0

Commits

The new version differs by 5 commits.

  • 0a8c9cb 2.3.0
  • e4badc5 Meta tweaks
  • 8b49e21 Add limit option to pEvent.iterator() (#16)
  • 68d745a Make .iterator() implement return() correctly (#20)
  • db3203f Add support for multiple event names (#19)

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 2.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for v2.3.1
  • Invalid limit option value should throw synchronously 2c13f7c

v2.3.0...v2.3.1

Commits

The new version differs by 2 commits.

  • aea0ca8 2.3.1
  • 2c13f7c Invalid limit option value should throw synchronously

See the full diff