Version 2.0.4

This follows quickly on 2.0.3, which removed a feature and a function argument. Removing the feature is still the right thing to do (see the 2.0.3 release notes), but the function argument needs to go through a deprecation cycle, since libraries like dask-awkward pass arguments through to Awkward. Removing flatten_records as an argument introduces an error, even if the surviving case of flatten_records=False is desired.

This will also be a good exercise of the deprecation schedule in 2.x.

New features

(none!)

Bug-fixes and performance

• fix: soft-deprecate flatten_records instead of hard-deprecation by @agoose77 in #2036

Other

(none!)

Full Changelog: v2.0.3...v2.0.4