coveralls
commented
6 years ago Coverage remained the same at 100.0% when pulling 3f97ce02e6bbc5bffa4af22920d77272f7f26047 on greenkeeper/jsdoc-to-markdown-4.0.0 into 38de8a5de01b534bfdebbd3c8eec2c39256652d5 on master.
greenkeeper[bot]
Version 4.0.0 of jsdoc-to-markdown was just published.
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of jsdoc-to-markdown.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v4.0.0Breaking changes since v3.0.4
--htmloption due to lack of use.New features
asyncorawaitstatements natively, without use of a babel plugin.Upgrade notes
Upgrade recommended. There are no API changes in v4.0.0, it is backward compatible. Assuming you don't need
--htmlyou can upgrade safely.Commits
The new version differs by 10 commits.
68bd7254.0.05145291Merge branch 'next'352b360upgrade dmd to fix #145da367e1remove --html option from API docs04cc56eregenerate API Docsbfe74bb3.1.0-167b6123linting.. depsc1d1cf23.1.0-0bde334aupgrade underlying jsdoc to get built-in support for async/await0399ccaupgrade command line parser depsSee the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: