release: prepare v0.2.0

Cargo.toml

@@ -3,7 +3,7 @@ resolver = "3"
 members = ["dhttp", "identity", "home", "api", "access"]
 
 [workspace.package]
-version = "0.1.0"
+version = "0.2.0"
 edition = "2024"
 license = "Apache-2.0"
 repository = "https://github.com/genmeta/dhttp"
@@ -38,15 +38,18 @@ chrono = { version = "0.4", features = ["serde"] }
 
 # Keep same-repository workspace members as path dependencies. Cross-repo
 # release dependencies resolve through crates.io in the formal release graph.
-dhttp-identity = "0.1.0"
-dhttp-home = { path = "home", version = "0.1.0" }
-ddns = { package = "dyns", version = "0.3.0", features = [
-    "h3x-resolver",
-    "mdns-resolver",
-    "http-resolver",
+dhttp-identity = "0.2.0"
+dhttp-home = { path = "home", version = "0.2.0" }
+ddns = { package = "dyns", version = "0.4.0", features = [
+    "resolvers",
+    "publishers",
+    "h3",
+    "http",
+    "mdns",
+    "dquic-network",
 ] }
-h3x = { version = "0.3.1", features = [
+h3x = { version = "0.4.0", features = [
     "dquic",
 ] }
-dhttp = { path = "dhttp", version = "0.1.0" }
-dhttp-access = { path = "access", version = "0.1.0" }
+dhttp = { path = "dhttp", version = "0.2.0" }
+dhttp-access = { path = "access", version = "0.2.0" }

README.md

@@ -32,11 +32,11 @@ Lower-level crates can be used independently, but application code should normal
 
 ### Add the Rust SDK
 
-Until the crates are published through the registry flow you use, depend on this repository directly:
+Add the published crate to your Cargo manifest:
 
 ```toml
 [dependencies]
-dhttp = { git = "https://github.com/genmeta/dhttp.git", version = "0.1.0" }
+dhttp = "0.2.0"
 ```
 
 ### Build an endpoint

api/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genmeta/dhttp",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "The True Internet",
   "license": "Apache-2.0",
   "homepage": "https://dhttp.net/",