CAAPIM / themer

Framework agnostic utility to make generic JavaScript components themeable and extensible.
MIT License
1 stars 1 forks source link

An in-range update of eslint-config-ca is breaking the build 🚨 #27

Open greenkeeper[bot] opened 7 years ago

greenkeeper[bot] commented 7 years ago

Version 2.0.1 of eslint-config-ca just got published.

Branch Build failing 🚨
Dependency eslint-config-ca
Current Version 2.0.0
Type devDependency

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

As eslint-config-ca is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:


Status Details - ❌ **clahub** Not all contributors have signed the Contributor License Agreement. [Details](http://www.clahub.com/agreements/CAAPIM/themer) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/CAAPIM/themer/builds/219973304)
Release Notes v2.0.1

<a name"2.0.1">

2.0.1 (2017-04-07)

Bug Fixes

  • remove require-default-props rule in favour of Flowtype (cc4a79d1)
Commits

The new version differs by 5 commits .

  • 98c3653 Merge pull request #14 from CAAPIM/require-default-props
  • cc4a79d fix: remove require-default-props rule in favour of Flowtype
  • 9e5b3ce Merge pull request #12 from CAAPIM/greenkeeper/initial
  • a676eee docs(readme): add Greenkeeper badge
  • e8b124e chore(travis): whitelist greenkeeper branches

See the full diff.

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree: