# parse-net v0.6.1 - Entity-tag list fix
**Date:** 2026-10-22
**Compare:** [`v0.6.0...v0.6.1`](https://github.com/jamesgober/parse-net/compare/v0.6.0...v0.6.1)
A fix for the conditional-request fields. Upgrade from 0.6.0 if you read `If-None-Match` or `If-Match`.
## Fixed
- `parse_condition`, `if_none_match`, and `if_match` refused a list of more than 16 entity tags with `TooManyEmptyElements`. The one-pass walker added in 0.6.0 left the comma after each tag for its next pass, which counted it as an empty element; 16 is the default `max_empty_elements`. Lists of up to `max_list_members` tags (1024 by default) are read again, and empty elements are counted as before.
## Testing
- A unit test reads lists of 1, 16, 17, 100, and 1024 tags, refuses 1025, and checks the empty-element boundary before, between, and after the tags.
- A property test compares `parse_condition` with the 0.5 reading (the general list walker and a parse of each element) on generated lists of up to 48 elements, mostly well formed. It fails on the 0.6.0 code and passes on this one.
- Found by the complexity tests being written for 0.7, which feed every walker inputs of 1 KiB, 64 KiB, and 1 MiB.
## Compatibility
- No API change. MSRV 1.85, edition 2024, `no_std` without `alloc`, zero runtime dependencies.
## Verification
- Local gate on Windows and WSL Ubuntu, Rust stable and 1.85: format, clippy with default, all, and no default features under `-D warnings`, tests in the same three modes, documentation under `-D warnings`, the bare-metal build, and `cargo package`.
**Full Changelog:** https://github.com/jamesgober/parse-net/compare/v0.6.0...v0.6.1