Back to async_std.

The issue described in #95 has been thoroughly tested & is now fixed.
Shoutout to @jakule for their work on implementing a solid fix for this.

closes #95

CHANGELOG.md

@@ -6,16 +6,14 @@ Subheadings to categorize changes are `added, changed, deprecated, removed, fixe
 
 ## Unreleased
 
-## 0.8.0
+## 0.9.0
+### fixed
+- Closed [#81](https://github.com/thedodd/trunk/issues/81): this is no longer needed as we now have support for WebSockets. HTTP2 is still outstanding, but that will not be a blocker for use from the web.
+- Closed [#95](https://github.com/thedodd/trunk/issues/95): fixed via a few small changes to precendce in routing.
+- Closed [#53](https://github.com/thedodd/trunk/issues/53): we've now implemented support for proxying WebSockets.
+
 ### changed
-- Switch over to `Tokio` from `async_std`
-- Closed [#81](https://github.com/thedodd/trunk/issues/81): Switch to warp from tide.
-- Closed [#95](https://github.com/thedodd/trunk/issues/95): Fixed as a result of switching to warp.
-- Closed [#53](https://github.com/thedodd/trunk/issues/53): Fixed as a result of switching to warp.
-
-## Upgrading from 0.8
-- `--proxy-rewrite` has been renamed to `--proxy-path`.
-- `Trunk.toml` must be updated in a way that `backend` denotes the proxy backend and `path` denotes where the server will listen. See the [example config file](./Trunk.toml) and [README](./README.md#config-file) for more information.
+- The `--proxy-ws` has been added to the `Trunk.toml` and specifies that the given endpoint is for a WebSocket.
 
 ## 0.8.2 & 0.8.1
 ### fixed