Update documentation to the latest version 🚀#83
Conversation
Version 5.0.0 just got published. |
Version 5.0.1 just got published. |
Version 5.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 5.1.1 just got published. |
Version 5.2.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 5.2.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 5.2.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 5.3.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
Version 5.3.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 5.3.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 8 commits.
See the full diff |
Version 5.3.3 just got published.Update to this version instead 🚀 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Version 5.3.4 just got published.Update to this version instead 🚀 CommitsThe new version differs by 15 commits.
See the full diff |
Version 5.3.5 just got published. |
Update to this version instead 🚀 CommitsThe new version differs by 13 commits.
See the full diff |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
Version 4.0.0 of documentation just got published.
The version 4.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of documentation.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 32 commits.
b42c0d7chore: Update lockfile80a06fechore(release): 4.0.01ae8136fix(package): update remark to version 8.0.05b5dcd1docs(theming): fix default theme linka3e1fb8fix(package): update vfile-reporter to version 4.0.04544886chore(package): update fs-extra to version 4.0.0 (#841)715c714fix broken link (#842)2329db4fix(package): update chalk to version 2.0.0 (#833)ea69608fix: Report nesting errors instead of throwing them as errors15239d1chore: Updated eslint. fixed no-useless-escape rule. (#834)505f62ddocs: Add issue template (#831)32ef5a5docs: Don't end 'getting started' abruptly, instead link to next steps.473f317fix: Fix filtering in the default theme15bd7afchore(package): update husky to version 0.14.0 (#823)61968c7fix: Show () for callbacksThere 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 🌴