bump version to "0.20.0-alpha.1"

Author: yngrtc

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "webrtc"
-version = "0.20.0"
+version = "0.20.0-alpha.1"
 authors = ["Rain Liu <yliu@webrtc.rs>"]
 edition = "2024"
 license = "MIT/Apache-2.0"
@@ -17,7 +17,8 @@ runtime-tokio = ["dep:tokio"]
 runtime-smol = ["dep:smol", "dep:async-broadcast"]
 
 [dependencies]
-rtc = { version = "0.9.0", path = "rtc/rtc" }
+rtc = { version = "0.20.0-alpha.1", path = "rtc/rtc" }
+
 bytes = "1.11.1"
 async-trait = "0.1.89"
 log = "0.4.29"
@@ -29,13 +30,14 @@ smol = { version = "2.0.2", optional = true }
 async-broadcast = { version = "0.7", optional = true }
 
 [dev-dependencies]
+signal = { version = "0.20.0-alpha.1", path = "rtc/examples/examples/signal", package = "rtc-signal" }
+
 env_logger = "0.11.8"
 chrono = "0.4.43"
 clap = { version = "4.5.59", features = ["derive"] }
 anyhow = "1.0.102"
 ctrlc = "3.5.2"
 serde_json = "1.0.149"
-signal = { version = "0.9.0", path = "rtc/examples/examples/signal", package = "rtc-signal" }
 hyper = { version = "0.14.32", features = ["full"] }
 rand = "0.10.0"
 

README.md

@@ -65,13 +65,18 @@ alt="Recall.ai">
 ## Overview
 
 WebRTC.rs is an async-friendly WebRTC implementation in Rust, originally inspired by and largely rewriting the Pion
-stack. The project is currently evolving into a clean, ergonomic, runtime-agnostic implementation that works with any async runtime (Tokio, async-std, smol, embassy).
+stack. The project is currently evolving into a clean, ergonomic, runtime-agnostic implementation that works with any
+async runtime (Tokio, async-std, smol, embassy).
 
 **Architecture:**
-- **[rtc](https://github.com/webrtc-rs/rtc)**: Sans-I/O protocol core with complete WebRTC stack (95%+ W3C API compliance)
+
+- **[rtc](https://github.com/webrtc-rs/rtc)**: Sans-I/O protocol core with complete WebRTC stack (95%+ W3C API
+  compliance)
 - **webrtc** (this crate): Async-friendly API with runtime abstraction layer
 
-**📖 Learn more:** Read our [architecture blog post](https://webrtc.rs/blog/2026/01/31/async-friendly-webrtc-architecture.html) for design details and roadmap.
+**📖 Learn more:** Read
+our [architecture blog post](https://webrtc.rs/blog/2026/01/31/async-friendly-webrtc-architecture.html) for design
+details and roadmap.
 
 ### 🚨 Important Notice: v0.17.x Feature Freeze & v0.20.0+ Development
 
@@ -85,29 +90,34 @@ stack. The project is currently evolving into a clean, ergonomic, runtime-agnost
 #### **What's Changing in upcoming v0.20.0+?**
 
 The new architecture will address critical issues in v0.17.x:
+
 - ❌ Callback hell and Arc explosion
 - ❌ Resources leak in callback
 - ❌ Tight Tokio coupling (cannot use async-std, smol, embassy)
 
 **v0.20.0+ will provide:**
 
 ✅ **Runtime Independence**
+
 - Support for Tokio, async-std, smol, embassy via Quinn-style runtime abstraction
 - Feature flags: `runtime-tokio` (default), `runtime-async-std`, `runtime-smol`, `runtime-embassy`
 
 ✅ **Clean Event Handling**
+
 - Trait-based event handlers with native `async fn in trait`
 - No more callback Arc cloning or `Box::new(move |...| Box::pin(async move { ... }))`
 - Centralized state management with `&mut self`
 
 ✅ **Sans-I/O Foundation**
+
 - Protocol logic completely separate from I/O (via [rtc](https://github.com/webrtc-rs/rtc) crate)
 - Deterministic testing without real network I/O
 - Zero-cost abstractions
 
 #### **How to Provide Feedback**
 
 We're actively designing v0.20.0+ and welcome your input:
+
 - Review the [architecture blog post](https://webrtc.rs/blog/2026/01/31/async-friendly-webrtc-architecture.html)
 - Join discussions on [GitHub Issues](https://github.com/webrtc-rs/webrtc/issues)
 - Chat with us on [Discord](https://discord.gg/4Ju8UHdXMs)
@@ -134,6 +144,25 @@ cargo doc --open
 cargo run --example data-channels
 ```
 
+## Semantic Versioning
+
+This project follows [Semantic Versioning](https://semver.org/):
+
+- **Patch** (`0.x.Y`): Bug fixes and internal improvements with no public API changes.
+- **Minor** (`0.X.0`): Backwards-compatible additions or deprecations to the public API.
+- **Major** (`X.0.0`): Breaking changes to the public API.
+
+While the version is `0.x`, the minor version acts as the major — i.e., a minor bump may include breaking changes. Once
+`1.0.0` is released, full semver stability guarantees apply.
+
+Pre-release versions are published with the following suffixes, in order of increasing stability:
+
+- **`-alpha.N`**: Early preview. API is unstable and may change significantly.
+- **`-beta.N`**: Feature-complete for the release. API may still have minor changes.
+- **`-rc.N`**: Release candidate. No further API changes are expected unless critical issues are found.
+
+For example: `1.0.0-alpha.1` → `1.0.0-beta.1` → `1.0.0-rc.1` → `1.0.0`.
+
 ## Open Source License
 
 Dual licensing under both MIT and Apache-2.0 is the currently accepted standard by the Rust language community and has