# 0.3.22 (November 28, 2025)

#### Important

The previous release [0.3.21] was yanked as it depended explicitly on
[tracing-0.1.42], which was yanked due to a breaking change (see [#3424] for
details). This release contains all the changes from the previous release, plus
an update to the newer version of `tracing`.

### Changed

- `tracing`: updated to 0.1.43 ([#3427])

[#3424]: #3424
[#3427]: #3427
[0.3.21]: https://github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.21
[tracing-0.1.42]: https://github.com/tokio-rs/tracing/releases/tag/tracing-0.1.42

# 0.1.0-beta.3 (November 28, 2025)

#### Important

The previous release [0.1.0-beta.2] was yanked as it depended explicitly on
[tracing-0.1.42], which was yanked due to a breaking change (see [#3424] for
details). This release contains all the changes from the previous release, plus
an update to the newer version of `tracing`.

### Changed

- `tracing`: updated to 0.1.43 ([#3427])

[#3424]: #3424
[#3427]: #3427
[0.1.0-beta.2]: https://github.com/tokio-rs/tracing/releases/tag/tracing-mock-0.1.0-beta.2
[tracing-0.1.42]: https://github.com/tokio-rs/tracing/releases/tag/tracing-0.1.42

## Motivation

This seems to be a result of the new `valueset!` optimisations combined
with this new `record_all!` feature. In fact, the `record_all!` feature never
worked with a set of fields differnt to all a span's fields in the correct order.

The following code panics

```rust
#[test]
fn tracing_bug() {
    let span = tracing::info_span!("example", foo=1, bar=2);
    tracing::record_all!(span, foo=3);
}
```

## Solution

This is horrible. We rename `valueset!` to `valueset_all!`, then
we re-introduce the original `valueset!` with some notable changes.

The new `valueset!` doesn't use fields from the fieldset iterator, it
instead uses `FieldSet::field(...)` to find the correct field. If the field
isn't found, we set a fallback field that will be ignored (callsites are
not equal).

Fixes #3431

# 0.1.36 (December 18, 2025)

- Fix `record_all` panic ([#3432])

[#3432]: #3432

# 0.1.44 (December 18, 2025)

### Fixed

- Fix `record_all` panic ([#3432])

### Changed

- `tracing-core`: updated to 0.1.36 ([#3440])

[#3432]: #3432
[#3440]: #3440