The version 13.0.1 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 github.
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 13.0.1 of github was just published.
The version 13.0.1 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 github.
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
v13.0.113.0.1 (2017-12-02)
Bug Fixes
Commits
The new version differs by 73 commits.
9c68105
fix: respect NO_PROXY environment variable (#667)
3c4ab02
breaking: remove
.get{Scope name}Api()
methods1956da2
test: remove test for
.get{Scope name}Api()
methods31ba34a
docs(CONTRIBUTING): add note about how type definitions and API docs are generated and published automatically
762a7e3
docs(README): remove dev notes section
5e5d2b2
chore: remove
followRedirects
option from type definitionsabb2be4
chore(package): publish to npm with @next dist tag
51eeb0d
fix: no headers are sent if there are no headers
20da873
test: no "link" header is sent if there are no pages
7f3528a
chore(package): deploy docs after publish
49d21dd
chore(package): build:docs script
2e98859
chore(script): generate API docs
21b234b
docs(README): add heads up comment to keep README example and type definition templates in sync
21c50a8
chore(gitignore): doc/apidoc.js
cd70273
chore: lowercase scripts file names
There are 73 commits in total.
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: