diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6bbbccc..082ae0b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,10 @@
+# 0.4.3 (July 3rd, 2025)
+
+### Added
+ - rt: partially stabilize `RuntimeMonitor` and related metrics ([#87])
+
+[#87]: https://github.com/tokio-rs/tokio-metrics/pull/87
+
 # 0.4.2 (April 30th, 2025)
 
 ### Fixed
diff --git a/README.md b/README.md
index 173725a..2c1d1b8 100644
--- a/README.md
+++ b/README.md
@@ -22,7 +22,7 @@ runtime and per-task metrics.
 
 ```toml
 [dependencies]
-tokio-metrics = { version = "0.4.2", default-features = false }
+tokio-metrics = { version = "0.4.3", default-features = false }
 ```
 
 ## Getting Started With Task Metrics
@@ -187,7 +187,7 @@ The `rt` feature of `tokio-metrics` is on by default; simply check that you do
 not set `default-features = false` when declaring it as a dependency; e.g.:
 ```toml
 [dependencies]
-tokio-metrics = "0.4.2"
+tokio-metrics = "0.4.3"
 ```
 
 From within a Tokio runtime, use `RuntimeMonitor` to monitor key metrics of
@@ -224,7 +224,7 @@ If you want to use [Prometheus], you could have this `Cargo.toml`:
 
 ```toml
 [dependencies]
-tokio-metrics = { version = "0.4.2", features = ["metrics-rs-integration"] }
+tokio-metrics = { version = "0.4.3", features = ["metrics-rs-integration"] }
 metrics = "0.24"
 # You don't actually need to use the Prometheus exporter with uds-listener enabled,
 # it's just here as an example.