bump tinyboot-ch32 to 0.5.0

Author: aq1018

CHANGELOG.md

@@ -4,6 +4,8 @@ Releases up through `v0.4.0` were workspace-wide and tagged `vX.Y.Z`. From `0.4.
 
 ## [Unreleased]
 
+## [tinyboot-ch32 0.5.0] - 2026-07-11
+
 ### Changed
 
 - **Breaking:** `tinyboot-ch32`: duplex selection moved from runtime config to compile time. The `Duplex` enum and `UsartConfig::duplex` are gone; enable the new `half-duplex` cargo feature for single-wire operation (full duplex is the default, and `rx_pull` only exists without the feature). Half-duplex now uses a shared-bus drive discipline: the wire parks open-drain while idle and drives push-pull only around writes, so an idle node never contends with the wire's other talkers — **an external pull-up on the wire is now a hardware requirement** (it owns the idle mark level). Costs ~130 bytes over full duplex; full-duplex binaries are byte-identical to before.

ch32/Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 name = "tinyboot-ch32"
 description = "tinyboot ch32 implementation"
-version = "0.4.1"
+version = "0.5.0"
 edition.workspace = true
 repository.workspace = true
 license.workspace = true

docs/contributing.md

@@ -106,4 +106,4 @@ System-flash validation follows the same shape but uses `wlink` to write to the
 
 ## Releases
 
-Releases are tagged `vX.Y.Z` across the whole repo — all crates share a version. `tinyboot-ch32` stays git-only (not published to crates.io) while it depends on an unreleased `ch32-metapac`. The rest (`tinyboot-core`, `tinyboot-protocol`, `tinyboot`, `tinyboot-ch32-rt`) publish to crates.io.
+Crates release independently: bump the crate's version, add a `## [<crate> X.Y.Z] - <date>` changelog section, and tag `<crate>-vX.Y.Z`. `tinyboot-ch32` stays git-only (not published to crates.io) while it depends on an unreleased `ch32-metapac`. The rest (`tinyboot-core`, `tinyboot-protocol`, `tinyboot`, `tinyboot-ch32-rt`) also publish to crates.io.