-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update got to the latest version 🚀 #585
Conversation
Version 7.0.0 just got published.Update to this version instead 🚀 Release Notes7.0.0Breaking changes
Highlights
All changes |
Version 7.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 17 commits ahead by 17, behind by 1.
There are 17 commits in total. See the full diff |
@cwillisf Instead of upgrading this, what do you think about switching |
@rschamp, that makes sense to me. Is there any reason to prefer either |
The main consideration is that if you're going to build for both web and Node, then |
(And when we do that, we should do the same for |
Ah, I mis-parsed your initial comment. I see what you were saying now :) |
Version 7.0.0 of got just got published.
The version 7.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of got.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
7.0.0Breaking changes
Setting the
body
option to be an object to stringify is no longer possible without setting either theform
option for URL encoding or thejson
option for JSON encoding. Previously, Got would use URL encoding by default, now it will throw an error. Since thejson
option also means Got will decode a JSON response for you, setting both options totrue
will encode the request as URL and decode the response as JSON.timeout
option now applies to the whole request and we added ability to control the timeout of the individual phases. 7964f2cHighlights
ParseError
when parsing fails on 2xx responses. c86706bprotocol
property to errors. 919703curl
property to errors. a287f8eAll changes
v6.7.1...v7.0.0
Commits
The new version differs by 157 commits ahead by 157, behind by 39.
c20bc5e
7.0.0
6fc1902
Add ability to opt-out of using
electron.net
7964f2c
Request timeout (#308)
b45896a
Redirect on 307, 308, 303 (#307)
a299b00
Set up proxy event emitter before making a request (#304)
2130570
Improve use in Electron (#311)
359a5d1
Use class syntax for errors (#306)
f501fc2
Add WHATWG URL support (#289)
ff0cef0
Tiny cleanup
9ef7a5a
Add ability to cancel in-progress requests (#287)
c86706b
Only throw ParseError on 2xx responses (#301)
8b4d06e
Include response headers and redirect URLs in error object (#302)
6d19a72
Bump some devDependencies
578f38d
Set
url
andrequestUrl
directly on the response (#300)14d0859
reduce retries number and make delays shorter (#299)
There are 157 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴