greenkeeper[bot]
commented
5 years ago - The
dependency@octokit/rest was updated from15.18.0to16.0.3.
Update to this version instead 🚀
Release Notes for v16.0.3
Bug Fixes
- aliasing
octokit.gitdata→octokit.git,octokit.authorization→octokit.oauthAuthorizations,octokit.pullRequests→octokit.pulls(0766d51)
Thanks to @hipstersmoothie for their help
Commits
The new version differs by 11 commits.
0766d51fix: aliasingoctokit.gitdata→octokit.git,octokit.authorization→octokit.oauthAuthorizations,octokit.pullRequests→octokit.pulls05f3f7bbuild: routes.jsonabcadaabuild: generate routes.json without manually mapping scopes367c710test: octokit.pulls.*db3074cbuild(types): remove obsolete code (#1122)72e26d2build: routes2a7343fchore(package): update lockfile package-lock.json0b13a63chore(package): update @octokit/routes to version 15.2.0b774adechore(package): update lockfile package-lock.json31185c9fix(package): update @octokit/request to version 2.1.2d926a8fdocs(README): Changegithub.paginatetooctokit.paginate(#1126)
See the full diff
The dependency @octokit/rest was updated from
15.18.0to16.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:
Now run the tests and look for
DEPRECATEDmessages 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})insteadMethods for undocumented endpoints have been removed.
Instead of
client.users.getById({id})useclient.request({method: GET, url: /user/:id, id})Instead of
client.repos.getById({id})useclient.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.jsroutes: the
milestoneparameter is no longer validated using a regex as it cannot be derived from octokit/routestravis: 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 precautionerror.statusis now the response status code number. The status text is no longer returnedFeatures
Bug Fixes
Continuous Integration
Bug Fixes in v16.0.1
noImplicitAnyflag tovalidate:ts(ef4d35a)headerobject when transformingContent-TypeandContent-Lengthtoheaders.content-typeandheaders.content-length(0b9cc37)Thanks @mamodom for your great help with these Typescript fixes💐
Commits
The new version differs by 86 commits.
01763bffix(typescript): Github.plugin is a static method, not an instance methodef4d35afix(typescript): Adding thenoImplicitAnyflag tovalidate:ts18ac5bffix(typescript): Adding return types0b9cc37fix(typescript): include aheaderobject when transformingContent-TypeandContent-Lengthtoheaders.content-typeandheaders.content-lengthebea33dbuild: remove obsolete artefacts for flow types9021da4build(typescript): date response header9efa49edocs(README): typo in code example09c2ba8build(package): next dist-tag138f08dbuild: TypeScript typing definitions for v16 updates (#1113)506dc3adocs: wrong variable name in example (#1112)46a1ee9build(package): remove engine field82a4678ci(travis): test node_modules folder size is < 1mb73207c7build: package-lock.jsonc597bf7build(package): update @octokit/requested90210build(package-lock): initial versionThere are 86 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: