search

ecomfe / fecs

Front End Code Style Suite
http://fecs.baidu.com/
643 stars 115 forks source link

An in-range update of csscomb is breaking the build 🚨 #348

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency csscomb was updated from 4.2.0 to 4.3.0.

🚨 View failing branch.

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

csscomb is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build is in progress ([Details](https://travis-ci.org/ecomfe/fecs/builds/521576126?utm_source=github_status&utm_medium=notification)). - ❌ **continuous-integration/appveyor/branch:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/chriswong/fecs/builds/23938785)).
Commits

The new version differs by 17 commits.

  • 5c69a07 v4.3.0
  • 842e9f9 Fix sort-order-fallback keep order
  • db0946f Perform npm audit fix
  • 08afce5 Update package-lock
  • d7f40ee Fix line-between broking when file start with comment
  • 38cd55e Fix sort-order test
  • 565a16f Update versions of dependencies
  • 3e029fc Fix ast.remove is not a function error
  • 55d58f4 Duplicate #576 without dependencies
  • 15a5459 Update list of support Node versions
  • db14fce Update GPE version
  • 19b9799 [cli] TTY-option type set to boolean
  • adcfc01 Ignore leading combinators
  • 269e854 Merge pull request #531 from romanlex/patch-1
  • 9b31811 Merge pull request #541 from Yurickh/fix-contributing-guide-markdown

There are 17 commits in total.

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