Update @octokit/rest to the latest version 🚀

[greenkeeper]

The dependency @octokit/rest was updated from 15.18.0 to 16.0.1.

This version 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.

---

Release Notes for v16.0.1

To upgrade to v16, make sure you have the latest v15 release installed first:

npm install @octokit/rest@15.18.0

Now run the tests and look for DEPRECATED messages in the logs. Once you see no more deprecations, upgrading to v16 should cause no problems.

BREAKING CHANGES

• all previously deprecated methods have been removed

• preview headers that are not required to use an API have been removed

• .gitdata.getTags() has been removed. Use .gitdata.listRefs({namespace: tags}) instead

• Methods for undocumented endpoints have been removed.

  Instead of client.users.getById({id}) use client.request({method: GET, url: /user/:id, id})
  Instead of client.repos.getById({id}) use client.request({method: GET, url: /repositories/:id, id})

• octokit.enterprise.* methods have been removed. They will be moved into a plugin like https://github.com/octokit/plugin-scim.js

• routes: the milestone parameter is no longer validated using a regex as it cannot be derived from octokit/routes

• travis: dropped support for node 4

• error.message is no longer a JSON string containing GitHub’s error message. Instead the JSON is parsed internally and error properties are assigned with its value. This is not technically a breaking change but a bug fix, but as this bug was around for a long time and plenty of apps depend on JSON.parse(error.message) to be working, we treat it as a breaking change by way of precaution

• error.status is now the response status code number. The status text is no longer returned

Features

• .paginate(options, mapFn) (8084afd)
• octokit.paginate & octokit.paginate.iterator (00a692f)
• octokit.registerEndpoints() (08a3c51)
• octokit.request & octokit.request.endpoint (1fdfbf0)
• plugin API (70e114a)
• rename methods to align more closely to the documentation at https://developer.github.com/v3/ (10b4f34), closes /developer.github.com/v3/repos/commits/#get-the-sha-1

Bug Fixes

• routes: remove validation for milestone parameter as it cannot be derived from octokit/routes (4d04d17)
• only set preview headers required to use the API (1628821)
• parse JSON from GitHub error messages (dd6306e)

Continuous Integration

• travis: drop tests in node 4 & 9, test in node 10 (ad8b1e5)

Bug Fixes in v16.0.1

• typescript: Adding return types (18ac5bf), closes #1116
• typescript: Adding the noImplicitAny flag to validate:ts (ef4d35a)
• typescript: Github.plugin is a static method, not an instance method (01763bf)
• typescript: include a header object when transforming Content-Type and Content-Length to headers.content-type and headers.content-length (0b9cc37)

Thanks @mamodom for your great help with these Typescript fixes 💐

Commits

The new version differs by 86 commits.

• 01763bf fix(typescript): Github.plugin is a static method, not an instance method
• ef4d35a fix(typescript): Adding the noImplicitAny flag to validate:ts
• 18ac5bf fix(typescript): Adding return types
• 0b9cc37 fix(typescript): include a header object when transforming Content-Type and Content-Length to headers.content-type and headers.content-length
• ebea33d build: remove obsolete artefacts for flow types
• 9021da4 build(typescript): date response header
• 9efa49e docs(README): typo in code example
• 09c2ba8 build(package): next dist-tag
• 138f08d build: TypeScript typing definitions for v16 updates (#1113)
• 506dc3a docs: wrong variable name in example (#1112)
• 46a1ee9 build(package): remove engine field
• 82a4678 ci(travis): test node_modules folder size is < 1mb
• 73207c7 build: package-lock.json
• c597bf7 build(package): update @octokit/request
• ed90210 build(package-lock): initial version

There are 86 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴