The version 1.1.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 typedoc-plugin-external-module-name.
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.
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).
Version 1.1.0 of typedoc-plugin-external-module-name was just published.
The version 1.1.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 typedoc-plugin-external-module-name.
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.
Commits
The new version differs by 12 commits.
6e97419
1.1.0
0ab05e0
chore(package): Add changelog
d6d4538
chore(package): Add release script
6fa2771
test(travis): add .travis.yml
1031d25
test(build): do not use typedoc --tsconfig because it broke in 0.9.0
88c38ea
test(*): Add gitignore
de0622b
test(*): Add publish-scripts to automate downstream testing
c8dbda3
test(typedoc): Add e2d tests for typedoc 0.5.10, 0.7.2, 0.8.0, 0.9.0, 0.10.0, latest
1097400
test(typedoc): Add e2e tests for typedoc 0.6.0
c39c924
fix(doublecomment): Monkey patch getJSDocCommentRanges instead of duplicating all of getRawComment
b1b7213
update .gitignore
124b58c
Revert "fix(doublecomment): Do not use 'getRawComment': better fix for not requiring a second comment block."
See 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: