v2.2.0

• Feature: Forward compatibility with freshly released react/promise-stream v1.0
  (#85 by @WyriHaximus)

v2.1.0

• Feature: Update minimum required Socket dependency version in order to
  support Unix Domain Sockets (UDS) again,
  support hosts file on all platforms and
  work around sending secure HTTPS requests with PHP < 7.1.4
  (#84 by @clue)

v2.0.0

A major compatibility release to update this component to support all latest
ReactPHP components!

This update involves a minor BC break due to dropped support for legacy
versions. We've tried hard to avoid BC breaks where possible and minimize impact
otherwise. We expect that most consumers of this package will actually not be
affected by any BC breaks, see below for more details.

• BC break: Remove deprecated API and mark Sender as @internal only,
  remove all references to legacy SocketClient component and
  remove support for Unix domain sockets (UDS) for now
  (#77, #78, #81 and #83 by @clue)

  All of this affects the Sender only, which was previously marked as
  "advanced usage" and is now marked @internal only. If you've not
  used this class before, then this BC break will not affect you.
  If you've previously used this class, then it's recommended to first
  update to the intermediary v1.4.0 release, which allows you to use a
  standard ConnectorInterface instead of the Sender and then update
  to this version without causing a BC break.
  If you've previously used Unix domain sockets (UDS), then you're
  recommended to wait for the next version.

• Feature / BC break: Forward compatibility with future Stream v1.0 and strict stream semantics
  (#79 by @clue)

  This component now follows strict stream semantics. This is marked as a
  BC break because this removes undocumented and untested excessive event
  arguments. If you've relied on proper stream semantics as documented
  before, then this BC break will not affect you.

• Feature: Forward compatibility with future Socket and EventLoop components
  (#80 by @clue)

v1.4.0

• Feature: Browser accepts ConnectorInterface and deprecate legacy Sender
  (#76 by @clue)

  If you need custom connector settings (DNS resolution, TLS parameters, timeouts,
  proxy servers etc.), you can explicitly pass a custom instance of the
  ConnectorInterface:

  $connector = new \React\Socket\Connector($loop, array(
      'dns' => '127.0.0.1',
      'tcp' => array(
          'bindto' => '192.168.10.1:0'
      ),
      'tls' => array(
          'verify_peer' => false,
          'verify_peer_name' => false
      )
  ));
  
  $browser = new Browser($loop, $connector);

v1.3.0

• Feature: Support request cancellation
  (#75 by @clue)

  $promise = $browser->get($url);
  
  $loop->addTimer(2.0, function () use ($promise) {
      $promise->cancel();
  });

• Feature: Update react/http-client to v0.5,
  support react/stream v0.6 and react/socket-client v0.7 and drop legacy PHP 5.3 support
  (#74 by @clue)

v1.2.0

• Feature: Forward compatibility with react/http-client v0.5
  (#72 and #73 by @clue)

  Older HttpClient versions are still supported, but the new version is now
  preferred. Advanced usage with custom connectors now recommends setting up
  the React\HttpClient\Client instance explicitly.

  Accordingly, the Sender::createFromLoopDns() and
  Sender::createFromLoopConnectors() have been marked as deprecated and
  will be removed in future versions.

v1.1.1

• Restructure examples to ease getting started and
  fix online tests and add option to exclude tests against httpbin.org
  (#67 and #71 by @clue)

• Improve test suite by fixing HHVM build for now again and ignore future HHVM build errors and
  lock Travis distro so new defaults will not break the build
  (#68 and #70 by @clue)

v1.1.0

• Feature: Obey explicitly set HTTP protocol version for outgoing requests
  (#58, #59 by @WyriHaximus, @clue)

  $request = new Request('GET', $url);
  $request = $request->withProtocolVersion(1.1);
  
  $browser->send($request)->then(…);

v1.0.1

• Fix: Explicitly define all minimum required package versions
  (#57 by @clue)

v1.0.0

• First stable release, now following SemVer
• Improve documentation and usage examples

Contains no other changes, so it's actually fully compatible with the v0.5.0 release.