Prepare for v0.2.0 release (#248)

* prepare for v0.2.0 release

Signed-off-by: Dennis Adjei-Baah <[email protected]>

Author: dadjeibaah

CHANGES.md

@@ -1,3 +1,31 @@
+## v0.2.0
+
+This is a big milestone! With this release, Conduit adds support for HTTP/1.x and raw TCP traffic,
+meaning it should "just work" for most applications that are running on Kubernetes without
+additional configuration.
+
+* Data plane
+  * Conduit now transparently proxies all TCP traffic, including HTTP/1.x and HTTP/2.
+    (See caveats below.)
+* Command-line interface
+  * Improved error handling for the `tap` command
+  * `tap` also now works with HTTP/1.x traffic
+* Dashboard
+  * Minor UI appearance tweaks
+  * Deployments now searchable from the dashboard sidebar
+
+Caveats:
+* Conduit will automatically work for most protocols. However, applications that use WebSockets,
+  HTTP tunneling/proxying, or protocols such as MySQL and SMTP, will require some additional
+  configuration. See the [documentation](https://conduit.io/adding-your-service/#protocol-support)
+  for details.
+* Conduit doesn't yet support external DNS lookups. These will be addressed in an upcoming release.
+* There are known issues with Conduit's telemetry pipeline that prevent it from scaling beyond a
+  few nodes. These will be addressed in an upcoming release.
+* Conduit is still in alpha! Please help us by
+  [filing issues and contributing pull requests](https://github.com/runconduit/conduit/issues/new).
+
+
 ## v0.1.3
 
 * This is a minor bugfix for some web dashboard UI elements that were not rendering correctly.
@@ -30,7 +58,7 @@ Conduit 0.1.1 is focused on making it easier to get started with Conduit.
 * The `conduit tap` command output has been reformatted to be line-oriented, making it easier to
   parse with common UNIX command line utilities.
 * Conduit now supports routing of non-fully qualified domain names.
-* The web UI has improved support for large deployments and deployments that don’t have any
+* The web UI has improved support for large deployments and deployments that don't have any
   inbound/outbound traffic.
 
 ## v0.1.0

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "codegen"
-version = "0.1.3"
+version = "0.2.0"
 authors = ["Carl Lerche <[email protected]>"]
 
 [dependencies]

codegen/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "futures-mpsc-lossy"
-version = "0.1.3"
+version = "0.2.0"
 authors = ["Oliver Gould <[email protected]>"]
 publish = false
 

futures-mpsc-lossy/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "conduit-proxy"
-version = "0.1.3"
+version = "0.2.0"
 authors = ["Oliver Gould <[email protected]>"]
 publish = false
 

proxy/Cargo.toml

@@ -5,7 +5,7 @@
 ## Build the rust proxy into a binary.
 #
 # If the RELEASE arg is set and non-empty, a release artifact is built.
-FROM gcr.io/runconduit/proxy-deps:6c797c62 as build
+FROM gcr.io/runconduit/proxy-deps:7280cf64 as build
 WORKDIR /usr/src/conduit
 # Ranked roughly from least to most likely to change. Cargo.lock is the least likely
 # because it is supposed to be cached in the deps base image.

proxy/Dockerfile

@@ -1,8 +1,8 @@
 [package]
 name = "tower-grpc-build"
-version = "0.1.3"
+version = "0.2.0"
 authors = ["Carl Lerche <[email protected]>"]
 
 [dependencies]
-codegen = { version = "0.1", path = "../codegen" }
+codegen = { version = "0.2", path = "../codegen" }
 prost-build = "0.2"

tower-grpc-build/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "tower-grpc-examples"
-version = "0.1.3"
+version = "0.2.0"
 authors = ["Carl Lerche <[email protected]>"]
 
 [[bin]]

tower-grpc-examples/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "tower-grpc"
-version = "0.1.3"
+version = "0.2.0"
 authors = ["Sean McArthur <[email protected]>"]
 
 [features]

tower-grpc/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "tower-h2"
-version = "0.1.3"
+version = "0.2.0"
 authors = ["Oliver Gould <[email protected]>"]
 description = "Exploring tower + h2"
 publish = false