An in-range update of documentation is breaking the build 🚨

[greenkeeper]

Version 4.0.0 of documentation just got published.

Branch	Build failing 🚨
Dependency	documentation
Current Version	4.0.0-rc.1
Type	devDependency

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

As documentation 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 32 commits.

• b42c0d7 chore: Update lockfile
• 80a06fe chore(release): 4.0.0
• 1ae8136 fix(package): update remark to version 8.0.0
• 5b5dcd1 docs(theming): fix default theme link
• a3e1fb8 fix(package): update vfile-reporter to version 4.0.0
• 4544886 chore(package): update fs-extra to version 4.0.0 (#841)
• 715c714 fix broken link (#842)
• 2329db4 fix(package): update chalk to version 2.0.0 (#833)
• ea69608 fix: Report nesting errors instead of throwing them as errors
• 15239d1 chore: Updated eslint. fixed no-useless-escape rule. (#834)
• 505f62d docs: Add issue template (#831)
• 32ef5a5 docs: Don't end 'getting started' abruptly, instead link to next steps.
• 473f317 fix: Fix filtering in the default theme
• 15bd7af chore(package): update husky to version 0.14.0 (#823)
• 61968c7 fix: Show () for callbacks

There are 32 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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