chore: prepare 0.4.2

Author: jlizen

CHANGELOG.md

@@ -1,3 +1,12 @@
+# 0.4.2 (April 30th, 2025)
+
+### Fixed
+ - docs: specify metrics-rs-integration feature dependency for relevant APIs ([#78])
+ - docs: fix links ([#79])
+
+[#78]: https://github.com/tokio-rs/tokio-metrics/pull/78
+[#79]: https://github.com/tokio-rs/tokio-metrics/pull/79
+
 # 0.4.1 (April 20th, 2025)
 
 ### Added

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "tokio-metrics"
-version = "0.4.1"
+version = "0.4.2"
 edition = "2021"
 rust-version = "1.70.0"
 authors = ["Tokio Contributors <[email protected]>"]

README.md

@@ -22,7 +22,7 @@ runtime and per-task metrics.
 
 ```toml
 [dependencies]
-tokio-metrics = { version = "0.4.1", default-features = false }
+tokio-metrics = { version = "0.4.2", default-features = false }
 ```
 
 ## Getting Started With Task Metrics
@@ -176,7 +176,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.1"
+tokio-metrics = "0.4.2"
 ```
 
 From within a Tokio runtime, use `RuntimeMonitor` to monitor key metrics of
@@ -213,7 +213,7 @@ If you want to use [Prometheus], you could have this `Cargo.toml`:
 
 ```toml
 [dependencies]
-tokio-metrics = { version = "0.4.1", features = ["metrics-rs-integration"] }
+tokio-metrics = { version = "0.4.2", 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.