search

zspecza / common-tags

🔖 Useful template literal tags for dealing with strings in ES2015+
Other
1.99k stars 60 forks source link

An in-range update of micromatch is breaking the build 🚨 #85

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 7 years ago

Version 2.3.11 of micromatch just got published.

Branch Build failing 🚨
Dependency micromatch
Current Version 2.3.10
Type devDependency

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

As micromatch 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 - ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/declandewet/common-tags/build/244) - ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/declandewet/common-tags/builds/181580951) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/declandewet/common-tags/a36b254054db67868a3ee4b1da607b436c68be50/files?status=passing) - ❌ **bitHound - Dependencies** 1 failing dependency. [Details](https://www.bithound.io/github/declandewet/common-tags/a36b254054db67868a3ee4b1da607b436c68be50/dependencies/npm#filter-failing-dep)
Commits

The new version differs by 3 commits .

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:

greenkeeper[bot] commented 7 years ago

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