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 doctoc is breaking the build 🚨 #83

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 7 years ago

Version 1.2.0 of doctoc just got published.

Branch Build failing 🚨
Dependency doctoc
Current Version 1.1.1
Type devDependency

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

As doctoc 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/240) - ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/declandewet/common-tags/builds/177596387) - ❌ **bitHound - Dependencies** 1 failing dependency. [Details](https://www.bithound.io/github/declandewet/common-tags/c94e03fa3c2d85ad8e24a5a000243e2825461cf4/dependencies/npm#filter-failing-dep) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/declandewet/common-tags/c94e03fa3c2d85ad8e24a5a000243e2825461cf4/files?status=passing)
Commits

The new version differs by 5 commits .

  • a376096 1.2.0
  • 9603fa2 doc: updating TOC in Readme with extra option
  • bb4f414 Added option for stdout
  • eab6f48 Peg anchor-markdown-header to ^0.5.5 (#110)
  • ec0157b Adds --entryprefix flag to use '*' instead of '-'

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

greenkeeper[bot] commented 7 years ago

Version 1.3.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 3 commits .

  • b96694f 1.3.0
  • c3aa65f Set dependencies version with "~" as @thlorenz requested
  • 37bbee2 Bump npm dependencies (npm test passed!)

See the full diff.