Proxy support for WebSockets is g2g!

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

Co-authored-by: Hamza <muhammadhamza1311@gmail.com>

CHANGELOG.md

@@ -6,6 +6,18 @@ Subheadings to categorize changes are `added, changed, deprecated, removed, fixe
 
 ## Unreleased
 
+## 0.9.0
+### added
+Added support for proxying WebSockets. This was a long-standing feature request. Due to changes upstream in the async-std/tide ecosystem, we are not able to properly support this. This will also unlock some nice features such as HMR via WebSockets, and other such niceties.
+
+### 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
+- The `--proxy-ws` has been added to the `Trunk.toml` and specifies that the given endpoint is for a WebSocket.
+
 ## 0.8.3
 ### fixed
 - Fixed [#133](https://github.com/thedodd/trunk/issues/133) where `watch` was infinitely looping on Windows