Skip to content

Commit a1c8c7b

Browse files
authored
chore: prepare 0.4.3 (#89)
1 parent 387fcfa commit a1c8c7b

File tree

2 files changed

+10
-3
lines changed

2 files changed

+10
-3
lines changed

CHANGELOG.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,10 @@
1+
# 0.4.3 (July 3rd, 2025)
2+
3+
### Added
4+
- rt: partially stabilize `RuntimeMonitor` and related metrics ([#87])
5+
6+
[#87]: https://github.com/tokio-rs/tokio-metrics/pull/87
7+
18
# 0.4.2 (April 30th, 2025)
29

310
### Fixed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ runtime and per-task metrics.
2222

2323
```toml
2424
[dependencies]
25-
tokio-metrics = { version = "0.4.2", default-features = false }
25+
tokio-metrics = { version = "0.4.3", default-features = false }
2626
```
2727

2828
## Getting Started With Task Metrics
@@ -187,7 +187,7 @@ The `rt` feature of `tokio-metrics` is on by default; simply check that you do
187187
not set `default-features = false` when declaring it as a dependency; e.g.:
188188
```toml
189189
[dependencies]
190-
tokio-metrics = "0.4.2"
190+
tokio-metrics = "0.4.3"
191191
```
192192

193193
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`:
224224

225225
```toml
226226
[dependencies]
227-
tokio-metrics = { version = "0.4.2", features = ["metrics-rs-integration"] }
227+
tokio-metrics = { version = "0.4.3", features = ["metrics-rs-integration"] }
228228
metrics = "0.24"
229229
# You don't actually need to use the Prometheus exporter with uds-listener enabled,
230230
# it's just here as an example.

0 commit comments

Comments
 (0)