Consolidate CHANGELOG
This commit is contained in:
parent
67678a9a54
commit
a10f5786bd
28
CHANGELOG.md
28
CHANGELOG.md
|
@ -5,40 +5,30 @@ Changelog
|
|||
|
||||
# 2.x release
|
||||
|
||||
## v2.0.0-alpha.3
|
||||
|
||||
- Major: overwrite user's `Content-Length` if we can be sure our information is correct
|
||||
- Fix: exhaust list in `Headers` constructor before processing
|
||||
|
||||
## v2.0.0-alpha.2
|
||||
|
||||
- Major: remove `headers.getAll()`; make `get()` return all headers delimited by commas (per spec)
|
||||
- Major: remove undocumented `FOLLOW_SPEC` switch -- it is now the default
|
||||
|
||||
## v2.0.0-alpha.1
|
||||
## v2.0.0
|
||||
|
||||
This is a major release. Check [our upgrade guide](https://github.com/bitinn/node-fetch/blob/master/UPGRADE-GUIDE.md) for an overview on some key differences between v1 and v2.
|
||||
|
||||
- Major: Node.js 0.10.x support is dropped
|
||||
- Major: rewrite in transpiled ES2015
|
||||
- Major: Node.js 0.10.x and 0.12.x support is dropped
|
||||
- Major: overwrite user's `Content-Length` if we can be sure our information is correct (per spec)
|
||||
- Major: `response.text()` no longer attempts to detect encoding, instead always opting for UTF-8 (per spec); use `response.textConverted()` for the v1 behavior
|
||||
- Major: make `response.json()` throw error instead of returning an empty object on 204 no-content respose (per spec; reverts behavior changed in v1.6.2)
|
||||
- Major: remove `headers.getAll()`; make `get()` return all headers delimited by commas (per spec)
|
||||
- Major: internal methods are no longer exposed
|
||||
- Major: throw error when a GET/HEAD Request is constructed with a non-null body (per spec)
|
||||
- Major: `response.text()` no longer attempts to detect encoding, instead always opting for UTF-8 (per spec); use `response.textConverted()` for the old behavior
|
||||
- Major: make `response.json()` throw error instead of returning an empty object on 204 no-content respose (per spec; reverts behavior set in v1.6.2)
|
||||
- Major: arrays as parameters to `headers.append` and `headers.set` are joined as a string (per spec)
|
||||
- Major: throw error when a `GET` or `HEAD` Request is constructed with a non-null body (per spec)
|
||||
- Enhance: start testing on Node.js 4, 6, 7
|
||||
- Enhance: use Rollup to produce a distributed bundle (less memory overhead and faster startup)
|
||||
- Enhance: make `toString()` on Headers, Requests, and Responses return correct IDL class strings
|
||||
- Enhance: add an option to conform to latest spec at the expense of reduced compatibility
|
||||
- Enhance: set `Content-Length` header for Buffers as well
|
||||
- Enhance: add `response.arrayBuffer()` (also applies to Requests)
|
||||
- Enhance: add experimental `response.blob()` (also applies to Requests)
|
||||
- Enhance: make Headers iterable
|
||||
- Enhance: make Headers constructor accept an array of tuples
|
||||
- Enhance: make sure header names and values are valid in HTTP
|
||||
- Enhance: add a list of default headers in README
|
||||
- Fix: coerce Headers prototype function parameters to strings, where applicable
|
||||
- Fix: fix Request and Response with `null` body
|
||||
- Fix: support WHATWG URL objects, created by `whatwg-url` package or `require('url').URL` in Node.js 7+
|
||||
- Other: rewrite in ES2015 using Babel and Rollup
|
||||
- Other: use Codecov for code coverage tracking
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue